I'm self-taught, been doing this since I was 13. As far as how I am as a programmer, the way I turned out was rigid in my design patterns, but with I'm told un

I'm self-taught, been doing this since I was 13. As far as how I am as a programmer, the way I turned out was rigid in my design patterns, but with I'm told unusually readable code. My biggest sin is a lack of comments and documentation. I have a set of axioms/constructs that I use over and over again to build software in many languages. It's just dumb shit that I use like reaching for legos off the shelf. E.g. a class object owns a thread that is joined in the destructor for that object, lots of singletons, uniform indent/variable name style (Allman + PascalCase), lots of jump tables and hash maps, etc. So far in my career it hasn't been much of a limitation, but I suspect that I'll eventually run into an employer that needs me to be a bit more flexible. As far as competency, I can create pretty much anything except math-heavy stuff like 3D engines, crypto or compression algorithms, stuff like that. I'm awful at math, and that's one of my bigger regrets.