I copy code from Stackoverflow and still call myself a developer.
But it’s not what you think. Just knowing C# and the .Net framework is no longer enough.
For example, I recently couldn’t get HttpClient working when compiled in Release, Configuration manager was having trouble with both appsettings and web.config in the same project, and shadowCopyBinAssemblies=”True” seems downright broken (causing issues for xcopy IIS deployments). All tracing back to changes introduced in .Net Core / 5.0 from what I can tell.
It’s unusual not to find the same problem already posted on Stackoverflow. But what I find most useful, is the _date_ stamp on the posts, letting me see when the issue first cropped up, and often how it has changed over subsequent .Net releases. I can get the full context to the issue at hand and make a good determination as to which of the many answers, maybe most relevant to my current stack.
Just knowing a language back to front is no longer enough. But I do miss the days when all you needed was “The C Programming Language” by Kernighan and Richie.
Frank Ray & Associates is a software engineering consultancy that builds high quality software for businesses.