3 ms·
Nah it's a pretty good representation. And acting like time should 100% be spent writing features is shortsighted - sometimes it's worth it to pay fixed costs s
by whateveracct 5y ago
Nah it's a pretty good representation. And acting like time should 100% be spent writing features is shortsighted - sometimes it's worth it to pay fixed costs such as filling in a gap of the ecosystem of the language you chose for higher reasons than cranking out business code.
- adamwk 5y agoWhat's this higher reason? Isn't the point to crank out business code?
- whateveracct 5y ago"Crank out" was supposed to imply optimizing the short-term. Ensuring your next sprint has the most output as possible. If you choose an FP language like Haskell, you tend to value things beyond that. Stability, engineering culture, retention, big rate, the ability to extend things for cheap only because you did the hard part of using Haskell to begin with, etc It's just throughput vs latency