We were working on a legacy C# project where the initial architecture was such that a RAKEFILE (ruby-make) was used to make a call to CSC.exe (the C# compiler).
"It's easy, we use Ruby to compile our C# so we can use wildcards .cs" (to say nothing of the problems caused by the loading of '.DLL' from the bin folder on app start)
Over time, when I was finally comfortable with the project, and after days of trial and error, I added CSPROJ files for each of the projects and was finally able to compile, run, and debug in visual studio.
When I tried to commit the CSPROJ files into git, he deleted them on the next commit.
When I asked why he removed the files is was a gongshow. "Why in hell should I allow you to put your shit in my repo?" He snapped.
When I explained that using intellisense & debugging were both incredibly valuable.
He countered with "why don't you just memorize the namespace (because that is what better programmers do)"
And "why don't you just use print statements to inspect values? (because that is what better programmers do)"
Skipping stack overflow is a similar sort of self hamstringing that I can't get behind.
Getting the job done quickly is part of what we're paid for. (Caveat* optimally quickly of course, there are plenty of times when taking a bit longer pays off in the long run)
Anyways, TL;DR skipping stack overflow is dumb.