How do you capture WHY engineering decisions were made, not just what?
via news.ycombinator.com
Short excerpt below. Read at the original source.
We onboarded a senior engineer recently strong, 8 years experience. He spent 3 weeks playing code archaeologist just to understand WHY our codebase looks the way it does. Not what the code does. That was fast. But the reasoning behind decisions: – Why Redis over in-memory cache? – Why GraphQL for this one service but […]