← Back to post

Edit history

Most recent

It says a lot that you think a coding good practice like “documenting things in code” which is at the level of using descriptive variable and function names, should be in the same bucket as structural non-coding processes (which are often entire professionions or very senior professional branches) like Requirements Analysis or Technical Architecture, both highly-complex things (the latter being the very top in seniority of the technical career track) which are non-existent in a formal sense in improvisational (read: amateur as fuck) “programming” companies.

You’re making my point on the whole Dunning-Krugger thing.

Edited

It says a lot that you think a coding good practice at the level of using descriptive variable and function names in code, should be in the same bucket as structural non-coding processes (which are often entire professionions or very senior professional branches) like Requirements Analysis or Technical Architecture, both highly-complex things (the latter being the very top in seniority of the technical career track) which are non-existent in a formal sense in improvisational (read: amateur as fuck) “programming” companies.

You’re making my point on the whole Dunning-Krugger thing.

Edited

It says a lot that you think a coding good practice at the level of using descriptive variable and function names in code, falls in the same bucket as structural non-coding processes (which are often entire professionions or very senior professional branches) like Requirements Analysis or Technical Architecture.

You’re making my point.

Original

It says a lot that you think a coding good practice akin to using descriptive variable and function names in code falls in the same bucket as structural non-coding processes (which are often entire professionions or very senior professional branches) like Requirements Analysis or Technical Architecture.

You’re making my point.