Design for the next developer
A project should explain itself through its folders, routes, database, and ordinary source files. The next maintainer should not need private context to discover how a request works.
Read the reasoning
Our approach
Software should remain understandable
The largest cost of business software is rarely its first release. It is changing the system safely years later, after its original assumptions and maintainers have moved on.
Maintenance is the dominant cost
Business software accumulates history: exceptions, integrations, data, and decisions nobody remembers making. A framework should make that history easier to follow, not bury it beneath another platform.
Reepolee treats understandability, maintainability, and direct operation as constraints that shape every technical choice.
Five principles for software that lasts
These are not universal rules for every system. They are the defaults we use for long-lived applications maintained by one developer or a small team.
Prefer explicit code over hidden behavior
Conventions and generators should remove repetition without concealing the result. Generated code remains available for review, testing, and adaptation.
Read the reasoningTreat the database as a foundation
Use SQL, constraints, relationships, and deliberate names as part of the application model, not as an implementation detail to hide behind imagined portability.
Read the reasoningKeep the runtime smaller than the problem
Add moving parts only when the application earns them. Simple deployment, visible failure modes, and fewer production packages are operational features.
Read the reasoningOwn where the software runs
Code, data, and infrastructure are business responsibilities. The architecture should preserve the option to run on a modest VPS or on-premise.
Read the reasoningThe source is part of the argument
Reepolee Framework and ReeWeb are MIT licensed because inspectability should not stop at documentation. The implementation, generators, defaults, and tradeoffs are open to examination and adaptation.
The principles in working software
ReeWeb applies them to static sites and documentation. Reepolee Framework applies them to database-backed business applications. Engineering Notes preserve the longer arguments behind both.