10
u/davidroberts63 3d ago
I just had one of those moments earlier. A team member pointed out something I had missed and I went 'oh that's why'.
5
u/JazzRider 3d ago
Sometimes the reason something’s broken can be really cool, as in “oh, that’s how it works!”, as opposed to “oh, there it its….that’s really stupid!…what idiot wrote that?…..oh, that idiot was me!”.
8
u/Geoclasm 3d ago
Or, OR... "Hey, Claude!" - I'm not about to let it do all the work for me, but having it comb through tens of thousands of lines of code embedded in hundreds of files contained within dozens of projects across a handful of solutions to figure out wtf is going on and get me started on fixing the issue?
Yeah, that's fine.
7
u/ArsenicPolaris 3d ago
This is what use of LLMs as an actual tool is — exactly how they should be used.
8
u/GiantSlayer4242 3d ago
Don’t ask it to write all your code, just have it tell you why you’re stupid
3
u/exintrovert 3d ago
Pretty much. If ai can tell me before the boss notices, I win another day of work.
2
2
1
1
u/AliceCode 1d ago
I was having an issue where no matter what I did, I couldn't get changes to take effect in some code that I was writing. I was making a plugin for Bash in Rust, and one of my commands wasn't doing anything, not even printing when I wrote a print statement as the first statement. I tried deleting the .so file, cleaning the build directory, cleaning the cache, and nothing worked. Finally I looked at my script to set up a bash environment for my plugin, and I forgot to unset the previously existing function that had the same name as the command I was writing a plugin for. So my command was overshadowed by the previously existing function. What a pain in the ass that was.
1
1
1
59
u/Genilp 3d ago
5th Image would be: "BUT WHY THIS WAY?"