Community Picks·2yChatGPT - Prompts for developers
ChatGPT is an AI chatbot that helps developers in various ways such as writing code, refactoring code, code review and debugging, optimizing code, explaining code, creating unit tests, adding code comments, creating boilerplate code, and writing regular expressions.
Medium·2y3 Lessons from the Smartest Developers I’ve Worked With
The author shares lessons learned from working with exceptionally smart developers. Key takeaways include the importance of writing unit tests, being thorough in code reviews, and aligning technical decisions with business goals. The post emphasizes learning from others and aiming higher in one's career for better growth.
Community Picks·2yBest Practices For Reviewing Code
Discover the best practices for reviewing code to ensure high software quality. Learn about setting goals and standards, communicating expectations, defining a code review process, using a code review checklist, and fostering a positive code review culture.
DEV·2yWriting a good Pull Request (with template)
A template for pull requests is introduced to improve codebase and the process of reviewing changes. The template includes sections for providing context, describing the task, discussing changes in the codebase and external services, and providing additional information.
Graphite.dev·2yThe new developer toolchain
The post discusses the relevance of Graphite in the era of AI code generation tools like GitHub Copilot and ChatGPT. It argues that AI will make the 'outer loop' of code review, testing, and deployment more critical. With AI-generated code increasing, the need for robust 'outer loop' tools to manage review and deployment workflows is emphasized. The post also explores the limitations and future improvements of AI coding models, stressing the necessity of human oversight in code quality and security.
Atomic Spin·2yReviewing Code: A New Developer's Guide
New developers often find code reviews daunting, but understanding how to write and review pull requests can significantly improve their abilities and confidence. Key steps include ensuring code quality, providing detailed testing instructions, effectively running and testing colleagues' code, and delivering constructive feedback in a considerate manner. Emphasizing a team-focused approach, this guide shares best practices for contributing meaningfully to code reviews and fostering professional growth.
Community Picks·2yBest practices for pull requests
Best practices for creating and managing pull requests include writing small PRs, reviewing your own pull request first, providing context and guidance, using pull request templates, defining code owners, using protected branches, and using automated tools to review code styling.
Code Like A Girl·2yCode Review Best Practices: Enhancing Development Efficiency and Quality
Effective code reviews are crucial for maintaining high-quality software and reducing development costs. Key practices include setting clear objectives, maintaining coding standards, crafting efficient review processes, and fostering team collaboration. These strategies help in catching bugs early, ensuring maintainability, performance, and security, and promoting continuous improvement. Code reviews should focus on providing actionable feedback and creating a positive, constructive environment for better teamwork and software quality.
DEV·2yMastering Code Review: A Guide for Reviewers and PR Creators
This post provides best practices for conducting code reviews and creating pull requests. It emphasizes the importance of constructive feedback, understanding context, and addressing critical issues. For reviewers, it suggests being specific, offering alternatives, and considering the bigger picture. For pull request creators, it recommends preparing clean code, providing context, engaging in discussions, and addressing feedback.
Hacker News·2yCode review antipatterns
Code reviews can be a double-edged sword: they can improve the codebase and the skills of the development team or be misused to obstruct progress and demoralize developers. The post humorously highlights several negative patterns, such as nitpicking, introducing delays, making vague criticisms, and contradicting previous feedback. It emphasizes the importance of constructive criticism, minimizing unnecessary rounds of revisions, and using authority responsibly in peer reviews. The ultimate goal is to foster a collaborative atmosphere that benefits the project and all the developers involved.
GitHub Blog·2yHow to review code effectively: A GitHub staff engineer’s philosophy
Sarah Vessels, a GitHub Staff Engineer, shares her code review philosophy, highlighting its significance in building quality software. She covers how she identifies and prioritizes pull requests, uses GitHub and Slack integrations, and emphasizes the importance of clear communication and consistency in code reviews. She also discusses strategies to reduce notification fatigue, uses of automation, and offers advice on providing constructive feedback. Ultimately, she aims to improve the overall code quality and foster a collaborative editing environment.
Machine Learning News·2yCodiumAI PR-Agent: An AI-Powered Tool for Automated Pull Request Analysis, Feedback, Suggestions and More
Managing pull requests is often time-consuming and error-prone. CodiumAI PR-Agent aims to streamline this process by offering AI-powered assistance for tasks such as automatic description generation, review feedback, and code suggestions. It integrates with popular git platforms like GitHub, GitLab, Bitbucket, and Azure DevOps. Its Pro version includes advanced features like generating documentation and custom labels, all powered by the GPT-4 model. PR-Agent is designed to save time, reduce errors, and maintain quality standards in pull request management.
The Daily WTF·2yYes, No, NO NO NO NO
The post criticizes a unique and seemingly unnecessary implementation of a YesNoType in Java, which essentially redefines a boolean value using strings. The analysis highlights several inefficient coding practices, such as redundant methods and unnecessary type reinvention, advocating instead for simpler solutions that utilize standard booleans.
Lobsters·2ydiff2html
diff2html provides a CLI tool for viewing differences in code with both line-by-line and side-by-side previews. It utilizes highlight.js for syntax highlighting and pairs similar lines for better change tracking. Installation is simple with npm, and the tool allows browsing commit changes directly in a web browser.
Hacker News·2yCode Review as Interview
CodeRev is a lightweight tool for organizing and conducting technical interviews using code reviews. It can be a better measure of a candidate's ability to adapt and contribute to a team. It provides a real-world, day-to-day responsibility of providing feedback to teammates.
Pointer·2yThe art of good code review
Code review is important for shared ownership and ensuring the big picture is considered. Good code review involves clear descriptions, thorough understanding of the code, reviewing tests, constructive commenting, and withholding approval until full understanding is achieved.
Product Hunt·2yKypso Code Reviewer - Eliminate code review bottlenecks
Kypso Code Reviewer is a productivity tool aimed at developers, utilizing artificial intelligence to streamline code review processes. It was featured on August 26th, 2024, and has received a 5/5 rating from 5 users since its initial launch on August 21st, 2023.
Engineering Enablement·2yReducing Code Review Time at Google
Google created a code review comment-resolution assistant using machine learning to help developers address review comments more efficiently. The assistant suggests code changes based on comment text, reducing the time spent resolving code review comments.
Stack Overflow Blog·2yThis developer tool is 40 years old: can it be improved?
Despite rapid advancements in development tools, many developers still use the Myers Diff Algorithm, a 40-year-old method for showing changes in code. GitClear's new 'Commit Cruncher' algorithm proposes a more precise way to reflect code modifications, potentially reducing the lines of code to review by 28%. This innovation could save significant time and resources during code reviews, improving efficiency and reducing the cognitive load on developers.
