Why We Don't Do Daily Stand-Ups at Supercede An Article by Jezen Thomas jezenthomas.com Yesterday I worked on the widget. Today I will work on the widget. I have no blockers. Are you asleep yet? The developers are. You promise them an intellectually stimulating work environment and what they end up with is drudgery. What value can be had from these meetings anyway? Using “alignment” for justification is so nebulous that it is essentially meaningless. Engineers align themselves. They talk. Especially if you hire good ones (which, you know, you’ll struggle to if you have a culture of coercing them into this kind of busywork). Where does the real discussion happen? It’s written down. Why we stopped breaking down stories into tasks agile
The superficial aspects of what someone else is doing What keeps me busy in my classes is trying to help my students learn how to think. They say, "Rob holds his hands like this...," and they don't know that the reason I hold my hands like this is not to make myself look that way. The end result is not to hold the gun that way; holding the gun that way is the end result of doing something else. …The more general issue is that a person who doesn't understand the thing they're trying to copy will end up copying unimportant superficial aspects of what somebody else is doing and miss the fundamentals that drive the superficial aspects. This even happens when there are very detailed instructions. Although watching what other people do can accelerate learning, especially for beginners who have no idea what to do, there isn't a shortcut to understanding something deeply enough to facilitate doing it well that can be summed up in simple rules, like "omit needless words". Dan Luu, Some thoughts on writing The Elements of Style style