what could possibly go wrong ...
15 karma · joined May 6, 2015
what could possibly go wrong ...
On such large apps that need large teams of engineers, without good product management and also project management, even great engineers can do a terrible job despite all their efforts or heroics "on the ground".
So true and sad. In all the so called data-driven groups I have worked for, the tyranny of data makes metrics and numbers the justification for or counter to anything, however they have been put together.
> The sad truth is that most people aren’t being rigorous about their A/B testing and, in fact, one could argue that they’re not A/B testing at all, they’re just confirming their own hypotheses.
The sad truth is that most people aren’t being rigorous about anything.
Catnaroek said it already: without parametric polymorphism you are forced to either: 1) commit to a single type upfront which limit the utility (string in your example I think), 2) use interface{} and suffer the boxing in every circonstances while not having any static type checking.
I actually like your pattern. I think it makes sense to have a process as a pair of input and output streams.
At best these are copy-pastable patterns.