Strongly agree with this thread.https://twitter.com/izs/status/950077798055661568 …
@dhh Do you count "focused technical conversation" as programming?
-
-
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
-
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.
-
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.
-
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.
End of conversation
New conversation -
-
-
I actually do, provided: 1) the conversation is less than 5 minutes (ideally less than 3), 2) it exclusively involves information of immediate use to all parties, 3) no pleasantries are exchanged. These interactions make me feel like one mind with many hands, it's amazing.
-
I've gotta say, working in the
@typelevel ecosystem in Scala helps. FP, type system, and category theory give our everyday vocabulary about software great analytical power. YMMV.
End of conversation
New conversation -
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.