eoin_murphy

I've been a big fan of emusic over the last few years. The subscription based model can be a bit awkward but it does encourage you to check out music you normally wouldn't listen to.

[edit] and they're all DRM free mp3 files

Alternatively; a two value system measuring popularity of the sentiment expressed and separately the quality of the post. So for example, a poorly written post with good ideas would be: legibility: -4, popularity: +4. This could be expressed as an rounded average or different users could filter by their own preference of legibility/popularity.

Of course this would all be a fairly major change to a system that isn't really broken so it's just speculative thinking on my part.

I can't remember where or when I heard it but I do recall that the number of accidents increase when the driver believes that they are good enough to avoid a crash through emergency manoeuvring. Safe driving is being aware and driving in such a was so as to prevent getting into that situation in the first place and if someone is trained to recover from a skid/drifting etc... then they're more likely to take risks.

That being said, if you can handle a car in emergency situations is a good thing as long as that doesn't encourage you to cause those situations.

Possibly to avoid the confusion of long and short number scales?

http://en.wikipedia.org/wiki/Long_and_short_scales

“It’s dangerous because it can create the illusion of understanding and the illusion of control,”

This would explain why it's so popular for middle management type meetings. People talking about things they don't understand but are responsible for have to give the impression that they're in charge.

Programming is a very wide field. In some cases creativity is a priority; the stereotype of the genius rock star developer hacking a business defining solution. For the majority of cases however, programming is all about communication with your team and with your stakeholders which is why core business hours are useful.

That's the problem with articles like these that they treat all programming equally. What's appropriate in one setting or for a particular developer is not appropriate for everyone.

That being said, if you can't allow your developers some flexibility and rely on them to behave like responsible individuals (re: internet access or time keeping) then the problem is with your staff and no amount of strict policies will fix that.

I still laughed at the article though.