/
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. 15.06.2022 at 01:04 am / Prepackaged Thought Cassettes
  2. 08.06.2022 at 04:13 pm / Counsel vs Client Perspectives
  3. 12.02.2021 at 12:55 am / 46 Simple Python Exercises/#10
  4. 10.01.2020 at 10:40 am / Learned Lumber
  5. 16.09.2019 at 10:32 am / Legal Practice & Taking From Software Best Practices
  6. 11.01.2019 at 06:39 pm / Clarity of Liskov
  7. 21.08.2018 at 10:59 am / Roses as Time
  8. 18.07.2014 at 12:00 am / Keep Learning Songs
  9. 03.01.2014 at 12:00 am / Write With Vigour
  10. 22.04.2012 at 12:00 am / Ludicrous Ace
© Wan Zafran. See disclaimer.