{"id":80,"date":"2008-04-08T07:44:09","date_gmt":"2008-04-08T12:44:09","guid":{"rendered":"http:\/\/www.wiredprairie.us\/blog\/index.php\/archives\/80"},"modified":"2008-04-08T20:39:16","modified_gmt":"2008-04-09T01:39:16","slug":"what-does-it-take-to-make-a-rock-star-software-developer","status":"publish","type":"post","link":"https:\/\/www.wiredprairie.us\/blog\/index.php\/archives\/80","title":{"rendered":"What does it take to make a rock star software developer?"},"content":{"rendered":"

From ReadWriteWeb, “Top 10 Traits of a Rockstar Software Engineer<\/a>.”<\/p>\n

See the full post for the details of each point.<\/p>\n

    \n
  1. Loves To Code<\/li>\n
  2. Gets Things Done<\/li>\n
  3. Continuously Refactors Code<\/li>\n
  4. Uses Design Patterns<\/li>\n
  5. Writes Tests<\/li>\n
  6. Leverages Existing Code<\/li>\n
  7. Focuses on Usability<\/li>\n
  8. Writes Maintainable Code<\/li>\n
  9. Can Code in Any Language<\/li>\n
  10. Knows Basic Computer Science<\/li>\n<\/ol>\n

    What do you think about this list — does this list represent a rock star software engineer? I personally think the list is too slanted on “Agile” practices. What works for a web application software provider may not work well for an ISV or an enterprise developer in all cases.<\/p>\n

    I would have expected some mention of one of the classic books of software development to be mentioned, Code Complete: A Practical Handbook of Software Construction<\/a>\"\" by Steve McConnell.<\/p>\n

    Maybe the biggest issue I have with the list is that even if I checked all of these off while interviewing someone, I don’t know that I’d hire them. There are a few things I’d add for a developer to be a rock star. The following are a few ideas.<\/p>\n