Questions Five Ways - Overview

Digg thisor Tweet it

I think one of the better ideas I've had on this blog is my 'Questions Five Ways' series. For each post, I'll ask a guiding question of five leading hackers, some from the Ruby community and some from outside it. My intent is to build some great resources for everyone who's trying to become a better programmer. If you'd like some more details about the seris, you can take a look at the Questions Five Ways Introduction.

As the series grows, I'm going to list all the entries here.

• Which 2-3 languages/approaches should a programmer be studying to move toward a more concurrent future? (May 13, 2009)
• Why is code reading so important to a programmer, and how can we become better at it? (May 20, 2009)
• What is the right interplay between testing code (unit test and the like) and static code analysis (lint, Reek, and their ilk)? (May 27, 2009)
• What makes a programmer a good (or great) programmer? What should Rubyists be doing to become better programmers? (June 3, 2009)
• What is the relationship between testing and code reading when dealing with legacy code, and how can we use the two processes to improve each other (and the code we're dealing with)? (Jun 10, 2009)

It might also be interesting to list who's taken part in these discussions:

• Venkat Subramaniam (@venkat_s)
  • Concurrency
  • (not part of questions five ways — Interview about 'Programming Scala')
• MenTaLguY @mentalguy)
  • Concurrency
• Tony Arcieri (@bascule)
  • Concurrency
  • (not part of questions five ways) — Interview about Reia)
  • (not part of questions five ways) — Interview about Revactor)
• Steve Yegge
  • Code Reading
• James Gray (@JEG2)
  • Code Reading
• Rick DeNatale (@RickDeNatale)
  • Code Reading
• Diomidis Spinellis (@DSpinellis)
  • Code Reading
• Don Stewart (@donsbot)
  • Code Reading
  • (not part of questions five ways) — Interview about 'Real World Haskell')
• Kevin Rutherford (@kevinrutherford)
  • Testing
  • Ruby Refactoring Workbook Interview — (not part of questions five ways)
  • Reek For Ruby Rocks — (not part of questions five ways
• Andy Lester (@petdance)
  • Testing
• Kay Johansen (@utahkay)
  • Testing
• Russ Olsen (@russolsen)
  • Testing
  • RubyNation Interview: Russ Olsen — (not part of questions five ways
  • Russ Olsen Interview — (not part of questions five ways
  • Design Patterns in Ruby, a Review — (not part of questions five ways)
• Robert Klemme
  • What makes a programmer a good (or great) programmer? What should Rubyists be doing to become better programmers? (June 2, 2009)
• Gregory Brown (@seacreature)
  • What makes a programmer a good (or great) programmer? What should Rubyists be doing to become better programmers? (June 2, 2009)
  • (not part of Questions Five Ways) Ruby Best Practices mini-Interview 1
  • (not part of Questions Five Ways) Ruby Best Practices mini-Interview 2
  • (not part of Questions Five Ways) Ruby Best Practices mini-Interview 3
• Lakshan Perera (@laktek)
  • What makes a programmer a good (or great) programmer? What should Rubyists be doing to become better programmers? (June 2, 2009)
• James Britt (@jamesbritt)
  • What makes a programmer a good (or great) programmer? What should Rubyists be doing to become better programmers? (June 2, 2009)
• Cory Foy ((@cory_foy)
  • (June 10, 2009)
• Dave Thomas (@PragDave)
  • (June 10, 2009)
• Antonio Cangiano (@acangiano)
  • (June 10, 2009)
• Tim Bray (@timbray)
  • (June 10, 2009)