3 ms·
I think you read this wrong, the performance doesn't matter. It matter that the person learned something new even that he was experienced Clojure developer. And
by jcubic 5y ago
I think you read this wrong, the performance doesn't matter. It matter that the person learned something new even that he was experienced Clojure developer. And he did this by reading closed PR.
Success Open Source project are usually created by very smart and experienced developers. And big projects have a lot of them. Their Code Reviews are much better then anyone your closed source team will have, unless you're junior developer in team of Senior developers.
Right now I'm thinking that at work we also have git (for intranet application) and we have PR, this may be very good idea for newcomers to read the PR that was done to understand how some features were implemented instead of just diving into recent code. This may be best advice I've seen in a while. But maybe it's just my own idea that came from this article, that you've understand differently.
For me this article is about advice read closed PR you will learn a lot, here for Open Source projects, because OSS projects on GitHub are biggest projects you can find.
- ineedasername 5y agoI fully agree that there is significant value in what the author writes even if there was more of the sort of crystallization of experience into learning. I just thing that this method of learning-- which seems not just useful but essential in learning how to write performant and less buggy code. As I said, experiential learning and learning from others will always be important & valuable, as it is in any field. I just think the balance between that and more established best practices is weighted too heavily toward the "figure it out for yourself finding ad hoc sources" side of things.