I built Project Delta as a solo, indie project, alongside my studies, with limited time and no external users. From the start, I was the only person using the product, and I treated that as a design constraint, not a shortcut.

Because of this, I optimized for clarity and speed over scalability. The goal wasn’t to build a flexible platform — it was to validate whether structured case studies actually improved how I reasoned about my work.

I deliberately avoided multi-user authentication and account management. Supporting multiple users would have forced premature decisions around onboarding, permissions, and data isolation before the core structure was proven.

The most uncomfortable constraint was rigidity. Locking content into fixed structures meant I couldn’t rely on free-form writing when something felt unclear. That friction was intentional — it exposed weak thinking instead of hiding it behind prose.

Time was the final constraint. I spent roughly two months building Project Delta, which forced strict scope discipline. Draft vs publish was enough. Anything else had to justify its complexity.

One constraint I underestimated was version history. I assumed it would be straightforward, but it became one of the most complex and fragile parts of the system. Even now, it’s imperfect — reinforcing my bias toward minimizing state and avoiding features that multiply complexity too early.