Skip to content

softaworks/agent-toolkit / skills/reducing-entropy

reducing-entropy

Verified

Manual-only skill for minimizing total codebase size. Only activate when explicitly requested by user. Measures success by final code amount, not effort. Bias toward deletion.

references/simplicity-vs-easy.md

View on GitHub
---
description: Simple is objective (not intertwined), easy is subjective (familiar). Choose simple over easy for long-term maintainability.
---

# Simplicity vs Easy

## The Core Distinction

**Simple** and **easy** are not the same thing. We conflate them constantly, and it costs us.

- **Simple**: One concept, not intertwined with others. Objective measure.
- **Easy**: Near at hand, familiar, relative to our capabilities. Subjective.

Easy changes over time as you learn. Simple is absolute.

## Why This Matters

When we reach for the "easy" solution - the familiar pattern, the framework we know, the abstraction we've used before - we often add complexity. The easy path introduces concepts that intertwine with others.

The simple solution might be unfamiliar. It might require thinking. But it doesn't braid together concerns that should be separate.

## Complecting

"Complect" means to intertwine or braid together.

Complexity comes from braiding together concepts that should be separate. Every time we couple things, we create complexity. Every coupling is a future debugging session.

Simple means:
- One role
- One task  
- One concept

If you can't explain it simply, it's too complex.

## The Choice

When designing, ask: "Am I choosing this because it's simple, or because it's familiar?"

Familiar feels productive. Simple *is* productive - over the lifetime of the code.

**Choose simple over easy. Always.**

## External References

- [Simple Made Easy](https://www.infoq.com/presentations/Simple-Made-Easy/) - Rich Hickey's canonical talk on this distinction
- [The Value of Values](https://www.infoq.com/presentations/Value-Values/) - Related talk on immutability and simplicity
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall