Preferences

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.


> I've been able to demonstrate significant speed up in development time for features with certain tools

Curious to hear more about this. I can't help feeling such an attempt is fundamentally flawed just as software estimates are. Because you're never building the same thing twice.

That and the thing "I" build with AI is not the same as the thing I would have built myself. So you're comparing some lowest common denominator version of the software with an original work created by a human. Not once have I got an LLM to output code where I think that's what I had in my mind's eye when I wrote the prompt.
We used https://www.coderabbit.ai/ at my work to do reviews and I was a pretty impressed with it. Might be worth a look. Not affiliated in any way.
> 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’m still waiting for an article like this one:

https://jlouisramblings.blogspot.com/2013/04/acme-as-editor_...

It’s clear, informative, and even without reproducing it, you can still form an opinion about the tool.

All the AI pushers’s comments are either very vague or experiments whose sole quality is that it has been done with LLMs (often badly).

There’s been a few that show the Git history of a project that were (allegedly) fully written with an LLM. Not fully vibe coded, but in a meaningful amount.

This item has no comments currently.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal