#Code-Quality
14 notas · última:
Importance of Writing Clean Code
The page argues that clean code helps other people understand your work, reduces future confusion, and makes software easier to maintain, debug, and extend in team projects.
Refactoring
The newsletter argues that refactoring keeps a codebase healthy, easier to maintain, and simpler to extend, and recommends doing it incrementally with tests and IDE tools.
Clean Code: The Good, the Bad and the Ugly
The article praises Clean Code for naming, readability and code-smell awareness, but criticizes its outdated Java focus, dogmatic advice and verbose examples, especially the prime generator.
No excuses, write unit tests
The text argues that unit testing is worth the upfront time because it exposes how functions behave, makes API changes visible, and catches bugs before they reach production. It also says that writing tests often leads to clearer, smaller, easier-to-test code.
AI Is Forcing Us To Write Good Code
A six-person team enforces 100% code coverage, thoughtful file naming, and fast disposable dev environments because coding agents need the guardrails humans used to skip under deadline pressure.
Great Developers Build Sustainable Readable Systems
00:11:28 — Great Developers Build Sustainable Readable Systems
Code Is Communication: Humans First, Machines Second
00:08:48 — Code Is Communication: Humans First, Machines Second
The Importance of Clean Code in Your Startup's Success
The post argues that clean code helps startups win investor, customer, and partner trust, while reducing tech debt and making changes easier. It also lists basic habits for keeping code readable, consistent, and maintainable.
CUPID - for joyful code
The page argues that code becomes more pleasant to work with when it is composable, follows Unix philosophy, is predictable, idiomatic, and domain-based, with each quality reinforcing the others.
5 things I wish I knew before starting serious development (a journey into code perfection)
The article argues that clean code depends on intention-revealing names, minimal comments, consistent formatting, short focused functions, and a team mindset that improves shared code.
Books to Read as a Developer
The post lists books a developer should read for programming practice, code quality, design patterns, legacy code, team work, and software design principles across languages.
Giving better code reviews
The article argues that code reviews should go beyond a quick approval. Reviewers need a light pass and a deeper contextual pass, keep diffs small, and ask questions that improve code quality and team understanding.
Nobody cares about your code
The article argues that code is only a tool: programmers are judged by the product and its features, while code quality matters because it helps deliver that product well.
11 Rules All Programmers Should Live By
The article lays out 11 guidelines for programmers: treat technology as a tool, favor clarity over cleverness, write only necessary code, test work before shipping, keep learning, and simplify.