Testing
Post #3378 · source on Telegram
Choosing deadline driven development over TDD, classic two-panel reaction meme
Description
Accessibility details: A two-panel reaction meme using the well-known orange-puffer-jacket template. Top left panel shows the jacket-wearing person turned away with a raised hand in rejection; the adjacent white, all-caps text on the right says “TEST DRIVEN DEVELOPMENT”. Bottom left panel shows the same person smiling and pointing approvingly; the adjacent white, all-caps text on the right says “DEADLINE DRIVEN DEVELOPMENT”. Technical context: The meme contrasts disciplined test-first workflows (TDD) with the all-too-common practice of prioritizing shipping before a looming delivery date, poking fun at real-world trade-offs senior engineers face between code quality and time pressure
More like this
More like this in Testing →
Use J and K for navigation
Comments
9Comment deleted
Deadline-Driven Development: the senior-grade TDD where your unit tests run in prod and their assertions arrive as PagerDuty pings at 2 AM
After 15 years in the industry, I've learned that TDD actually stands for 'Technically Delayed Delivery' - because the only test that really matters to stakeholders is whether it ships before the quarterly earnings call
The irony is that TDD advocates promise it saves time in the long run, but when your PM schedules the demo for tomorrow and you're still refactoring your test fixtures, suddenly 'move fast and break things' becomes the de facto methodology. We all know the technical debt will compound at 40% APR, but that's Future Team's problem - right now, we're just trying to make it to Friday's deploy without the build breaking. The real test-driven development is whether your code survives production long enough to write those tests you promised yourself you'd add 'right after launch.'
We promised TDD and delivered DDD: product thinks Domain-Driven Design, leadership enforces Deadline-Driven Development, and CI implements 'Don't Detect Defects.'
Deadline-driven development: where red - green - refactor becomes red‑alert, greenlight, refactor‑never
TDD: Red-Green-Refactor. Deadlines: Red-F5-Deploy-Pray
Committing that I was unable to do it :❌ Saying that it's farmework's problem:✅ Comment deleted
Now that's a 3D Comment deleted
This is why every time my boss says I gotta finish something by a certain deadline, I respond "why?" Comment deleted