Earlier quoted context omitted.
These are some of the things I do to try and get good results: - I prime the context of the LLM with any extra rules or instructions I want it to follow. - I also prime the context with every single file it needs to see in order to be able to do its job properly. Sometimes this can be two files but sometimes it can be 15 files. - I instruct the LLM in bullet point format for smaller edits. For larger edits I ask the…
This sounds less like engineering advice and more like spellcasting advice.
GPTs and Feeling Left Behind
171–180 of 226 posts
Re: GPTs and Feeling Left Behind
#172Earlier quoted context omitted.
This is for a janky backend admin panel, not a customer facing product. If it’s way better than it was before, which likely wasn’t responsive either, it’s a win. Understanding the context of a project is important.
And the tests? To me, if it was something important enough to have tests for in which case it's important to check the tests are valid so I'd have to review them
Re: GPTs and Feeling Left Behind
#173Earlier quoted context omitted.
I guess the main takeaway is that you don’t care about the quality of the generated code. The end result is all that matters. If I ask it to “add drag & drop”, I already know in my mind what the correct code should look like, because I’ve implemented it many times in the past. LLMs just never deliver the -code- that I want. The end result might look ok and the drag & drop will work, but the code will be atrocious and…
No, you’re being paid to deliver the product to the _company’s_ chosen standards, not yours. And in my experience, fast and cheap and cheerful is often exactly what they want. They’ll have changed their minds next week and want it all ripped out for something else anyway.
I do wonder if this is why there is such a gulf in LLM experience. If you're doing hardcore huge scale distributed systems then I can (maybe?) see why you'd think it is useless. However, that is very niche imo and most software dev work is some level (unfortunately) of virtually throwaway code. Of course, not all is - of all the ideas and experiments, some percentage is hopefully very successful and can be polished.
Re: GPTs and Feeling Left Behind
#174This is a really interesting signal to me. It's almost indisputable that you can get good results (I get good results pretty consistently) and so there's definitely something there. I don't think that folks who don't get good results are doing something "wrong" so much as not understanding how to work with the model to get good results.
If I was at a company building these tools, the author would be the person I'd want to interview. I doubt it's a skill issue. And it's definitely not user error. You can't sell a tool that is said to do something but the user can't replicate the result.
A tool that works but only after you've invested lots of time working to reverse engineer it in your head isn't a good tool, even if it's extremely powerful. The tool needs to be customizable and personalizable and have safety rails to prevent bad results.
Re: GPTs and Feeling Left Behind
#175I find myself on both sides actually. I did have some great luck producing quite useful and impactful code. But also lost time chasing tiny changes.
Re: GPTs and Feeling Left Behind
#176The author calling them "GPTs" suggests to me maybe not keeping up with the state of the art.
Re: GPTs and Feeling Left Behind
#177Earlier quoted context omitted.
Frontend dev for 13+ years here. In my experience it’s pretty bad at anything but basic frontend stuff. I’ve tried all the models, editors, Claude code etc. It’s constantly wrong about the simplest things. Just now it was hallucinating about CSS grid properties. I’m convinced that how good AI seems is inversely correlated to someone’s knowledge in that domain, as you also mentioned. Still super useful in my day to da…
I am very bad at frontend and I know frontend peeps keep saying claude/llms are bad at it, but now, for the first time in my 40 year career, I deliver frontend that are looking better and functioning better than whatever I see in hip products people 'designed with love in blah'. And our clients agree. If the css is correct or not, I don't know as I never really found the energy to learn it and now I don't need to and…
Re: GPTs and Feeling Left Behind
#178Earlier quoted context omitted.
> but it saved me from a bunch of tedious work that I don’t enjoy anyway. I play music and find practicing scales and learning music theory much more tedious and less enjoyable. I'd much rather be playing actual songs and having that flow where it is like the music is just coming out of me. But the reason I do the tedious stuff is because I don't get the latter stuff without the former. I can still learn to play song…
I'm having trouble with this sentiment, because most progress in programming environments involves eliminating and automating away drudgery. The analogy you're making to playing scales and learning music theory applies just as much --- maybe even more so --- to automated memory management!
Re: GPTs and Feeling Left Behind
#179Earlier quoted context omitted.
I'm having trouble with this sentiment, because most progress in programming environments involves eliminating and automating away drudgery. The analogy you're making to playing scales and learning music theory applies just as much --- maybe even more so --- to automated memory management!
Not necessarily disagreeing with your points, or the general argument, but I think the trade-offs and consequences of choosing a language with automated memory management are reasonably well understood, and manageable, but can we say the same about vast amounts of AI written code?
Re: GPTs and Feeling Left Behind
#180Earlier quoted context omitted.
Not necessarily disagreeing with your points, or the general argument, but I think the trade-offs and consequences of choosing a language with automated memory management are reasonably well understood, and manageable, but can we say the same about vast amounts of AI written code?
Automated memory management was fiercely debated at the time. So were high-level programming languages, so much so that Paul Graham was moved to write "Beating the Averages".