@JohnKoepi @ g on software engineering

My extended list of Joel’s 12 steps to better code

On Wednesday, August 09, 2000 famous Joel Spolsky wrote his great article The Joel Test: 12 Steps to Better Code. It is so amazing, this thing written more than 10 years ago and is popular right now as never before. All that stuff became part of best practices long time ago already. So many OSS systems were created to help you follow this hints along your developing process.

So, working here in Russia, i decided to extend this list to help backend developers to rate their workplaces and companies they are tend to work at.

The Joel Test extended

  1. Do you use source control?
  2. Can you make a build in one step?
  3. Do you make daily builds?
  4. Do you have a bug database?
  5. Do you fix bugs before writing new code?
  6. Do you have an up-to-date schedule?
  7. Do you have a spec?
  8. Do programmers have quiet working conditions?
  9. Do you use the best tools money can buy?
  10. Do you have testers?
  11. Do new candidates write code during their interview?
  12. Documentation you do hallway usability testing?


  1. Do you buy best hardware for your linux developers? (i7 4K, 32GB, SSD, …)
  2. Do you buy Mac Book Air for your developers (in addition to default workstation)?
  3. Do you buy big table and a good chair for your developers?
  4. Do you buy at least 2 24 inch monitors (and holder) for your developers?


  1. Do you buy books?
  2. Do you send your developers to conferences?
  3. Do you learn / use modern technology stack in your field of area (scala)?
  4. Do you know / use something but OOP?


  1. Do your developers write tests?
  2. Do you use static code analysis?
  3. Do you use code review?
  4. Do you do code refactoring?


  1. How big is your team?
  2. How do you resolve conflicts with a team members?
blog comments powered by Disqus