News for hackers. Stuff that matters.
Re:The Busy Person’s Lies by pc86 on Thursday December 01, 2016 @02:49PM (#13082819)
Not all work is (or needs to be) "intellectually productive."

I see statements like this on HN a lot, particularly from developers (myself included), but most of them cringe at the thought of having 2-4 hours of administrative work every day.

Re:The Busy Person’s Lies by lacampbell on Thursday December 01, 2016 @03:02PM (#13082949)
What sort of work would you class as administrative?
Re:The Busy Person’s Lies by Jtsummers on Thursday December 01, 2016 @03:15PM (#13083087)
Meta-tasks around projects. Communicating/coordinating with other people. In big-corp land, mandatory training and time spent on time tracking (a bit ironic). Dealing with git screw-ups by people new to it.
Re:The Busy Person’s Lies by haikuginger on Thursday December 01, 2016 @11:20PM (#13085979)
> Dealing with git screw-ups by people new to it.

I do this all the time. Of course, the person new to it is usually myself.

Re:The Busy Person’s Lies by dieterrams on Thursday December 01, 2016 @04:20PM (#13083609)
I think the problem is when such administrative work interrupts the intellectually productive work.
Re:The Busy Person’s Lies by pc86 on Friday December 02, 2016 @01:32PM (#13091037)
I think another key component of administrative work is that even if it's time sensitive, it's not urgent.
Re:The Busy Person’s Lies by Kenji on Thursday December 01, 2016 @02:59PM (#13082911)
Software Design is intellectually productive. If you aren't, you are not designing and implementing software.
Re:The Busy Person’s Lies by jgord on Thursday December 01, 2016 @09:00PM (#13085354)
I actually disagree - maybe 60% of good software dev is really really thinking. A lot of it is automatic, based on learning the crafts good habits, repeating motifs, testing can be repetitive but is important to do as you go. Making sample data, talking to people writing emails - so there is a chunk that is not deep foo.

This correlates with my anecdotal observation that the smartest people can write bad code, and it takes them quite a while to absorb the stuff of writing good code.. a couple years at minumum perhaps. Its not just about raw thinking power - perhaps the important bits are, but not all of it.