Leading by Bleeding
Tonight Chad Fowler posted on twitter an interesting comment and link to a blog post by David Copeland and his take on his knowledge of technologies; from the bleeding edge to those “on the way out”. His post was inspired by an exercise in Chad’s new book, The Passionate Programmer, which is on my list of books to read in the very near future.
My initial reaction was three fold:
- Annoyance that I couldn’t mark more of them in yellor or green.
- Happiness that I had at least heard of or had some very basic knowledge in almost all of them.
- Curiosity on how he had picked his list, why he had not included some others, and why he had placed some where he had.
I intend to fill out a similar personal survey tomorrow which I will post … but until then I leave this question to anyone who reads this: What would yours look like, and what things would you remove/add/move if you were doing it?
Obviously any such list could contain any number of items depending on your background and scope (what do we include? languages? ideas? patterns?) but a few that I thought were missing off of the top of my head were:
- Adobe AIR / Flash
- RCP applications
- Web services
- Functional programming
- Agile development practices (Lean/XP/Scrum)
- Hibernate or other ORMs (e.g. ActiveRecord, iBatis, etc)
- UAT libraries / tools (e.g. Selenium, WebDriver, WebRat, Wati[R|J|N])
It really is hard to know where to stop. Quickly it feels like a corporate skills inventory list that eveyone updates when they are hired and then never again. We will see what the guys at work can come up with tomorrow and then see what my personal sheet looks like. If you do one of your own, can think of something thats missing or just have a thought … please leave a comment.
At the very least, it was a very thought provoking post.