The spectrum framing is useful. Most of the conversation treats vibe coding and disciplined engineering as a binary but it's really a dial you adjust depending on what you're building. For throwaway prototypes, full vibes. For anything that needs to survive contact with users, you need the patterns. Simon Willison's new agentic engineering guide codifies exactly where that line sits. His take on when to trust agents with implementation versus when to keep your hands on the wheel is the clearest I've seen. Covered it here: https://reading.sh/simon-willisons-playbook-for-working-with-coding-agents-d56ccd3f959f?sk=702022f0c1f1ad123686a987c90676bd
Vibe coding is good for MVP/prototype but when something goes wrong in production AI cannot save you in current scenario you need engineer and there are lot of errors as well.Depending on Pros is better idea after building Prototype rather than vibe coding as it is not consistent but Frontend/UI is way better by AI.
Truly insightful, this clearly separates fleeting speed from lasting skill. Appreciate the clarity on what actually makes an engineer valuable with AI.
I talk about the latest AI trends and insights. If you’re interested in practical ways to work smarter with AI and amplify your engineering or creative workflow, check out my Substack. I’m sure you’ll find it very relevant and relatable.
Yes! I cover technical content regularly. Practical AI strategies, workflows, and insights that engineers and creators can actually apply. Appreciate you checking it out!
The spectrum framing is useful. Most of the conversation treats vibe coding and disciplined engineering as a binary but it's really a dial you adjust depending on what you're building. For throwaway prototypes, full vibes. For anything that needs to survive contact with users, you need the patterns. Simon Willison's new agentic engineering guide codifies exactly where that line sits. His take on when to trust agents with implementation versus when to keep your hands on the wheel is the clearest I've seen. Covered it here: https://reading.sh/simon-willisons-playbook-for-working-with-coding-agents-d56ccd3f959f?sk=702022f0c1f1ad123686a987c90676bd
Yes to all of this! I can vibe code, but the moment I want something to be real, I’m calling in the pros (the engineers).
Vibe coding is good for MVP/prototype but when something goes wrong in production AI cannot save you in current scenario you need engineer and there are lot of errors as well.Depending on Pros is better idea after building Prototype rather than vibe coding as it is not consistent but Frontend/UI is way better by AI.
Very powerful ending and a great read all together. Thank you for sharing!
Truly insightful, this clearly separates fleeting speed from lasting skill. Appreciate the clarity on what actually makes an engineer valuable with AI.
I talk about the latest AI trends and insights. If you’re interested in practical ways to work smarter with AI and amplify your engineering or creative workflow, check out my Substack. I’m sure you’ll find it very relevant and relatable.
Glad that u liked it.Thanks for reaching out and commenting.
Will checkout your substack, do u post technical content !
Yes! I cover technical content regularly. Practical AI strategies, workflows, and insights that engineers and creators can actually apply. Appreciate you checking it out!