Party of One for Code Review
Some good thoughts on code reviews in the emerging age of AI.
Read more [tidyfirst.substack.com]
Posts tagged with code review
Store Code Discussions in Git using Git Notes
Git is a gift that keeps on giving
Read more [wouterj.nl]
Join 9,500+ smart developers
Get my monthly newsletter with what I learn from running Spatie, building Oh Dear, and maintaining 300+ open source packages. Practical takes on Laravel, PHP, and AI that you can actually use.
"Freek publishes a super resourceful and practical newsletter. A must for anyone in the Laravel space"
No spam. Unsubscribe anytime. You can also follow me on X.
No code reviews by default
At Raycast, the dev team only requests code reviews when they think it's necessary.
Read more [www.raycast.com]
Authoring Great Pull Requests
– dev.to - submitted by Patrick
Some best practices and tips for composing high quality pull requests when contributing to open source projects.
Read more [dev.to]
How to become a great engineer
Philip Walton, an engineer at Google, wrote a wonderful article that every developer should read. He talks about front-end engineers, but most tips are applicable to back-end engineers as well. A few quotes:
Taking the time to figure out why your hack works may seem costly now, but I promise it’ll save you time in the future. Having a fuller understanding of the systems you’re working within will mean less guess-and-check work going forward.
Solving problems on your own is a great way to learn, but if that’s all you ever do, you’ll plateau pretty quickly. Reading other people’s code opens your mind to new ways of doing things.
In my experience, writing, giving talks, and creating demos has been one of the best ways to force myself to dive in and fully understand something, inside and out. Even if no one ever reads what you write, the process of doing it is more than worth it.Be sure to read the full article here: http://philipwalton.com/articles/how-to-become-a-great-front-end-engineer/
