User Tools

Site Tools


software_engineering:advice

The Zen of Python (in python, import this)

  • Beautiful is better than ugly.
  • Explicit is better than implicit.
  • Simple is better than complex.
  • Complex is better than complicated.
  • Flat is better than nested.
  • Sparse is better than dense.
  • Readability counts.
  • Special cases aren't special enough to break the rules.
  • Although practicality beats purity.
  • Errors should never pass silently.
  • Unless explicitly silenced.
  • In the face of ambiguity, refuse the temptation to guess.
  • There should be one– and preferably only one –obvious way to do it.
  • Although that way may not be obvious at first unless you're Dutch.
  • Now is better than never.
  • Although never is often better than *right* now.
  • If the implementation is hard to explain, it's a bad idea.
  • If the implementation is easy to explain, it may be a good idea.
  • Namespaces are one honking great idea – let's do more of those!

Jon's Advice for himself

  • Keep it professional, few people really care about you personally
  • Don't go on witch hunts and stay away from people who do
  • Accept blame and fix the problem
  • Don't freak just because the boss does
    • figure out what the boss really wants and get it
  • Document everything – if it gets bad even bathroom breaks
  • Be competent. If you're not, admit it and learn it – fast.
    • If you are act like it.
  • Where is the documentation? If it doesn't exist create it.
  • Make sure there is a process for everything done on a regular basis.
  • Ensure every process is thoroughly documented.
  • Avoid favoritism and the appearance of
  • Make clear standards, clearly communicate and enforce them

The Pragmatic Programmer Tips

The above link is sage advise and while numerous all should be followed.

software_engineering/advice.txt · Last modified: 2013/04/01 14:43 by lowcloudnine