> Consider we have an API receiving 50 requests per second. Say we want to keep the average response time under 200 ms so that users don’t get frustrated. We can estimate the number of concurrent requests that should be…
It means that hierarchy matters more than otherwise, because the higher-ups "are right" more by LP decree than by meritous consensus.
I don't understand these kinds of leadership/management. What they want clearly isn't a tech company. They don't want technical wisdom, insight, nor vision. Why bother hiring in-house SWE's at all? They should just…
In terms of debugging inconvenience for intermediate values, `->(x) | a | b | c` is the same as `c(b(a(x)))`. I find debugging /w a REPL using functional-esque code much easier. You can play around and exec/inspect…
> Consider we have an API receiving 50 requests per second. Say we want to keep the average response time under 200 ms so that users don’t get frustrated. We can estimate the number of concurrent requests that should be…
It means that hierarchy matters more than otherwise, because the higher-ups "are right" more by LP decree than by meritous consensus.
I don't understand these kinds of leadership/management. What they want clearly isn't a tech company. They don't want technical wisdom, insight, nor vision. Why bother hiring in-house SWE's at all? They should just…
In terms of debugging inconvenience for intermediate values, `->(x) | a | b | c` is the same as `c(b(a(x)))`. I find debugging /w a REPL using functional-esque code much easier. You can play around and exec/inspect…