view the rest of the comments
news
Welcome to c/news! Please read the Hexbear Code of Conduct and remember... we're all comrades here.
Rules:
-- PLEASE KEEP POST TITLES INFORMATIVE --
-- Overly editorialized titles, particularly if they link to opinion pieces, may get your post removed. --
-- All posts must include a link to their source. Screenshots are fine IF you include the link in the post body. --
-- If you are citing a twitter post as news please include not just the twitter.com in your links but also nitter.net (or another Nitter instance). There is also a Firefox extension that can redirect Twitter links to a Nitter instance: https://addons.mozilla.org/en-US/firefox/addon/libredirect/ or archive them as you would any other reactionary source using e.g. https://archive.today . Twitter screenshots still need to be sourced or they will be removed --
-- Mass tagging comm moderators across multiple posts like a broken markov chain bot will result in a comm ban--
-- Repeated consecutive posting of reactionary sources, fake news, misleading / outdated news, false alarms over ghoul deaths, and/or shitposts will result in a comm ban.--
-- Neglecting to use content warnings or NSFW when dealing with disturbing content will be removed until in compliance. Users who are consecutively reported due to failing to use content warnings or NSFW tags when commenting on or posting disturbing content will result in the user being banned. --
-- Using April 1st as an excuse to post fake headlines, like the resurrection of Kissinger while he is still fortunately dead, will result in the poster being thrown in the gamer gulag and be sentenced to play and beat trashy mobile games like 'Raid: Shadow Legends' in order to be rehabilitated back into general society. --
Personally, I've had a pretty positive experience with the coding assistants, but I had to spend some time to develop intuition for the types of tasks they're likely to do well. Like if you need to crap out a UI based on a JSON payload, make a service call, add a server endpoint, LLMs will typically do this correctly in one shot. These are common operations that are easily extrapolated from their training data. Where they tend to fail are tasks like business logic which have specific requirements that aren't easily generalized.
I've also found that writing the scaffolding for the code yourself really helps focus the agent. I'll typically add stubs for the functions I want, and create overall code structure, then have the agent fill the blanks. I've found this is a really effective approach for preventing the agent from going off into the weeds.
I also find that if it doesn't get things right on the first shot, the chances are it's not going to fix the underlying problems. It tends to just add kludges on top to address the problems you tell it about. If it didn't get it mostly right at the start, then it's better to just do it yourself.
All that said, I find enjoyment is an important aspect as well and shouldn't be dismissed. If you're less productive, but you enjoy the process more, then I see that as a net positive. If all LLMs accomplish is to make development more fun, that's a good thing.
his has to be a bit, right?
Have you actually used these tools?
I find it helps to tell it I want very terse answers and to never respond with more than 1 or 2 steps at a time so I can tell it when it just crapped out a bunch of wrong info. That helps tremendously.
Definitely, I'd really love to see a visual tool like a scene graph where it could propose nodes and you could review and decide whether to add them or make changes.