Rewriting Code? Discover the Key Question You Should Be Asking

Skip to main content

Hashnode Roberto Lupi

The Math of SRE
Augmented Awareness
Deep Cuts

Command Palette

Search for a command to run...

Rewriting Code? Discover the Key Question You Should Be Asking

Why Identifying the Underlying Need is Crucial in Personal Creative Projects

UpdatedMarch 23, 2025

•2 min read•View as Markdown

Rewriting Code? Discover the Key Question You Should Be Asking

Comments

Join the discussion

No comments yet. Be the first to comment.

More from this blog

The Protocol Reviews Itself

One day of botfam — the agents design their coordination layer, review it, build it, break it, and fix it. I contribute two shell commands and a bedtime rule.

Jun 9, 2026·10 min read

Two Worktrees, One Clean Merge

The last post ended on a promise. After two AI assistants learned to drop letters into a shared mailbox instead of taking turns at a notepad, I said the next thing to build was the boring half of any

Jun 8, 2026·10 min read

The Notepad Becomes a Mailbox

In the last post, two AI assistants learned to share a notepad: a single markdown file, one turn at a time, with me carrying every handoff between them by hand. It worked. It was also slow on purpose

Jun 7, 2026·10 min read

Two AIs, One Notepad

I've been running two AI coding assistants in parallel. Claude for architecture and implementation — it reasons carefully about code structure and catches edge cases. Gemini for research, reading long

Jun 6, 2026·6 min read

The Chorus Is the Part That Comes Back

Pulsar by Vangelis is a 12-minute track. The first seven minutes are slow, evolving, near-silence synthesis. Then it erupts. Deep Cuts was telling me it sounded like AC/DC. The bug was in how I'd been

Jun 5, 2026·7 min read

Roberto Lupi

27 posts

Writing new software is a journey of research, discovery, and creation. Like any research endeavor, it requires a clear guiding question to establish direction. This question is only answered at the conclusion of the process. Moving in one direction means temporarily setting aside other possibilities. Building momentum demands a sustained commitment to a chosen path. Without this commitment, you will repeat false starts over and over. If you find yourself frequently starting over, take a moment to clarify the question you are implicitly trying to answer.

Any research starts with a clear question that gives direction. Similarly, any new software begins with a clear goal and a set of requirements you want to meet. In personal projects, it's easy to skip this step and end up starting over repeatedly, getting lost in the excitement of creation for its own sake.

Any decision to move in a particular direction means temporarily foregoing other options. In software development, choosing a specific technology stack, such as opting for React for the front end and Node.js for the back end, means setting aside alternatives like Blazor or Python/Django, at least for the time being. This choice influences the project's architecture, the skills required, and the potential trade-offs. Personal projects come with their own challenges because working alone is both freeing and limiting.

Building momentum requires a steady commitment to a chosen direction. Without this commitment, false starts become common. Constantly changing direction wastes time and resources and lowers morale. Each shift means relearning new tools and adapting to different approaches, which slows down overall progress.

If the direction you're heading in turns out to be wrong or misleading, don't just go back to writing software from scratch. Instead, revisit your implicit requirements. If you find yourself restarting projects again and again, it's crucial to clarify the core problem you're trying to address.

#requirements #creativity

© 2026 Roberto Lupi

Members
Archive
Privacy
Terms