[lloydatkinson]

That isn’t made up in the slightest. Creative thought processes take time to get into the flow state.

Frequent disruptions to this are deeply frustrating and almost every dev I’ve worked with has made similar remarks. Poor meeting scheduling is a guaranteed way of ensuring your devs have little to no motivation to do anything.

In a previous job we called Wednesday “Meeting Wednesday” because total meeting time was at least 4 hours sometimes with small gaps between where nothing would get done.

Sure you might be able to do small tasks that truly take less than an hour but in reality that’s rarely the case.

[KnobbleMcKnees]

Your rarity is another man's frequency. Defining all programming in terms of long drawn out creative endeavours isn't very useful, which is the point I was making to begin with.

[sokoloff]

The quote doesn’t say that no programming tasks can be done in blocks of an hour, but rather that programming well cannot.

[KnobbleMcKnees]

The quote says "generally prefer". What programmer generally prefers a half day to complete a sub-hour task?

[smallnix]

Yes, both of you only contributed anecdotes and no data. (Neither did I)

[williamdclt]

You’re not disagreeing with your parent, I think their point is that « work restoring creative thought processes » is a subset of the work that a software developer does