Hacker News new | ask | show | jobs
by f1shy 585 days ago
> The risk is that managers at this tier end up telling people precisely what to do and how to do it. This is not scalable, leads to frustration on the part of the manager and managee, and burnout. > Better is that the manager describe the desired outcome and set of standards, kpis, norms, etc, that must be met, and let ICs do it any way that fits. (Standards and norms enforce a culture that lets people collaborate more productively. No point letting a dev loose to code up a feature if they turn around a week later and tell you they did it...but in C#, when you're a Rust shop.)

It is like the difference between imperative and declarative programming. Imperative programming is micro-management (bad), you should strive for declarative programming.

1 comments

Declaritive programming, without the programming part.