Announcing my new book proposal:

📚 Working Effectively with Vibed Code

Based on the timeless classic Working Effectively with Legacy Code by Michael Feathers.

Chapter highlights:

• “The AI wrote this at 2am and I have no idea what it does”
• Characterization Tests: When you can’t ask the original author because there wasn’t one
• Breaking Dependencies on 47 npm packages you didn’t know you needed
• The Grand Question: “Is this a feature or a hallucination?”

Key techniques covered:

• The “just accept all suggestions” debugging method
• Sprout Class: When Claude adds 6 helper classes you didn’t ask for
• Wrap Method: Wrapping vibed code in try-catch and praying
• Extract Interface: Asking “what does this even do” as a service

Who is this book for?

Anyone who inherited a codebase where the author just says “Ask Claude if you don’t understand.”

The difference between legacy code and vibed code?

Legacy code: “The person who wrote this left 5 years ago”

Vibed code: “The person who wrote this is sitting right here and has no idea either”

Thoughts? 💭

On a serious note, I think it’s prime time to revisit this book. The techniques are still very useful if you need to fix bugs in vibed code.

#VibeCoding #LegacyCode #SoftwareEngineering #AI #TechHumor