pull down to refresh

It's interesting that I prefer choosing between the 3 implementations and prefer wishy washiness. At root, I think I don't like having to (or struggle to) adjust my trust levels. I'd much rather figure something out on my own if I have to.
That's interesting.
Maybe it's because my trust level in the AI is already low, so I don't expect to actually use any of its implementations (at least word for word). I'm mainly using it to get a sense of "where in the code should I be looking", and "what's the general idea for the solution?" as a quicker alternative than reading and crunching all the code in my own mind.
I'm still gonna crunch enough code to understand what's going on, so the purpose of the AI is more like "find me the best jumping off point"
reply
Do you feel that these suggestions help you understand the codebase better?
reply
Usually yes. So far they've done a decent job in finding the right parts of the code to be looking at, and their suggested solutions are usually on the right track (but usually not something you can just copy paste)
reply
30 sats \ 0 replies \ @optimism 6h
That's cool. I will actually try this when I go work on some software I have never worked on before - have multiple of these on the non-immediate todo list.
reply
100 sats \ 0 replies \ @optimism 7h
Yeah, I rarely use it for code except when I try something new to see what it can do. But then, I've spent 95% of my time reviewing other people's code the last decade, so for me it's not much use in production. I've tried doing AI-enhanced code review where I feed it the resulting code of a diff, but it didn't really work well for me on c++ code. I'm still a skeptic when it comes to production usage really. Maybe autocomplete, but the one in my rich-ish text editor works fine for me.
reply