“What I cannot create, I do not understand.” The line stays with me because it turns understanding from something passive into something testable.
It is easy to feel like you understand a queue, a transaction, a payment flow or an authentication system while someone else is explaining it. Building one changes the standard. Suddenly the edge cases are yours.
What happens when the webhook arrives twice? What happens when two couriers accept the same delivery? What happens when the network fails after money moves but before the response is recorded? Those questions are not footnotes. They are the system.
The architecture becomes real at the boundary where the happy path stops being enough.
Creation exposes the gaps.
That is why I like building from first principles when I am learning. I want to know what abstraction is protecting me from, what trade-off it makes, and what would break if it disappeared.