Other September 12, 2026 mixed ⇧ 2207 pts across 3 threads

Builders wrestling with whether to keep making things in the AI era

The 'Fuck it, make it anyway' post got real traction. The author describes a conversation with a developer who laid out three paths: use AI and lose the joy of building, compete without it and lose market position, or find a third way. The post ends with 'fuck it, make it anyway,' which sounds defiant but the thread underneath it is more complicated. Some people said AI has made building more fun than ever. Others said it has made the output feel hollow.

This thread connects directly to the 'AI and mathematics misalignment' post, which argues that solving problems is a proxy for the real goal of conceptual understanding, and that AI short-circuits that. The same argument applies to software: if the point of building is the understanding you gain, not just the artifact produced, then delegating to AI changes what the activity fundamentally is.

The counterpoint, and it was well-represented in the thread, is that AI is just another tool, and the 60-year-old who said Claude Code re-ignited his passion for programming is a real data point too. The split seems to track whether you value the process or the output. Both are legitimate. But founders need to be honest about which one they're actually in it for.


So what?

This is worth taking seriously as a retention and team culture question, not just a personal philosophy one. Developers who value craft and process are going to feel differently about AI-assisted work than those who are output-focused. If you are building a product or a team, knowing which type you have, and which type you are, matters for how you structure work and who you hire.

Read these