Most active commenters
  • dotnet00(4)

←back to thread

152 points GavinAnderegg | 16 comments | | HN request time: 1.373s | 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 #
1. 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 #
2. marcosscriven ◴[] No.44458693[source]
What service was this?
replies(1): >>44458898 #
3. unshavedyak ◴[] No.44458837[source]
Honestly i'm less scared of claude doing something like that, and more scared of it just bypassing difficult behavior. Ie if you chose a particularly challenging feature and it decided to give up, it'll just do things like `isAdmin(user) { /* too difficult to implement currently */ true }`. At least if it put a panic or something it would be an acceptable todo, but woof - i've had it try and bypass quite a few complex scenarios with silently failing code.
replies(2): >>44459535 #>>44460387 #
4. dotnet00 ◴[] No.44458898[source]
Looks like I misremembered the shutting down bit, but it was this guy: https://twitter.com/leojr94_/status/1901560276488511759

Seems like he's still going on about being able to replicate billion dollar companies' work quickly with AI, but at least he seems a little more aware that technical understanding is still important.

5. apwell23 ◴[] No.44458971[source]
> around the peak of the vibe coding madness.

I thought we are currently in it now ?

replies(2): >>44459017 #>>44459022 #
6. 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 #
7. RexySaxMan ◴[] No.44459022[source]
Yeah, I kind of doubt we've hit the peak yet.
8. euazOn ◴[] No.44459337{3}[source]
The Karpathy tweet came out 2025-02-02. https://x.com/karpathy/status/1886192184808149383
replies(1): >>44460255 #
9. rufus_foreman ◴[] No.44459361{3}[source]
>> back in late 2024/early 2025

As an old man, this is hilarious.

replies(1): >>44462153 #
10. WXLCKNO ◴[] No.44459535[source]
This is by far the most crazy how thing I look out for with Claude Code in particular.

> Tries to fix some tests for a while > Fails and just .skip the test

replies(1): >>44461711 #
11. dotnet00 ◴[] No.44460255{4}[source]
...my perception of time is screwed... it feels like it's been longer than that...
replies(1): >>44462683 #
12. alwillis ◴[] No.44460387[source]
Sounds like a prompting/context problem, not a problem with the model.

First, use Claude's plan mode, which generates a step-by-step plan that you have to approve. One tip I've seen mentioned in videos by developers: plan mode is where you want to increase to "ultrathink" or use Opus.

Once the plan is developed, you can use Sonnet to execute the plan. If you do proper planning, you won't need to worry about Claude skipping things.

replies(1): >>44465830 #
13. Paradigma11 ◴[] No.44461711{3}[source]
Oh, but it will fix the test if you are not careful.
14. DonHopkins ◴[] No.44462153{4}[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.

15. oc1 ◴[] No.44462683{5}[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?
16. unshavedyak ◴[] No.44465830{3}[source]
I wish there was a /model setting to use opus/ultrathink for planning, but sonnet for non planning or something.

It's a bit annoying having to swap back and forth tbh.

I also find planning to be a bit vague, where as i feel like sonnet benefits from more explicit instructions. Perhaps i should push it to reduce the scope of the plan until it's detailed enough to be sane, will give it a try