Developing Programmers .com

OK, I have not tested this so I don’t know if it will have the effect I hope, but I think it’s a neat idea. I think technical managers (and perhaps even each developer) should read the commit logs of their dev team. Not an in depth line by line check; perhaps scan for key points [...]

I recently picked up a copy of Mike Gunderloy’s book, “Coder To Developer”. The title grabbed me right away because it’s exactly what this site is about! Reading it in fragments of time between work and home commitments, I was actually excited to try things after reading each chapter. The bulk of the book is [...]

Phil Chu’s company, Technicat, is a consulting and development company specializing in net, educational, graphical and video game software.

Phil writes articles based on his experience and they’re available on his web site. One that’s particularly relevant to Developing Programmers is called “Seven Habits of Highly Effective Programmers”.

What are the others in your office working on at the moment?

We get quite a few things from our group meetings:

• At least an outline of what everyone else is working on and how they feel they’re going with it.
• Create a more close-knit group.
• Teach and Learn new skills.
• See the “Big Picture”.

Well not really. Today I’m exploring what kinds of rants experienced programmers have when they start working with someone new. There are a few reasons to do this and none are intended to offend. The main reason is that there are a few problems common to most new work places which can be identified and explored. This will make our readers at least fore-warned, and possibly arm them with ways to mitigate frustrations both from the perspective of a new programmer and also from the perspective of a team leader bringing someone new into a project.