1 views collected around this technical thread.
This article presents a playful yet comprehensive programming exam that includes multiple‑choice, fill‑in‑the‑blank, true/false, code‑reading, and essay questions covering debugging habits, Git practices, code review comments, and common developer myths, complete with answer keys and sample code snippets.
The article examines how AI-powered code generation, while boosting surface productivity, introduces hidden technical debt at the code, architecture, and organizational levels, urging architects to implement rigorous review, governance, and cultural practices to prevent long‑term risks.
This article analyzes Google’s large‑scale code review practices, showing how lightweight processes, tool‑driven automation, and a culture of knowledge transfer turned code review from a time‑consuming task into a productivity engine that scales across tens of thousands of engineers.
The team built a low‑cost AI‑powered code‑review assistant that injects line‑level comments into GitLab merge requests, using LLMs via Feishu, iterating quickly through MVP and optimization phases, achieving 64 integrations, 150+ daily comments, feedback‑driven prompt refinement, and demonstrating high ROI for small‑to‑medium teams while outlining future IDE and rule‑based extensions.
This article outlines seven common habits of inexperienced developers—such as massive code submissions, poor code quality, multitasking, arrogance, ignoring feedback, handling personal matters at work, and chasing trends—and offers practical steps to become a more professional programmer.
The article argues that cultivating a strong engineering culture—through shared values, clear processes, automation, altruistic collaboration, and continuous self‑improvement—empowers programmers to remain reliable and productive despite uncertainty, boosting the odds of sustained success while acknowledging that culture is only one of several critical factors.
The article outlines how to build a scalable, modular AI code‑review agent using LangChain, detailing stages from naive prompting to advanced prompt engineering, architecture with six core modules, strategies to curb hallucinations, improve reliability, performance, and human‑AI collaboration, and future RAG integration.
This article reviews Java Spring code for a coupon claim and approval workflow, identifies concurrency and transaction issues such as missing locks and inconsistent update order, and proposes optimizations including user‑level locking, simplifying lock management, and aligning transactional update sequences to prevent deadlocks.
A simple typo that changed a daily interest rate from 0.00006944444 to 0.00069444444 inflated calculated interest tenfold, went unnoticed because the author self‑approved the SQL update and testing only checked syntax, and the incident underscores the need for rigorous code review, testing, and change‑management procedures for critical data.
The author recounts a late‑night incident where a newly launched marketing tool malfunctioned due to a boolean logic error in Java code, describes the chaotic debugging process, presents the faulty and corrected implementations, and confirms the logical equivalence of the final solution.
Improving code reviews hinges on clear, domain-specific naming, concise guiding comments that explain why code behaves as it does, and respectful, issue-focused communication that adapts to reviewers’ experience, collectively boosting code quality, team cohesion, and overall software reliability.
This article outlines ten practical guidelines for robust parameter validation in backend Java services, covering enumeration ranges, consistent length constraints, proper use of @NotBlank, synchronizing API documentation, comprehensive annotation usage, request object encapsulation, and the importance of self‑testing and authorization checks.
This article outlines seven common behaviors of inexperienced programmers—such as massive code commits, poor code quality, multitasking, arrogance, ignoring feedback, handling personal matters at work, and chasing every tech trend—and offers practical steps to become a more professional and effective developer.
The article recounts a developer’s mistake of entering an extra decimal place in a SQL update for daily interest rates, explains how the error escaped code review, testing and production validation, and shares practical lessons on precision handling, review processes, and operational safeguards.
This article explains what code review is, why front‑end team leads should conduct it, and how to use AI‑powered VSCode extensions together with modern JavaScript/TypeScript techniques—such as optional chaining, function extraction, constant usage, and mapping—to streamline review workflows and produce cleaner, more maintainable front‑end code.
The article recounts a real‑world incident where a device’s MAC address could not be changed because a previous engineer deliberately disabled the relevant function, discusses the discovery of the backdoor code, and examines the legal and ethical implications of such intentional vulnerabilities.
This article explains the importance of code review, outlines its core goals and basic principles, provides step‑by‑step practical guidance with a detailed checklist, shares real‑world case studies and code examples, and discusses metrics and future AI‑assisted improvements to help teams improve software quality.
This article explains the importance of code review, outlines its core objectives and basic principles, describes practical steps and a detailed checklist, shares several real‑world case studies with before‑and‑after code snippets, and discusses the benefits, metrics, and future AI‑assisted enhancements.
The article describes Vivo's Engineering Efficiency team's VCR platform, built on GitLab and Gerrit, detailing the design and implementation of code‑review plugins, challenges faced, architectural integration, customization techniques, and future directions toward automated and AI‑enhanced code review.
The article shares practical lessons on maintaining code quality and readability amid intense project iterations, emphasizing thorough code reviews, incremental refactoring, and the importance of a shared coding style to prevent technical debt and the broken‑window effect.