top | item 46940506

(no title)

wvlia5 | 21 days ago

Sounds like you only tried it on small projects.

discuss

order

K0balt|21 days ago

That’s where it really shines. I have a backlog of small projects (-1-2kLOC type state machines , sensors, loggers) and instead of spending 2-3 days I can usually knock them out in half a day. So they get done. On these projects, it is an infinity improvement because I simply wouldn’t have done them, unable to justify the cost.

But on bigger stuff, it bogs down and sometimes I feel like I’m going nowhere. But it gets done eventually, and I have better structured, better documented code. Not because it would be better structured and documented if I left it to its ow devices, but rather it is the best way to get performance out of LLM assistance in code.

The difference now is twofold: First, things like documentation are now -effortless-. Second, the good advice you learned about meticulously writing maintainable code no longer slows you down, now it speeds you up.

ozozozd|21 days ago

I’ve developed a similar sense about maintainability becoming more important with LLMs. I have no hard data. Just feels that way.

Can you elaborate a little bit on how you get the LLM to produce maintainable code? Any tricks other than better prompting?

brookst|21 days ago

At work I use it on giant projects, but it’s less impressive there’s

My mold project is around 10k lines of code, still small.

But I don’t actually care about whether LLMs are good or bad or whatever. All I care is that I am am completing things that I wasn’t able to even start before. Doesn’t really matter to me if that doesn’t count for some reason.