News for hackers. Stuff that matters.
Re:Developer productivity: The art of saying no by ryandrake on Saturday March 14, 2015 @12:58PM (#9203259)
A strategy of communication avoidance might work if you're a one-person company with no managers and no customers, but in the real world, it's necessary to periodically come out of our hidey-holes and talk to people. The need to communicate regularly grows as the project's size and complexity grows, as deadlines approach, as requirements change.

The idea of the Lone Wolf Developer sitting uninterrupted in his office 24/7, building the software in a vacuum, gloriously emerging after three months, on time, with software that perfectly conforms to the requirements, that miraculously works exactly according to the customer's needs, is a myth--incompatible with the reality of professional software development.

Re:Developer productivity: The art of saying no by BurningFrog on Saturday March 14, 2015 @01:19PM (#9203352)
Having meetings every Thursday is exactly "periodically come out of our hidey-holes and talk to people".
Re:Developer productivity: The art of saying no by cssmoo on Saturday March 14, 2015 @02:38PM (#9203668)
I operate a "if you can't be bothered to structure your thoughts in a well-written email, you can bugger off" process. Meetings Thursday is a no go area for me.

This works well once everyone understands it.

Unfortunately for it to work, you tend to have to serve as an internal consultant to a company, write good replies and maintain a lot of documentation and technical standards.

Re:Developer productivity: The art of saying no by nerdy on Saturday March 14, 2015 @01:08PM (#9203306)
Unfortunately so.