How I Build Software
Opinions on building software and running a one-person studio: MVPs worth keeping, why Scrum fails small teams, shipping every week, pricing and referrals.
Software Engineering Principles for Startups
33 principles I use to ship software every week: a working system built from years of product development
Why Scrum Fails in Small Teams
Scrum was designed to coordinate large cross-functional teams. When your team is small enough to just talk, the ceremonies become the bottleneck.
Your Market Tells You Who You Are
Launched as an MVP shop. Clients stayed for 12 months. Eventually I listened to what the market was telling me about who I actually am.
Being Good to Be Referred
Split your business brand (clients) from personal brand (peers). Build referral relationships through authentic content, not polished marketing.
The Fourth Evolution of MVP
Frank Robinson invented MVPs in 2001. Eric Ries redefined them in 2011. AI is redefining them again in 2025.
If You Throw Away Your MVP Code, It Wasn't an MVP
6-day "MVPs" are prototypes disguised as products. Real MVPs use foundation-first architecture for extension, not throwaway code.
"It Works" Isn't Enough for Commercial Software
Vibe-coding excels for personal projects but creates dangerous technical debt in commercial products that require human-designed architecture and oversight
Domain Experts Still Need Tech Partners (Even in AI Era)
Industry experts know the problems; tech partners know how to build solutions. Why domain knowledge alone isn't enough to ship a software product.
Start Now; Iterate and Saturate Later
A project that survives starts with the core value, adapts to real feedback, and improves over time. Why launching early beats planning forever.
Deliver Ideas to Market with Applied R&D
Applied R&D allows entrepreneurs to innovate quickly, adapt to changing conditions, and solve real-world problems efficiently.
Workflow Automation Is Business' Superpower
Workflow automation transforms how businesses operate, replacing manual effort with technology to execute recurring tasks.
Smooth Operator of Software Development Lifecycle
Everything should have its place and time, and the engineering work should flow. How to structure delivery so nothing blocks and nothing drifts.