Python is a very simple language compared to C#, C++, Java, etc. Last I checked, C# had over 30 Generics. Really, you only need the three that Python has: Dictionary, List, Queue and the C# ones are specialized variation on those. There is a lot of that, maybe called language bloat. I like C#, but could live with Python easily enough.

If there is, I'd like to check it out. I am planning to get a drone.

That's a bit overboard. I've seen some crazy stuff, but at least it had some rationality.

That's the one. Thanks a lot. The more I thought about it, the more I liked it. I did search on cognitive load and it didn't lead me to it.

I'm looking for an article I saw but did not keep. Every developer should read it. If you happen to know a link to it, I'd appreciate it. I logged into Github after not being there for a while and for some reason it took me to an article in a repository by someone with a name starting with a 'Z'. I was thinking "what is this" and had some trouble getting to my home page, so I read it. I didn't really register it at the time, but it was amazing. It largely said that almost everything we've been told about programming best practices leads to excessive "cognitive load", meaning our minds are getting kicked by the intellectual demands. I've known this for a while, especially with the demands of cloud, security and DevOps. I also liked it because it described practices I have done for decades, but never much admit to because they are not popular... I write really complicated stuff and need all the help I can get. Consider, if I'm right, it popped up because the Github folks, very smart people, though that developers should see it. I agree.

And that's a good question. A programmer can handle a fair amount of decently designed code without so much problem. Documentation helps and the first thing/best way to learn a new code base is to work through it, documenting as you go. I've managed to maintain something like 6 large projects, (2 WAN, 3 Intranet, cloud utility) and it wasn't real hard. On the other hand and this is where I got tripped up, there was a report that discussed that one of the hardest/most aggravating things for a developer was having to work with technologies that they didn't have the time (resources) to master. Then you are just outside of your comfort zone all the time. The article was in relation to DevOps. While it isn't hard to maintain a number of large code bases because you are comfortable using the same technology in them all, DevOps means that you are switching technologies, some of which may be unfamiliar, hard to master and ever changing. A heavy load of similar tasks (multiple large code bases, applications) is not so hard to manage. A load of many dissimilar technologies can be crushing. I loved that one CEO didn't want to come out and say that DevOps was hard to maintain. He said there was a bandwidth problem. There are many good developers, but not near as many that can handle the demands of DevOps. I can handle it, a bit uncomfortably if it includes much cloud, but in my long career I have only known a few developers that were comfortable in that storm. What I wonder though is for all his impressive mastery, was Bill (all bow down to Bill) going to be able to keep up with the changing technology.

I've read the other comments and I think there is a lot of great advice, especially getting to know the business. The funny thing is that my title is "Senior System Architect", yet most of that doesn't apply to me. What the people I have worked for see is that they can describe what they want and I can lay out a robust, Maintainable, complete system to do it. ... My niche is a bit odd though. I just do weird stuff no one else wants to try. My management likes me focused.