[all2]

I'll follow on here because "don't plan too far in the future" is something I struggle with. My imagination is good, and so staying away from 'what could be' can be difficult at times.

---

My "plans" typically start with a broad vision. These ideas/visions come to me in day dreams as I ponder current tech or things that are interesting to me presently. These visions of what could be are typically not very revolutionary, and mostly just what ifs. Recently I've been pondering geographically bound search engines aimed at getting people back into the real world (I think this is a product in search of customers, tbh.), or a language server and dev tools for an esoteric scripting language, or a HN clone that serves specifically to catalog AI stuff.

From a broad vision, I make a small bulleted list of what a finished MVP might look like.

After the MVP I make/stumble-into an assessment of my skills and the skills required to complete the project. In my current project -- the aforementioned HN clone -- I found that I knew almost nothing about ASPNET web projects, then I found that I knew nothing about SPA+ASPNET, then I found I knew nothing about user authentication/authorization, and so on. This step is "pay down your debt of ignorance". It's kind of grindy, but I've been enjoying learning as I go. I've restarted my coding project about 10 times as I attempt to reformulate based on some new thing I've learned.

And then wash, rinse, repeat until I check all the boxes for the MVP. Then deploy and advertise/tell people about it.

[chrisdevs]

> From a broad vision, I make a small bulleted list of what a finished MVP might look like

I like this approach.

It's hard to project far into the future, especially when you've not gotten started.

Set a rough target, move towards, and continually adjust as you learn more.