Hey there,

A lot of developers are wondering what to learn next now that AI is writing more code.

It's a classic case of the paradox of choice; with how fast tech moves, the options feel infinite.

What hasn't changed for me though is seeing software as a tool to solve a (business) problem.

So if/when you're wondering what to learn next, I would flip it around and ask what to build next.

Then base your learning on that goal; it will become more tangible, motivating and relevant.

As per last email about my Sun journey building a server log parser, since that experience I always think in terms of learning by building real-world things.

The nice side effect is that you'll end up with relevant artifacts for your GitHub portfolio as well.

Over the weekend I've built a new tool for this: Scope First

It's based on 3 articles I've written recently about this philosophy: design over code, building the smallest thing that works, and mind map before writing code.

If you're not sure what to invest your time in next, start with the "what to build next" question and give this tool a try.

I hope it helps you get clarity; let me know what you think.

No ideas yet? What about adapting this HN + Reddit idea scraper?

I get plenty of inspiration talking with people, reading books, but also by running a similar scraper every Monday.

What will you build next?

Bob