Just doing work without an eye on the big picture rarely satisfies anyone. We want to k**w what we’re doing matters and that means k**wing why we’re doing it. This is true in all walks of life and certainly so in software development.

If you simply ask a programmer to implement a feature, but fail to share the purpose or the justification for said feature, all you get is a code monkey. Code monkeys merely translate requirements into code verbatim. There’s ** room to trade concessions with the designers if I don’t k**w what you’re trying to do.

So **t only is it demotivating **t to k**w why, it’s also bad for productivity. Figuring out what the problem really is is how good programmers judo the problem: “Yes, what you’re proposing is one way to solve it, and that’ll take 50 hours. But we can solve the same underlying problem by doing this instead and that’ll only take 8 hours. How about it?”

Sharing the context shares ownership. **w we’re all working on solving the problem the best way we can. **t just laying the bricks in the order the big man tells us to.




أكثر...

---

Humans need to k**w why