This has been what I've been seeing internally within $DAYJOB down to the split between vibe coding / vibe engineering / artisinally crafted code.
The gaps between engineers using the tools and those not are continuing to grow, and I'm curious to see what tools we get to use internally and what we can't... I've been able to demonstrate significant speed up in development time for features with certain tools but the amount of control some of these companies want in contracts are things the company hadn't seen before, and made it too conservative to go in on.
I also see this space changing so much that I don't particularly care for the tools for individuals now as much as I care about the way I share the workload with my team. I need a way to keep everyone up to date and reviewing code without getting brain drained as fast. Review fatigue is real, and it sucks. I haven't really found one that I've liked in that regard and one that a Fortune N company would want to go in on.
> The gap between engineers using the tools and those not are continuing to grow
Yeah, the ONLY place I hear this where it means "AI pushers are getting faster" is on this website, where half of your salaries depend on said belief.
When I go outside and talk to real engineers who I respect, in confidence and away from the suits forcing them to use AI, away from the hype of the industry telling them only one opinion is allowed, they all agree that "agentic coding" is simply not a meaningful improvement in quality or speed of publishing working software in the real world.
Maybe you like it, and that's fine. If you want to pay a lot of money for advanced IntelliSense and you can get your boss to do that for you, have fun. Just don't force it on me.
I don't believe you'll be meaningfully faster or produce better work than I can without the clanker's help.
If I get furloughed I'm going to get a new career working with my hands.
This has been what I've been seeing internally within $DAYJOB down to the split between vibe coding / vibe engineering / artisinally crafted code.
The gaps between engineers using the tools and those not are continuing to grow, and I'm curious to see what tools we get to use internally and what we can't... I've been able to demonstrate significant speed up in development time for features with certain tools but the amount of control some of these companies want in contracts are things the company hadn't seen before, and made it too conservative to go in on.
I also see this space changing so much that I don't particularly care for the tools for individuals now as much as I care about the way I share the workload with my team. I need a way to keep everyone up to date and reviewing code without getting brain drained as fast. Review fatigue is real, and it sucks. I haven't really found one that I've liked in that regard and one that a Fortune N company would want to go in on.
> The gap between engineers using the tools and those not are continuing to grow
Yeah, the ONLY place I hear this where it means "AI pushers are getting faster" is on this website, where half of your salaries depend on said belief.
When I go outside and talk to real engineers who I respect, in confidence and away from the suits forcing them to use AI, away from the hype of the industry telling them only one opinion is allowed, they all agree that "agentic coding" is simply not a meaningful improvement in quality or speed of publishing working software in the real world.
Maybe you like it, and that's fine. If you want to pay a lot of money for advanced IntelliSense and you can get your boss to do that for you, have fun. Just don't force it on me.
I don't believe you'll be meaningfully faster or produce better work than I can without the clanker's help.
If I get furloughed I'm going to get a new career working with my hands.
I was trying to create a spectrum of agentic tools ranging from "Vibe coding" to "Old-school craftmanship". This article did exactly that for me :)