Bilingual

The Short Leash AI Coding Method for Beating Fable
23 days ago
- The post discusses using AI agents to write high-quality software, emphasizing a method suitable for expert developers who want to enhance performance without compromising quality.
- Current AI agent approaches, like those promoted by YouTubers, often lead to low-quality code and lack of understanding, as AI can go off track, especially in niche areas with limited training data.
- The "Short Leash" method is introduced, which involves active developer involvement, including planning, reviewing diffs, denying permissions when needed, and committing after subtasks to maintain control and quality.
- For AI reviews, combining human and AI review is recommended, with AI acting like a linter and humans catching higher-level issues. PRs should disclose AI usage and be thoroughly reviewed by the author before submission.
Zero-defects code: the prescient Microsoft memo from 1989
20 days ago
- Microsoft's 1989 Zero Defects memo advocated for principles like continuous integration and test-driven development long before they became mainstream.
- The memo highlighted problems in Microsoft's culture, such as rewarding developers for checking in incomplete code and treating schedules as more important than quality.
- Chris Mason argued that writing perfect, zero-defects code was achievable and emphasized the need for a mindset shift to prioritize quality over speed.
- Key solutions proposed included having a working, shippable product daily, fixing bugs immediately, and shifting testing to quality assurance rather than bug-finding.
- The memo suggested practical techniques like code reviews, writing tests before debugging, and using asserts to verify assumptions, aiming to reduce bugs and improve predictability.
- Leadership committed to supporting realistic schedules and pushing back against pressures to cut corners, emphasizing that taking minor heat early was better than major issues later.
Why you should not have Managers in your class name
19 days ago
- Naming classes and methods correctly is crucial as it influences code structure, future thinking, refactoring, and extension, with poor naming leading to technical debt.
- Using '-er' suffixes like 'Manager' often indicates poor design; for example, 'ConnectionManager' became complex with multiple responsibilities, whereas 'Connection' would have been clearer and simpler.
- Choosing precise names helps maintain clean code, simplifies extension and refactoring, and reduces complexity and bugs, so spending extra time on naming is recommended.
Anyone else get a vague GitHub shakedown notice?
15 days ago
- Greg Troxel received an email from GitHub about billing for Code Quality, moving to general availability in July 2026.
- He suspects the email is genuine but is confused as he has not signed up for paid plans and is not a GitHub Sponsor.
- Greg questions if QGIS's use of Code Quality might have triggered the email and asks if others received similar notices or are concerned about unexpected bills.

Hasty Briefsbeta

code quality

The Short Leash AI Coding Method for Beating Fable

Zero-defects code: the prescient Microsoft memo from 1989

Why you should not have Managers in your class name

Anyone else get a vague GitHub shakedown notice?