The Million-Dollar Maybe
A major opportunity arrives while the product is still a proof of concept. Business sees a closing window; engineering sees what remains unproven.
- #Software Engineering
- #POC
- #Business
- #Risk

Articles on software, automation, AI, and lessons from real projects.
New here?
Three pieces that best explain what I write about.
A major opportunity arrives while the product is still a proof of concept. Business sees a closing window; engineering sees what remains unproven.

AI can generate code in minutes. Design patterns still help us decide whether that code is something we can safely change and own.

A viral warning says AI could end humanity. That is a possibility, not a prediction. Here is what would have to go wrong and what could stop it.

Choose a topic or browse everything.
I barely learned XML at university. Then I started working with legal documents and found it quietly carrying real work.
A major opportunity arrives while the product is still a proof of concept. Business sees a closing window; engineering sees what remains unproven.

AI can generate code in minutes. Design patterns still help us decide whether that code is something we can safely change and own.

A viral warning says AI could end humanity. That is a possibility, not a prediction. Here is what would have to go wrong and what could stop it.

When architecture, AWS, security, deployment, scaling, and production quietly land on your desk, the opportunity is real—but so are the boundaries you need.

The automation followed every documented rule. Then an Excel file nobody had mentioned revealed how the work actually happened.

How to protect your curiosity, growth, and potential when tools, access, experiments, and decisions are tightly controlled.

A practical way to decide which parts of a system need AI judgment and which parts should remain predictable, testable code.

After trying productivity apps, books, and advice that never stuck, I built a low-friction system with a pocket notebook and Excel.

A practical lesson in reliable document automation: keep AI focused on interpretation, then use code to validate and transform the result.

Why I’m documenting the systems I build, the problems I encounter, and the lessons worth remembering.

The newsletter
Get practical notes about software engineering, AI, and lessons from real projects. No spam, just the things worth sharing.
Unsubscribe anytime. Powered by Buttondown.