3 Comments
User's avatar
Drew Hoskins's avatar

Thanks, Gergely, for posting, and thanks to everyone for reading and sharing!

I didn't write this book because of AI--many of the topics, like errors and warnings, I've been itching to cover for years. But the AI transition *is* likely why it was chosen for publication. This is a very nervous moment in the history of software engineering as the role gets redefined, and amid all the fun engineers are having coding with Claude et al., I think individual contributors feel anxiety--am I ready for what's coming? As a lifelong IC, and in the spirit of Kent Beck's mission to "help geeks feel safe in the world," I hope this helps.

I want this to be a dialogue, not just a book. I'd love to hear from folks on Substack or LinkedIn--stories, questions, topic suggestions, or feedback about the content.

Adham Bishr's avatar

@drew Definitely getting this book. Would love for you to analyze more real world use cases (the Stripe example of using test more than production was a very interesting example).

Also really liked the exercises.

Samuel Path's avatar

Such skills are becoming ever more important as AI agents are becoming better in their technical skills. Product thinking can definitely help future-proof our careers as software engineers.