[inetknght]

> you said you were working on game code

Actually, I didn't. I said I wanted to "up my game" which is a phrase commonly meaning "to get better". Said another way: I needed to get better at describing code to management.

> I will encourage you to keep thinking about the complexity of the choices you make in which constructs to use

Indeed, management generally wants simpler code even at the cost of performance. Simpler code generally translates to cheaper developers and cheaper maintenance.

> don’t buy into the thought that says performance implications are not a really concern

I actually write DNA analysis software. Performance implications definitely are a concern. :)

But performance is useless if I'm the only developer who understands how it all comes together (eg, high bus factor). So I've been writing a lot of documentation to that end, from file-level down to the systems-level and bit-level descriptions. I really would like better support for diagrams in markdown.