I'm currently of the opinion that humans should be laser focused on the data model. If you've got the right data model, the code is simpler. If you've got the relevant logical objects and events in the database with the right expressivity, you have a lot of optionality for pivoting as the architecture evolves.

It's about that solid foundation - and of course lots of tests on the other side.

My takeaway is that (presuming the argument is correct) that much of human striving is probably better described with specific words (as you suggested - joy, accomplishment, fulfillment, excitement, etc). For most of human history, most people probably didn't think "I want to be happy" but "I want to have a good partner", "I want a big family", "I want my crop to grow so I don't die."

I wonder how much unhappiness is caused by seeking a poorly-defined ideal of happiness.

The book was called "Power, Pleasure, and Profit: Insatiable Appetites from Machiavelli to Madison".

I think this gestures at a more general point - we're still focusing on how to integrate LLMs into existing dev tooling paradigms. We squeeze LLMs into IDEs for human dev ergonomics but we should start thinking about LLM dev ergonomics - what idioms and design patterns make software development easiest for AIs?

And of course, making it easier to rebase makes it more likely I will do it frequently.

And of course Grok's unhinged persona is... something else.

He sounds like a different person now.

I never understand this type of critique of Johnson. It's framed like he's suffering daily for his project, but the guy sounds happy as a clam - especially contrasted with his pre-Blueprint podcast with Lex Fridman.

Seems like he's doing something right.

And the best way I can describe why is that my code generally ends up with a few heavy functions that do too much; I can fix it once I notice it, but that's the direction my code tends to go in.

In my OCaml code, I would look for the big function and... just not find it. No single workhorse that does a lot - for some reason it was just easier for me to write good code.

Now I do Rust for side projects because I like the type system - but I would prefer OCaml.

I keep meaning to checkout F# though for all of these reasons.

But I would recommend just starting using Claude in the browser, talk through an idea for a project you have and ask it to build it for you. Go ahead and have a brain storming session before you actually ask it to code - it'll help make sure the model has all of the context. Don't be afraid to overload it with requirements - it's generally pretty good at putting together a coherent plan. If the project is small/fits in a single file - say a one page web app or a complicated data schema + sql queries - then it can usually do a pretty good job in one place. Then just copy+paste the code and run it out of the browser.

This workflow works well for exploring and understanding new topics and technologies.

Cursor is nice because it's an AI integrated IDE (smoother than the VSCode experience above) where you can select which models to use. IMO it seems better at tracking project context than Gemini+VSCode.

Hope this helps!