Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I see the SDE pushback on LLMs, but most of it is unfounded. Like any new tool, if used irresponsibly of course bad things can happen. Most of the backlash from devs seems rooted in:

1. It causes a step change in productivity for those that use it well, and as a result a step change in the expectations on productivity for dev teams. Folks simply expect things to be done faster now and that’s annoying folks that have to do the building.

2. It’s removed much of the mystique of dev. When the CEO is vibe coding legit apps on their own suddenly the SDE team is no longer this mysterious oracle that one can’t challenge or question because nobody else can do what they do. Now everyone can do what they do. Not to the same degree, yes, but it’s completely changed the dynamic and that’s just annoying some devs.

SDEs aren’t going away, but we will likely need less moving forward and the expectations on how long things take have changed forever. Like anything in tech we’re not going back to the old way so you either evolve or you get cycled out.

I also hear the “but LLMs only produce unrecognizable junk that one can’t maintain” angle, but that implies dev teams have been shipping beautiful artwork. Truth is most dev teams have been shipping undocumented fragile junk for years. While LLMs occasionally do odd things, in my experience LLM code is actually better documented and structured than what most dev teams produce and because of that it’s actually easier to hand off to others vs the typical codebase full of hacky workarounds and half-completed documentation.



> in my experience LLM code is actually better documented

Most LLM documentation is extremely poor unless you literally can’t understand code. It’s communicating obvious things that the code makes apparent. Good documentation covers what’s not obvious from reading the code. I’m amazed at how many devs think running Claude init is a good idea.

I’ve noticed a constant trend throughout my career that low performing devs generate and are impressed with this kind of documentation.

> and structured than what most dev teams produce

Left alone, LLM structure is terrible. Speed running the cheapest outsourced slop is not a good thing unless you’re already paying for outsourced slop. Huge win in that case.

LLMs are median equalizers. I think a large contingent of devs (especially given the money grab around 2021) are not that good, and LLMs really are a step improvement for them. I’m not denying there are use cases for competent devs, but so far that seems much narrower (albeit insanely impressive) than the benefit low performers (think) they receive. This fact is important to keep in mind when discussing the future of dev.


There is definitely a sort of undercurrent online to a lot of the claims and animosity towards anyone questioning LLMs or even exploring the downsides. Tons of anger and vitriol; on HN now even.

I get the sense a lot of new and middling engineers view this as some shortcut to success. Angry about getting passed on promotions, push back on their PRs, questioned why things are taking so long(hint: because they weren't actually putting in a full days work), or not making the grade for FAANG.

Now here is LLM and it's their chance to get stuff done without having to do much work. Don't need to have put in the work to learn and study. Now all those that were keeping them down before are the REAL problem because they are too slow, too out of date. What a gift! It's the great mediocracy uprising!

I haven't quite wrapped my head around it but there is definitely some weird social stuff going on.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: