4 ms·

Wait, you're actually putting that forward as a good day? That boggles my mind...if you come in at 9, get settled, you have maybe 45 minutes to work. Then, unti

Wait, you're actually putting that forward as a good day? That boggles my mind...if you come in at 9, get settled, you have maybe 45 minutes to work. Then, until 14-15, you have NO one hour stretch, then you have just one more stretch from 16-17...when do you actually code?? Don't you need a couple hours of focused time?

cabraca 7y ago
> Wait, you're actually putting that forward as a good day? sure. Its better this way. otherwise i would have those meetings scattered across a complete week. and tbh, days like this come every two weeks. its not every day. most days its 15min daily standup in the morning and sometimes a refinement of 30m. >...when do you actually code?? i come in at around 7-7:30, code until ~10, go home after the last meeting.
WaylonKenning 7y ago
As an Architect, I'd rather have six hours of meetings, and one hour of documentation, than eight hours straight of being at a computer. In some jobs - meetings are the work. Meetings are influencing, are negotiating, are discussing, are communicating. And all of that is best done face to face.
- wutbrodo 7y ago
  That's orthogonal to the fragmentation. Probably two thirds of my job is meetings, but I'm ruthless about compacting them so that the remaining third isn't a scattered forty five minutes at a time
- deleted 7y ago
  [deleted]
wongarsu 7y ago
I assume he's coding on the other days of the week.