#Tdd
6 notas · última:
What is the right "unit" in unit testing and why it is not a class?
The talk argues that the right unit for testing is defined by scope and functional boundaries, not by classes, and suggests using heuristics to keep tests focused, stable, and valuable.
Manifesto for Deadline Driven Development
The text contrasts deadline-driven habits with Agile technical practices, arguing that tests, clean code, refactoring, CI, and ATDD are what make incremental delivery and fast feedback possible.
Superpowers: How I'm using coding agents in October 2025
The post describes Superpowers, a Claude Code plugin system built from skills, subagent workflows, TDD, worktrees, and pressure-tested instructions that teach agents to search and use skills.
Test-Driven APIs with Phoenix and Elixir
The tutorial uses TDD to build a Phoenix API for listing movies, adding dependencies, routes, a controller, a view, and a model while showing how each test failure guides the next change.
Programmers Without TDD Will be Unemployable by 2022
The author predicts that by 2022 professional programmers will need routine TDD, with automated unit tests, better maintainability, fewer bugs, and shifts in hiring, training, and tools.
SOLID Code for SOLID Reasons
The post argues that good code should be written for maintainability, with testability as a secondary benefit. It connects SOLID, bounded contexts, and anti-corruption layers to TDD and criticizes using moles or shims to justify weak design.