Fantastic article. The main problem in my view is that in most companies bad practices like vibe coding are being forced on developers by clueless upper management. It has gotten to the point that it doesn't matter if you write good code or not, if you don't use AI you are a bad developer.
Context is what sets apart a junior from a senior. You can be “senior” in terms of years of experience, yet still be “junior” when it comes to a specific system or company. You can make assumptions, but in most cases it takes months or even years to fully grasp a system.
When I started at the company where I work now, I admit I had no idea what to look for in terms of optimization. Doing a lot of research, even with the help of AI, only went so far. Firefighting my way through downtime taught me far more about what the system was capable of and what needed improvement.
That said, there were some parts that were “vibe-completed” (I know that word doesn’t exist), and I found them messy.
Fantastic article. The main problem in my view is that in most companies bad practices like vibe coding are being forced on developers by clueless upper management. It has gotten to the point that it doesn't matter if you write good code or not, if you don't use AI you are a bad developer.
Thank you! Glad it resonated
Context is what sets apart a junior from a senior. You can be “senior” in terms of years of experience, yet still be “junior” when it comes to a specific system or company. You can make assumptions, but in most cases it takes months or even years to fully grasp a system.
When I started at the company where I work now, I admit I had no idea what to look for in terms of optimization. Doing a lot of research, even with the help of AI, only went so far. Firefighting my way through downtime taught me far more about what the system was capable of and what needed improvement.
That said, there were some parts that were “vibe-completed” (I know that word doesn’t exist), and I found them messy.
Very well said 🙏