Strongly agree with this thread.https://twitter.com/izs/status/950077798055661568 …
-
-
Replying to @wycats
My condolences to any developer who has to spend 3/4 of their time in meetings, discussions, planning, and other “communication” every week in and out. Sounds miserable to me.
9 replies 45 retweets 187 likes -
Replying to @dhh
It's not, in practice miserable unless it's wall to wall *meetings*. Thinking and communicating is just part of the way I do programming. It of course depends on what I'm programming.
1 reply 0 retweets 6 likes -
Replying to @wycats
Different stripes, I suppose. Bliss for me is to spend 3/4 of work programming, 1/8 on communication (chat/comments/videochats/etc), 1/8 on the rest.
2 replies 0 retweets 16 likes -
I'm with
@dhh on this one. Coding solo, reading documentation, experimenting, reading/writing papers, thinking quietly, pair programming, and focused technical discussions collectively constitute "programming" for me and I enjoy it all.2 replies 0 retweets 5 likes -
Replying to @MooseFather @dhh
@dhh Do you count "focused technical conversation" as programming?2 replies 0 retweets 0 likes -
Replying to @wycats @MooseFather
No. It's rare that I spend more than an hour a day on "focused technical conversation". But that together with PR reviews probably adds up to that 1/8 target
1 reply 0 retweets 1 like -
Replying to @dhh @MooseFather
Sounds legit. There are definitely different styles and different goals here. I have no problem working with someone who likes focusing on coding as long as they're working on features with clear goals and their code communicates its intent well.
2 replies 0 retweets 6 likes -
Replying to @wycats @MooseFather
This whole discussion got kicked off from the idea that people think working 80-100 hours is a good idea. If you can't even make the most of 40, then doubling that or more is bananas.
4 replies 2 retweets 30 likes
Totally agree. Adding more hours over more than a very brief period has no chance of working. 2x time costs more than 2x productivity so it's a net negative.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.