Hacker News new | ask | show | jobs
by locknitpicker 34 days ago
> It's literally text autocomplete. You can dress it up however you want but it takes input text and outputs the most likely next sequence.

Last year this level of ignorance and cluelessness was amusing. Nowadays it's just sad and disappointing. It's like looking at a computer and downplaying it as something that just flips switches on and off.
2 comments
siva7 34 days ago
Gitlab is looking to lay off people like him. All major tech companies are currently raiding to fire such employees.
link
LtWorf 34 days ago
Yeah they all want to fire the guys who can make sense of the mess the vibe coders are doing and try to stop it.

It will be interesting in the next few years. Assuming we won't be in the 3rd world war thanks to the USA and will have much bigger concerns.

link
locknitpicker 34 days ago
> Yeah they all want to fire the guys who can make sense of the mess the vibe coders are doing and try to stop it.

You're grossly inflating the level of contribution from your average software developer. Are we supposed to believe that the same people who generated the high volume of mess that plagues legacy systems are now somehow suddenly exemplary craftsmen?

Also, it takes a huge volume of wilful ignorance and self delusion to fool yourself into believing that today's vibecoders are anyone other than yesterday's software developers. The criticism you are directing towards vibecoding is actually a criticism of your average developer's output reflecting their skill and know-how once their coding output outpaces or even ignores any kind of feedback from competent and experienced engineers.

What I see is a need to shit on a tool to try to inflate your sense if self worth.

link
LtWorf 34 days ago
I've seen which developers became vibecoders. They were the people I'd have wished to get rid of.

The ones who never acknowledge a mistake even if the process is crashing; the ones who put "return true" in a test so that the test doesn't execute and will insist that you broke their code if you remove the return true and when the test actually runs it fails; the ones who read a blog post about some new thing and decide we need to do like that; the ones who will write code that fails and then be nowhere to be seen when there is customer support to do.

link
locknitpicker 34 days ago
> I've seen which developers became vibecoders. They were the people I'd have wished to get rid of.

Trying to portray everyone who ever used a tool as the incompetent cohort is an exercise in self-delusion.

link
LtWorf 34 days ago
Using AI ≠ vibecoding.
link
locknitpicker 34 days ago
> Gitlab is looking to lay off people like him. All major tech companies are currently raiding to fire such employees.

Gitlab has been strapped for cash and desperately seeking a buyer to cash out for years.

If anything, the LLM revolution represents an opportunity that Gitlab is failing to capitalize upon. They have a privileged position to develop pick axes for this gold rush, but apparently they are choosing to dismiss themselves from the race altogether.

Gitlab's decision is being taken in spite of LLMs, not because of them. Enough of this tired meme.

link
lynx97 34 days ago
Ahh, are we there yet? Has non-deterministic computer use eroded your mind so much that you are starting to question the binary system? You know, the insight that computers are something that flips switches on and off is rather old, and I have heard it uttered (although slightly humorously) several times already, nobody ever raising any eyebrow hearing it.
link