Whether it’s an internal or external project, for coworkers or clients, the trap of being the boy who cried “wolf”, or in this case, the developer who cried “done,” is an easy one to fall into. The issue here, besides an elongated development time, is that this trap cuts at our credibility as programmers, even—and especially—when the circumstances are out of our hands. If you say it’s done, it’d damn well better be done. So, to avoid such an incredulous rap, try following these steps to make sure that projects actually get completed on time, the first time. (more…)