←back to thread

413 points martinald | 1 comments | | HN request time: 0s | source
Show context
DrewADesign ◴[] No.46199989[source]
As I said in a previous post:

I think the 90/90 rule comes into play. We all know Tom Cargill quote (even if we’ve never seen it attributed):

The first 90 percent of the code accounts for the first 90 percent of the development time. The remaining 10 percent of the code accounts for the other 90 percent of the development time.

It feels like a gigantic win when it carves through that first 90%… like, “wow, I’m almost done and I just started!” And it ‘is’ a genuine win! But for me it’s dramatically less useful after that. The things that trip up experienced developers really trip up LLMs and sometimes trying to break the task down into teeny weeny pieces and cajole it into doing the thing is worse than not having it.

So great with the backhoe tasks but mediocre-to-counterproductive with the shovel tasks. I have a feeling a lot of the impressiveness depends on which kind of tasks take up most of your dev time.

If your job is pumping out low-effort websites that are essentially marketing tools for small businesses, it must feel like magic. I think the more magical it feels for your use case, the less likely your use case will be earning you a living 2 years from now.

replies(3): >>46200091 #>>46207358 #>>46207851 #
adammarples ◴[] No.46207851[source]
One thing I've noticed is that Claude is so good at doing things that I've asked for, that later on I realise that I shouldn't have even been doing them because they're stupid or unnecessary but Claude was just cheerleading me on and emoji spamming tick marks so that I didn't realise there was very little purpose to the feature.
replies(1): >>46212638 #
1. DrewADesign ◴[] No.46212638[source]
Yeah once you start working at the feature level, you’re into product design, and that’s an entirely different realm of working that, IMO, shouldn’t even involve code. Even higher-level software design —e.g. broad stroke architecture like figuring out your data model and how it will be accessed— is better off being done before any significant amount of code gets written. Claude, et al will happily walk you straight off a cliff if you ask it to, and not having that stuff sketched out ahead of time is a most efficient way of accidentally doing that.