Tuesday, October 12, 2010

Developers should know How, What and Why ... and when it is expected.

Are you working in one of those big companies which have slow processes and endless meetings? Are you told to work on a task to create an API but you don’t really know how it is going to be used? Are you just following the specifications to make it technically correct?

The knowledge of “How to do things” is the most valuable piece of information developers brings to teams. Sadly some people think that it is the only thing developer needs to know to pick him to the project.

We don’t think so.

Posted via email from markjeee.com

No comments: