Facebook's complexity will be its doom(forums.theregister.co.uk)
forums.theregister.co.uk
Facebook's complexity will be its doom
http://forums.theregister.co.uk/forum/1/2011/09/27/too_much_facebook/
3 comments
I posted the link to the comments because they're even better than the piece, which was not bad (and is linked at the top of the comments page).
The one titled "Too many developers" may be right: [...] My John Harvey-Jones fix: bin 90% of the programmers (pay them a million each), keep a small team to maintain and slowly extend the core, and leave it at that. After all, once your house is finished you don't keep the builders and architects on retainer, but you might hire in a decorator once in a while. [...]
Also, three slots down: I easily manage my facebook content by never reading it.
The one titled "Too many developers" may be right: [...] My John Harvey-Jones fix: bin 90% of the programmers (pay them a million each), keep a small team to maintain and slowly extend the core, and leave it at that. After all, once your house is finished you don't keep the builders and architects on retainer, but you might hire in a decorator once in a while. [...]
Also, three slots down: I easily manage my facebook content by never reading it.
This is a problem that afflicts many big companies that have large teams of product managers, designers and programmers. In such organisations, huge effort is spent constantly redesigning and tweaking software, for little obvious gain. It is action for action's sake.
Not long ago I worked on a contract with a big media company in the UK. During the whole three months I worked there, the company was working on what was a stopgap redesign of the website. By stopgap I mean, this was a design that was to appear between the current design and the "proper" redesign that was still being drawn up.
In truth, the "proper" design being drawn up will probably be just another stop gap. So I was probably working on a stopgap design between two other stop gap designs.
Funny thing is that everyone knew that having a stopgap design was a ludicrous idea but no-one had the power to prevent it happening.
I think this happens because big companies end up with big design and development teams. They can't easily get rid of these teams and it isn't acceptable to leave such a huge team idly doing nothing. So instead they set them to work on adding ever more features to the product.
A much better option, of course, would be to set them to work on a completely new product.