Suggest they C suite be replaced with vibe managing.
Ask HN: Worth leaving position over push to adopt vibe coding?
71–80 of 99 posts
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#72The answers to stay until you find something else are correct.
I would also add that it's probably pretty easy to fake it - in my experience management, especially executive level, have no idea how things actually get done.
If they aren't prescribing a very specific workflow, you can create you own/install whatever tooling you want.
It's also worth pointing out - if you really are sufficiently experienced, these tools could prove to be a force multiplier and may actually be worth an investigation. You still have to review code and provide clear specifications in discrete, easily palatable chunks.
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#73I know with only 5 years experience this may not be obvious, but this is only the first of many “revolutionary” technologies making everyone around you lose their minds that you’ll have to deal with in your career. Like every other such technology, I recommend that you engage with it, understand it, relate that experience to what your employer does, and be the voice of knowledgeable pragmatism about where to use it.…
> I know with only 5 years experience this may not be obvious, but this is only the first of many “revolutionary” technologies making everyone around you lose their minds that you’ll have to deal with in your career. While this has some truth, the size of the current "revolution" makes all the others look tiny, especially in terms of how it affects a programmer's day job. Nor did most of those "revolutions" affect ev…
Were you around for the OOP craze? It definitely affected a lot of peoples’ day job. I mean, quite a few people use C++ and Java, no?
In my list I didn’t even mention the internet, the web, smartphones, and the cloud, all of which had a very broad effect on programming and programmers, and had similar top-down edicts from the C-suite, e.g., declaring you must be “all-in on cloud”. Turns out those things were indeed quite transformative, but now that the hype has dissipated somewhat, we’ve absorbed them into the toolkit and just proceed with the engineering.
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#74impressive that you're a senior engineer after only 5 years
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#75Earlier quoted context omitted.
> I know with only 5 years experience this may not be obvious, but this is only the first of many “revolutionary” technologies making everyone around you lose their minds that you’ll have to deal with in your career. While this has some truth, the size of the current "revolution" makes all the others look tiny, especially in terms of how it affects a programmer's day job. Nor did most of those "revolutions" affect ev…
Were you around for the OOP craze? It definitely affected a lot of peoples’ day job. I mean, quite a few people use C++ and Java, no? In my list I didn’t even mention the internet, the web, smartphones, and the cloud, all of which had a very broad effect on programming and programmers, and had similar top-down edicts from the C-suite, e.g., declaring you must be “all-in on cloud”. Turns out those things were indeed q…
I've been programming professionally since around 2003. I'd say I caught the late-stages OOP craze (or maybe after-craze) though not really the origin or rise of OOP. My first job was in a C++ codebase, and I spent a lot of time learning the OOP design patterns (or really, the "how do we make C++ behave well" patterns).
That said, the rise of OOP is probably measured in a decade or two. It eventually "spawned" whole new programming languages, that eventually got a lot of popularity. But this is over a much longer time-frame than how quickly we went from no such thing as AI coding, to (now) coding agents. It also didn't affect the entire industry in the same way - hell, some people were still writing assembly in the 80s as the OOP craze was winding up. I don't have actual stats, but I imagine coding agents are far more ubiquitious across far more industries/languages/stacks, for more quickly.
> In my list I didn’t even mention the internet, the web, smartphones, and the cloud, all of which had a very broad effect on programming and programmers,
The internet (or maybe the web) I'd say was probably the more transformative thing. Cloud affected a lot of things too but not quite as much and didn't make quite as big a difference to the day-to-day work. I deployed things pre-cloud and post-cloud (though honestly mostly during the early-stage cloud), and there wasn't such a big difference.
Look, at the end of the day you can't just compare AI to other technologies blindly and say "well they were big hypes, this is the same". By actually looking at what it's doing and how it's affecting things, it's fairly clear it has a much bigger impact on the day-to-day work of programming, as opposed to anything else you mentioned.
I'm not saying this is the end of development, for all I know this will mean more developers! But I think software development will look fundamentally different in 5 years in a way that is far more widespread than in any other of these changes.
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#76Knowing how to vibe code is a skill, though a lesser one than knowing how to design maintainable enterprise scale code that can be maintained and reused by others.
The vibe coding fad will pass, but building enterprise code and intelligently using AI for some tasks will make you better.
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#77Your concerns are completely valid - over-relying on AI for everything, especially deleting entire test files instead of debugging, will definitely stunt your technical growth and leave you managing a mess of generated code later. If leadership won’t listen to a balanced approach where AI handles boilerplate but humans handle complex logic and debugging, then it’s probably time to move on. With 5 years of experience, you’re in a good position to find a company that values proper engineering practices while still leveraging AI as a tool rather than a crutch.
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#78I know with only 5 years experience this may not be obvious, but this is only the first of many “revolutionary” technologies making everyone around you lose their minds that you’ll have to deal with in your career. Like every other such technology, I recommend that you engage with it, understand it, relate that experience to what your employer does, and be the voice of knowledgeable pragmatism about where to use it.…
> I’ve been through this with (including but not limited to) PCs, OOP, client-server, SOA, XML, NoSQL, blockchain, “big data”, and indeed, multiple definitions of “AI”. Turns out all but one of those were actually somewhat useful in the end, when applied properly, but they didn’t eliminate the industry. Just roll with it.
My non-technical boss was excited about some silver-bullet tech and I had to walk him through how these things play out.
I talked through most of the industry's overhyped "trends" since the 70's and describe the promise and the reality (very similar to your list).
I did mention that there were 2 trends that had more lasting general application (compared to things that were just another tool in the toolbox used for some situations):
1-Relational databases
2-Internet
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#79Earlier quoted context omitted.
> I know with only 5 years experience this may not be obvious, but this is only the first of many “revolutionary” technologies making everyone around you lose their minds that you’ll have to deal with in your career. While this has some truth, the size of the current "revolution" makes all the others look tiny, especially in terms of how it affects a programmer's day job. Nor did most of those "revolutions" affect ev…
Were you around for the OOP craze? It definitely affected a lot of peoples’ day job. I mean, quite a few people use C++ and Java, no? In my list I didn’t even mention the internet, the web, smartphones, and the cloud, all of which had a very broad effect on programming and programmers, and had similar top-down edicts from the C-suite, e.g., declaring you must be “all-in on cloud”. Turns out those things were indeed q…
> Were you around for the OOP craze?
In the early 90's I was working for a large ERP company that went all in on OOP and distributed objects.
I was talking to one of the guys from the new team they created to re-write the entire system and had an entertaining conversation:
Tech guy that had drunk the kool-aid (TGTHDTKA): "...and the objects can just automatically interact with each other, like I can drop this person object on the phone object and it just automatically makes the phone call to that person"
Me: "Uh, but you still had to write specific code that causes that interaction to occur, you can't just do that with objects that haven't agreed on how to communicate"
TGTHDTKA: "No, it's all automatic because a person has a phone number and a phone uses a phone number to make calls, so you don't have to code anything special"
etc.
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#80[dead]