Honestly, when I started dev the .net learning materials made me feel like an idiot. It seems like no one teaching it was willing to acknowledge how things were

Honestly, when I started dev the .net learning materials made me feel like an idiot. It seems like no one teaching it was willing to acknowledge how things were organized might have been stupid. Ergo, any confusion you had was a problem with you not the software. Cryptic errors for basic mistakes and the default option for it, at the time, visual studio's thousand menu's and buttons. "Oh you complete fool, you're using .net version 4.7 which is completely incompatable, go through 5 menus to download it. Hope you have the right version of Microsoft Silverlight!" I had to download like 10 versions of .net by the time I was done. A comparatively large amount of work for a hello world compared to almost any other choice for PHP or Python. And those had tutorials and text based environments were approachable. I definitely had issues with Apache's config hidden god knows where but learning how to search for config files was a skill I found far more useful than rooting around layers of menus while someone told me this was normal and, actually, good. If I had to choose a tech start for a start up MS still wouldn't be my first or second choice. I'm sure it works, but god that first year informed me it wasn't the community I wanted to be in.