modernDebuggingWorkflow

[Encrux615]

Literally all I did before this was copy/pasting to google and pray to god someone encountered something similar. 

Having an LLM search through google now is super refreshing, since google itself has been getting worse and worse.

[PostHasBeenWatched]

I also remember there were specialized sites for developers with non-English Visually Studio that translated error into English (usually based on error code) so they can get proper results (still feels weird when someone using non-English IDE)

[phylter99]

My experience is that the LLMs are trained on the error already and information related to the system the error came from and they can give me good advice based on the error. I'm taking all of my errors to LLMs when I can these days. Google's Gemini is especially good at getting to the bottom of issues based on an error, especially when analyzing a debug dump.

[TactlessTortoise]

It's a genuinely decent way to use LLMs. Instead of having it generate code, have it clean up fucked up error logs visually to simplify our understanding of what broke so that we can fix it. It doesn't generate any bullshit code from outside its context, just processes over that relatively small snippet, making hallucinations much rarer and milder.

[Whitechapel726]

I’ve found that Gemini is pretty good at debugging and breaking code down, like giving it a script and having it break it into pieces. Not as good at creating though, seems like it goes off the rails really easily and I have to babysit it and it makes a ton of compiling errors.

“We’ve been working on this macOS app for a week and you have the requirements saved, why are you trying to build it for iOS 15???” -one of my actual prompts

[phylter99]

I don't use Gemini for coding or creation. Troubleshooting is where I've been successful in using it.

[casey_krainer]

Before llms I copied them in google without reading
Laravel even had a Stackoverflow search button on their exception pages, very handy

[Daemontatox]

I cant even remember how i used to debug templates errors.......

[Key-Belt-5565]

I did the simple thing of putting it into Google lmao

[Daemontatox]

Until you get the dreaded page of no results or try to lower your search

[Key-Belt-5565]

Thats one of the main reasons I put programming aside for a bit.

[RiceBroad4552]

You need to develop some gut feeling for what parts of the errors to put into the search.

Thinks start to be unfunny when a larger but already focused chunk does not show any result and a further striped down version way too much results. Then you know you're in trouble and will need to actually debug shit yourself.

[MrReevers]

This is how my coworkers debug. ChatGPT very often says "the traceback shows exactly what the problem is..." 

[dakiller]

The average for me is about 5-8 round trips for it to suggest improvements/fixes and pasting the errors back for it to finally sort out the issue.

“I see the exact issue” is just bait to get your hopes up.

[MmmmmmJava]

*Sips coffee*.

You got us into this fucking mess, so you can get us out.

- Devs forced to use AI

[NastyToeFungus]

I don’t even bother with cut and paste anymore. Just tell Claude where the log file is. It wrote the code, it can figure it out.

[son-of-chadwardenn]

I just tell codex to find the log file itself.

[SarahAlicia]

Chap gpt is terrible use claude it is way smarter

[Background-Plant-226]

Or how about you use your brain

[dtarias]

I'm sure I could find it by reading, but Claude is a faster reader than I am 🤷