[Mxtetris]

What distinguishes senior practitioners from juniors, in software development and in other crafts, is the number of errors they've already made and the lessons they learned from those errors.

Those mistakes and learnings together inform their judgement when approaching tasks and allow them to ask questions like:

* Is this code robust enough? (They ask because of the many times they pushed code and suddenly everything broke.)

* Should we even be building this? (They ask because of that one time they didn't ask, and wasted weeks of effort on something that was never used.)

* Is approach A the best way to achieve our goal? (They ask because of that one time they tried A, thought it would take one week, but spent two months on it instead.)

* What happens when we're asked to add X feature? (They ask because of that one time they were surprised by a feature request and had to rewrite a bunch of their code.)