Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
sodaTab451214dSounds like the dev is purposely trying to give you a bad name.
Watch your back.
> Watch your back
Nah, I think he was focused on a solution and not solving the problem (Solution finding vs. Problem solving). He's a big solution finder.
He had in his mind doing X was a solution with no facts to back it up. Like with some individuals, even having the facts cannot deter them from their course of action.
> He's a big solution finder.
To me he actually sounded pretty clueless. What he did is called "shotgun debugging". It's the worst unproductive, unprofessional way one can make changes.
> Like with some individuals, even having the facts cannot deter them from their course of action.
"Computer science" actually has many parallels to other sciences. One of them is starting with a hypothesis or goal and working with facts. You're not just aimlessly flailing around in hope that magically the right thing happens.
Off the top of my head, I can't even come up with *any* profession where that makes sense.
>To me he actually sounded pretty clueless
Troubleshooting complex issues is not in everybody's tool chest.
He has a Master's degree in software engineering, so he's not dim by any means. Makes me wonder if he lets his intellect get in the way. Ex. every complex problem requires an equal or even greater complex solution.
> Troubleshooting complex issues is not in everybody's tool chest
I agree, it certainly in mine wasn't when I was new. I learned to get help. He should try it, instead of flailing around aimlessly.
I don't even understand why this is a thing. "It doesn't work, I don't get it. I did something. Now it appears to work, and I still don't get it" - how is that in any way satisfying? How can that *not* feel completely wrong?