Tuesday, November 20, 2012

Developers's time of permanency is 15 years?

This article is not about performance of PHP, but more about performance of developers in general.
A nice article from golem.de claims that the developers's time of permanency is - exactly - 15 years.

The main facts of the article:
  • developers have abrasion like professional athletes

    No: Developers don't require fast running, much muscle power or intensive training. Of course, getting older does not mean getting healthier, but health care improves every year and people are getting older and older. The key success factors are more talent and motivation than age. Also, older athletes produce more money with marketing than younger ones.

  • developers at the age of 20 bring more money than older developers

    Yes, if the business is selling developers by hour/day and quality (number of bugs, wrong architecture decisions, usability, performance) does not matter. Young developers without a final degree and without working experience normally have lower salaries.

    No in all other cases. The TCO of a developer looks more like this:

    salary + bugs + hardware + wrong architecture decisions
    + unneeded features produced + further education
    - revenue from creating products
    Since wrong architectures cost millions and revenue from creating products brings millions, the experience of a developer is more important than the salary.
    Another factor are marketing costs: Here in Germany, 2 spots on television with 1 minute cost more than a developer in the whole year (see zdf, page 13). Creating a bad or slow landing page is more expansive than hiring a more experienced developer. Therefore, younger developers might have lower salaries, but cost more in total.

  • developers get unnecessary if they don't acquire higher qualifications

    Yes: Compared to ten years ago, programming languages had less features, there were less frameworks, browsers had less features, there were no mobile devices, frontends were different, backends had more low-level programming. But it is easier for an older developer to learn the new things coming in than for a young developer to learn all the stuff.

    No, if developers enhance themselves, but the job remains the same. In this case, higher qualification does not matter.

Looking at piano players like Wilhelm Kempff, you see that even old guys are able to play at a very high level. And writing code is less demanding than hitting all keys correctly in real-time with the right strength and rhythm on a piano.

No comments:

Post a Comment


performance (23) benchmark (6) MySQL (5) architecture (5) coding style (5) memory usage (5) HHVM (4) C++ (3) Java (3) Javascript (3) MVC (3) SQL (3) abstraction layer (3) framework (3) maintenance (3) Go (2) Golang (2) HTML5 (2) ORM (2) PDF (2) Slim (2) Symfony (2) Zend Framework (2) Zephir (2) firewall (2) log files (2) loops (2) quality (2) real-time (2) scrum (2) streaming (2) AOP (1) Apache (1) Arrays (1) C (1) DDoS (1) Deployment (1) DoS (1) Dropbox (1) HTML to PDF (1) HipHop (1) OCR (1) OOP (1) Objects (1) PDO (1) PHP extension (1) PhantomJS (1) SPL (1) SQLite (1) Server-Sent Events (1) Silex (1) Smarty (1) SplFixedArray (1) Unicode (1) V8 (1) analytics (1) annotations (1) apc (1) archiving (1) autoloading (1) awk (1) caching (1) code quality (1) column store (1) common mistakes (1) configuration (1) controller (1) decisions (1) design patterns (1) disk space (1) dynamic routing (1) file cache (1) garbage collector (1) good developer (1) html2pdf (1) internationalization (1) invoice (1) just-in-time compiler (1) kiss (1) knockd (1) legacy code (1) legacy systems (1) logtop (1) memcache (1) memcached (1) micro framework (1) ncat (1) node.js (1) openssh (1) pfff (1) php7 (1) phpng (1) procedure models (1) ramdisk (1) recursion (1) refactoring (1) references (1) regular expressions (1) search (1) security (1) sgrep (1) shm (1) sorting (1) spatch (1) ssh (1) strange behavior (1) swig (1) template engine (1) threads (1) translation (1) ubuntu (1) ufw (1) web server (1) whois (1)