Tag
ty has added the ability to detect always-true or always-false conditions in code, helping to prevent common mistakes such as forgetting to call a function in an if-statement.
Kent C. Dodds demonstrates a technique to prevent low-quality code generation without needing to manually review the code.
The article discusses using lines of code as a metric for evaluating Ruby gems, suggesting it helps understand implementation complexity and encourages a design philosophy focused on clarity and maintainability through 'breezy reads'.
Lauren Tan, a former engineer at Meta and Netflix now at xAI, shared her methodology for leading an AI agent fleet to merge 2500 production PRs in a month, emphasizing rigorous validation and a Dune architecture with an open-source tool called pstack.
This article discusses how to manage code quality when using AI coding agents by adopting strategies like spec-driven development and test-driven development to reduce bugs and increase productivity.
An AI agent designed to assist developers in writing idiomatic, production-grade Go code for APIs, CLIs, and concurrent services, with features for error handling, concurrency, and project context retention.
The article introduces a CLI tool called 'malveon check' that verifies code completion by running build, lint, and test commands to prevent AI agents from falsely declaring tasks done.
GitHub Podcast discusses AI hot takes, questioning if fine-tuning models for codebases indicates bad code and inviting listener opinions.
A developer recounts spending hours using tools like fable, sol, and grok for code review and simplicity checks, only to produce what they describe as one of the worst interfaces.
ImpactGate is a tool that measures and gates the structural decay introduced by code changes, using a scoring formula to encourage refactoring and maintain code quality.
Ryan Peterman interviews Casey Muratori about computer history, software engineering, and programming practices in a podcast episode focused on balanced tech discussion.
The article highlights how coding agents introduce technical debt in software systems and proposes using tools like ArchUnitPython to enforce architectural rules and prevent structural issues.
Boris Cherny emphasizes the need for higher standards and guardrails when using AI models like Claude for production code to maintain quality and avoid maintenance issues.
The article explores how LLMs can generate correct code but often introduce sloppiness like unnecessary abstractions, and discusses methods to measure code quality, including using AI judges and human evaluation.
This article emphasizes the need for trust in AI-generated code within engineering teams and outlines practices such as accountability, coding guidelines, and deterministic tooling to uphold code quality.
The article critiques the AI model GPT 6 Astra for generating poor-quality code in software engineering tasks despite its impressive capabilities, suggesting that AI training may reward task completion over output quality.
Simon Willison argues that completely rewriting legacy systems from scratch rarely succeeds and typically results in two parallel systems in production. He recommends shoring up the old system with automated testing and targeted refactors instead, citing Will Larson's writing on migrations as the best responsible approach.
Zach Kehs observes that unlike physical buildings, software faces no structural ceiling and can always degrade further through additional layers of indirection and reduced performance.
The article explores whether AI tools are accelerating learning for junior developers or merely enabling task completion without deep understanding, based on insights from experienced engineers.
This article is the first part of a guide to pstack, a personal set of engineering skills and tools that includes verification skills and aids in building high-quality AI applications like Grok Bot.