←back to thread

152 points GavinAnderegg | 8 comments | | HN request time: 1.038s | source | bottom
Show context
iamleppert ◴[] No.44457545[source]
"Now we don't need to hire a founding engineer! Yippee!" I wonder all these people who are building companies that are built on prompts (not even a person) from other companies. The minute there is a rug pull (and there WILL be one), what are you going to do? You'll be in even worse shape because in this case there won't be someone who can help you figure out your next move, there won't be an old team, there will just be NO team. Is this the future?
replies(7): >>44457686 #>>44457720 #>>44457822 #>>44458319 #>>44459036 #>>44459096 #>>44463248 #
dotnet00 ◴[] No.44458319[source]
Probably similar to the guy who was gloating on Twitter about building a service with vibe coding and without any programming knowledge around the peak of the vibe coding madness.

Only for people to start screwing around with his database and API keys because the generated code just stuck the keys into the Javascript and he didn't even have enough of a technical background to know that was something to watch out for.

IIRC he resorted to complaining about bullying and just shut it all down.

replies(3): >>44458693 #>>44458837 #>>44458971 #
1. apwell23 ◴[] No.44458971[source]
> around the peak of the vibe coding madness.

I thought we are currently in it now ?

replies(2): >>44459017 #>>44459022 #
2. dotnet00 ◴[] No.44459017[source]
I don't actually hear people call it vibe coding as much as I did back in late 2024/early 2025.

Sure there are many more people building slop with AI now, but I meant the peak of "vibe coding" being parroted around everywhere.

I feel like reality is starting to sink in a little by now as the proponents of vibe coding see that all the companies telling them that programming as a career is going to be over in just a handful of years, aren't actually cutting back on hiring. Either that or my social media has decided to hide the vibe coding discourse from me.

replies(2): >>44459337 #>>44459361 #
3. RexySaxMan ◴[] No.44459022[source]
Yeah, I kind of doubt we've hit the peak yet.
4. euazOn ◴[] No.44459337[source]
The Karpathy tweet came out 2025-02-02. https://x.com/karpathy/status/1886192184808149383
replies(1): >>44460255 #
5. rufus_foreman ◴[] No.44459361[source]
>> back in late 2024/early 2025

As an old man, this is hilarious.

replies(1): >>44462153 #
6. dotnet00 ◴[] No.44460255{3}[source]
...my perception of time is screwed... it feels like it's been longer than that...
replies(1): >>44462683 #
7. DonHopkins ◴[] No.44462153{3}[source]
We can't bust code like we used to, but we have our ways.

One trick is to write goto statements that don't go anywhere.

So I ran a bourn shell in my emacs, which was the style at the time.

Now just to build the source code cost an hour, and in those days, timesheets had hours on them.

Take my five hours for $20, we'd say.

They didn't have blue checkmarks, so instead of tweeting, we'd just finger each other.

The important thing was that I ran a bourn shell in my emacs, which was the style at the time...

In those days, we used to call it jiggle coding.

8. oc1 ◴[] No.44462683{4}[source]
all our perception of time seems messed up. claude code came out like 4 months ago and it feels like we had been using this thing for the past years. it feels like every week there is a new breakthrough in ai. it has never been more soul draining than now to be in tech just to keep up to be employable. is this what internet revolution felt like in the early 90s?