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.
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.