...but a perfect developer needs:

Describing the perfect developer's responsibilities, I forgot the preconditions and environment he (in rare cases she :-)) needs:

  1. Trust: is better, than thousands of specification pages or use cases. A good relation between the customer and developer or project manager and developer is the key to success. In general case it is better to define a minimal set of functional and nonfunctional requirements - the essential requirements, and let the developer to decide about the details. Short iterations and trust, are better than waterfall and a specification bible...
  2. Environment: hardware is cheap. Human resources are expensive. A developer should be able to choose a prefered hardware (even Mac, Linux, multiscreen etc.). A good hardware is good for motivation, and so also for the efficiency. From the overall perspective it is a lot cheaper to spend money on "cool" hardware, than saving money on RAM, CPU power or even design. I do not understand, why some companies still try to save money on hardware...
  3. Recognition: in case a project fails, managers try to find someone to blame. In case the project is successful there is no recognition or incentive. Sometimes a simple sentence: "Well done" would be appropriate...and also increase the productivity. Some managers still believe, that the real added value are the analysts, designers and architects. In their perspective developers are replaceable and can be easily outsourced (which is a very common fallacy :-)).
  4. Flexibility: especially in europe developers have to work in predefined working hours, which is mainly o.k. But sometimes (in the preproduction phase) we have to work more, than 10 hours which is often not allowed. It would be more efficient and also good for the motivation, working more for some period of time, and afterwards to take some days off.
  5. Good Teams: the best thing which can happen to you is: you are the less experienced developer in a team, so you can learn from the others. Even a motivated developer needs also motivated collegues. Otherwise  the project will be infected by the "work-to-rule" mentality, which does not very well work in the software development area.
  6. Motivation: books, workshops, magazines, conferences and trainings should be natural and matter of course. The costs for the above activities are nothing, comparing it to the increased motivation, and so also efficiency - so they pay off shortly (sometimes in weeks).
In case I forgot something, just comment this post.


Cloudy Jakarta EE and MicroProfile: Microservices, Clouds and Beyond Jakarta EE / MicroProfile airhacks workshops at MUC airport, Winter Edition

airhacks.fm the podcast:

Stay in touch: airhacks.news.

Comments:

Interesting projects too.. =]

Posted by felipe on December 04, 2006 at 02:34 PM CET #

Post a Comment:
  • HTML Syntax: NOT allowed
Online Workshops
realworldpatterns.com
...the last 150 posts
...the last 10 comments
License