{"id":4189,"date":"2014-08-21T06:26:33","date_gmt":"2014-08-21T06:26:33","guid":{"rendered":"https:\/\/modeling-languages.com\/?p=4189"},"modified":"2014-08-21T06:45:56","modified_gmt":"2014-08-21T06:45:56","slug":"specialization-recruiters-developers","status":"publish","type":"post","link":"https:\/\/modeling-languages.com\/specialization-recruiters-developers\/","title":{"rendered":"Specialization is for recruiters, not developers"},"content":{"rendered":"

In his blog<\/a>, Matt Mullenweg (in case his name does not ring a bell, he is the co-founder of WordPress), reminds us of this great quote by Peter Merel<\/a>:<\/p>\n

A programmer should be able to fix a bug, market an application, maintain a legacy, lead a team, design an architecture, hack a kernel, schedule a project, craft a class, route a network, give a reference, take orders, give orders, use configuration management, prototype, apply patterns, innovate, write documentation, support users, create a cool web-site, email efficiently, resign smoothly. Specialization is for recruiters.<\/p><\/blockquote>\n

We could give arguments both to support and reject his statement (you’re more than welcome to share yours in the comments below) but just to give my 2 cents on this:<\/p>\n