/
29.01.2020 at 10:48 am
Cuttings

Code & Shame

Be critical with your code, and sometimes yourself.

... There is a difference between saying "an idiot wrote this code" and "this code is crap". The comic is the latter. On purpose, I presume. Attacking the author is unlikely to have any benefits, but it should be possible to strongly criticize the code itself. In reality, many authors can't separate themselves from their work, but the ability to do so is a valuable asset.

Left to themselves, most people have a tremendous ability to ignore their flaws, and it hampers their growth. A bit of shame is often a positive motivation. I am ashamed of a lot of code I wrote last year. I have reasons why it is the way it is, some of which are defensible, but some are just "WTF was I thinking?" If you don't have nagging bits of guilt about your recent body of work, it might well be a benefit for someone to point out problems in terms that break through your defenses.

I would be happy if someone tore into everything I wrote for the Oculus Mobile SDK. I'm sure most of it would be just me nodding my head and agreeing, but I bet I would learn something from it, and it would influence my future work.


Filed under:
#
Words: 221 words approx.
Time to read: 0.88 mins (at 250 wpm)
Keywords:
, , , , , , , , ,

Other suggested posts

  1. 11.06.2022 at 07:24 am / Vampiric Pathology
  2. 08.06.2022 at 04:13 pm / Counsel vs Client Perspectives
  3. 03.01.2020 at 10:46 am / Git for Legal Practice
  4. 03.01.2017 at 12:00 am / Debugging: Twice As Hard As Writing Code
  5. 08.02.2016 at 12:00 am / Eye to Eye (Jonathan Young's Version)
  6. 06.09.2015 at 12:00 am / Big Illegal Guns
  7. 19.07.2015 at 12:00 am / Deadened Demonyms
  8. 20.06.2015 at 12:00 am / Mike Tyson on (His) Lawyers
  9. 29.11.2013 at 12:00 am / ガラケー Garakei Evolution
  10. 21.07.2012 at 12:00 am / Hunted By GLaDoS
© Wan Zafran. See disclaimer.