|
|
|
|
|
|
by throwaway17_17
2315 days ago
|
|
|
If you find these flowcharts instructive, and I think that you are well founded in doing so, good on you. A majority of other comments seem to be of the opinion that pointing out the complexity of control flow generated by the constructs in a language is a negative. It certainly seems like the prevailing attitude is ‘if I can’t see it, it doesn’t exist.’ But you said you were working on game code, so I will encourage you to keep thinking about the complexity of the choices you make in which constructs to use and don’t buy into the thought that says performance implications are not a really concern. |
|
|
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.