Some devs say, you learn programming by reading code but sometimes reading is not enough. I want to learn story behind it (why it is written like that). Any repos with good articles providing history?
Shameless plug, while this does not have full articles explaining decision process, I started tracking design decision with a short summary and the date those choices were introduced: <a href="https://github.com/wiringbits/scala-webapp-template/blob/master/docs/design-decisions.md">https://github.com/wiringbits/scala-webapp-template/blob/mas...</a><p>This has been helpful to my team because there are times where something does not seem right, or, it just seems a weird choice, documenting the reasoning can help new team members to understand this.<p>In retrospective, I should have started doing this many years ago.
If you're at the repo level, then read the commit messages, release notes, and issues and comments linked to a pull-requests. They will contain the rationale and discussions on technical decisions and the tradeoffs behind them.
This sounds right up your alley: <a href="http://www.aosabook.org/en/index.html" rel="nofollow">http://www.aosabook.org/en/index.html</a>