Some people here are mentioning code reviews for their teams and how they don’t enjoy that.
I would say this article is missing a fair point. I’ve learned a lot by just browsing Github.
For example if I’m interested in solving a Caching problem I’ll skip some of the open source libraries around caching and how it’s implemented.
Often times you run into a very elegant and readable solution that someone has created. And the most interesting takeaway from that is that you can get inside the persons head around API design and implementation.
When I stumble upon an awesome elegant library I always either take a mental note about it or try a small sample implementation of my own. This has helped me synthesize great APIs designs over my career. You develop your own style over time by picking and choosing your elegant solutions, and eventually you also come up with your own bright ideas through language features or loopholes that come across as exceptionally elegant.
Some people here are mentioning code reviews for their teams and how they don’t enjoy that.
I would say this article is missing a fair point. I’ve learned a lot by just browsing Github.
For example if I’m interested in solving a Caching problem I’ll skip some of the open source libraries around caching and how it’s implemented.
Often times you run into a very elegant and readable solution that someone has created. And the most interesting takeaway from that is that you can get inside the persons head around API design and implementation.
When I stumble upon an awesome elegant library I always either take a mental note about it or try a small sample implementation of my own. This has helped me synthesize great APIs designs over my career. You develop your own style over time by picking and choosing your elegant solutions, and eventually you also come up with your own bright ideas through language features or loopholes that come across as exceptionally elegant.