Kache

> 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 in the system and adjust the number of threads accordingly: L=λW=50×0.2=10 So, we need around 10 concurrent workers processing requests!

Uh... What? Concept seems misapplied

Example: if we only want to keep it under 1 sec (our users are more patient), then we need 50 x 1 = 50, even MORE workers?

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 stick with consultants and contactors.

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 lines/snippets at will without changing state & "breaking" the debug session.