It appears that one consequence of being a tech lead is that team members consider you the default reviewer for all their pull requests (PR). Though the code review process seems straightforward, there are many aspects that need to be considered. Effectively being one form of feedback, I would like to share my observations and give advice to future leaders about making this process as smooth as possible. Code review is an essential technique to improve the code quality and share knowledge. It...| Software Testing Magazine
Do you think all AI generated code is shit? Are you an engineer, founder, or layperson who has used AI in the last few...| Revelry
Two months ago, a 13-year-old video taught me why AI agents get stuck at 90% and how to architect my way to ~100%| Forge Code Blog
“If you shame attack research, you […]| hn security
Control is an Illusion Anyway... Code review is an indispensable practice in any self-respecting software engineering organization. We get higher quality code and knowledge sharing. It's awesome. But, it’s also not awesome. To be honest, it can be a nightmare. Sometimes we get blocked for days waiting for approval or end up in a never-ending context-switching game of review ping-pong.| The Ivory Tower
In 2016, Microsoft made a pull request to Node.js that added almost 3 million lines of code. The Node.js maintainers were actually super cool about it, since it enabled Node.js to use MicrosoftR…| Andy G's Blog
¿Buscando introducir o mejorar un proceso de revisión de código? Este artículo puede ayudarte a observar la problemática desde diferentes dimensiones.| 10Pines | Blog
Learn how to implement effective code review practices to foster developer growth with feedback, collaboration, and continuous improvement.| HAY
Learn the secrets to faster code reviews: How to deploy individual preview environments for each pull request using GitHub Actions and Kubernetes.| developer-friendly.blog
Let’s talk about Code Reviews for a minute. They’re important; they spread knowledge around and catch bugs [citation needed], but they can be frustrating some times. They don’t need to be though. There are a few things we can do to keep the code review a pleasant experience. Review the code, not the coder. Keep […]| Christopher J. McClellan
*There is an excellent documentary called Behind the Curve where you can witness Flat Earthers do this exact thing when their experiments only continue to prove the earth is round.| Andy G's Blog
Next entry: Conflict management| Andy G's Blog
(This is the second part in a series about working effectively to pass code review quickly and without missed defects.) Image source: Wikimedia In part one, we showed that, all other factors consid…| Andy G's Blog
A Pull Request is an event where a developer submits code changes for review before they are merged into a project's main codebase.| HAY
At the 31. Chaos Communication Congress I had the pleasure to watch the presentation of Fabian Yamaguchi about the code analysis platform Joern. I’ve heard about this tool before at Hacktivity but this time I could have deeper view on the internals and the capabilities of the software that inspired me to clean up and release some piece of code I used for some years in code review projects.| Silent Signal Techblog
Guidelines describing the required mindset and phrasing techniques for effective and respectful code reviews| Philipp Hauer's Blog