Programmers do that a lot? I always just start trying stuff in the command line until it works. It’s in research though, so maybe different from what is typical developer stuff?
“Fuck it, let’s try [blank]” is absolutely a valid debugging mechanism. Whether you get the same problems or fascinating new problems - you learned something about what’s wrong.
Now go take a walk and let your brain figure out what it means.
Programmers do that a lot? I always just start trying stuff in the command line until it works. It’s in research though, so maybe different from what is typical developer stuff?
“Fuck it, let’s try [blank]” is absolutely a valid debugging mechanism. Whether you get the same problems or fascinating new problems - you learned something about what’s wrong.
Now go take a walk and let your brain figure out what it means.
Yes! I got a new error!
Different error is definitely progress. Unless you get “1638394 rows deleted”.
That’s not an error though, so maybe that’s what you’re after!
The most valid learning/troubleshooting technique I’ve found is to push every button until something new happens. Seems to piss everyone else off tho
I hope you aren’t a pilot, or at least not my pilot.
I’m sure I can figure out what most of them do before we hit the gr . . . . .