box | Joshua writes

You build a box to pack a mess. But if there's one thing you know about a mess, it grows.

So you cram harder, tape the corners, sit on the box begging to explode. You'd probably laugh at yourself if you weren't so distracted by the cardboard wrinkling under your butt.

"All right, enough!" says your sense, uncommon.

Now you resolve to stack boxes, right. Starting with the one your cheeks got chummy with, you pile box on top of wretched box until the stack becomes so unstable you can't bear to look at it, it might roll down with your eyes.

Finally, it at all, you realize you've become a box juggler. You might even call yourself an architect. By now, odds are you forgot how to laugh at yourself, just like you forgot about the mess you said you were packing.

Or, sorry. What I meant to say was:

"By this stage, significant expertise has been developed in box management, box stabilization, box orchestration, and cross-box dependency mitigation. The organization may reasonably describe this capability as architecture."

You build a box to pack a mess. But if there's one thing you know about a mess, it grows.

So you cram harder, tape the corners, sit on the box begging to explode. You'd probably laugh at yourself if you weren't so distracted by the cardboard wrinkling under your butt.

"All right, enough!" says your sense, uncommon.

Or, sorry. What I meant to say was: