I actually wanted to binge-watch the third season of The Night Agent on Netflix yesterday.
One last reach for the phone.
Somewhere between S3 E2 and S3 E3, it hit me:
I wasn’t really watching.
I had disappeared into posts, threads, and articles.
Prompt Driven Development.
PDD here, PDD there.
Less Netflix, more opinion.
More interpretation.
More projection.
Between two paragraphs, I realized something uncomfortable:
I’m putting the term “prompt” far too much at the center.
And I should know better.
PDD is not prompt engineering.
Prompts are just the interface — not the system.
Prompt Driven Development is architecture work with new tools.
It needs context.
It needs role distribution.
It needs the hard discipline of iteration and review.
The idea of the “perfect prompt” is a dangerous illusion.
It often appears where solid architecture is missing —
or where people hope to replace design decisions with clever wording.
It will probably take some time until this new vocabulary moves
from short-term buffer into actual memory.
Until experiment and hype-coding become what they have always been:
Craft.
Simply: coding.
📌 Publication Metadata
Original Publication:
February 26, 2026
Author: Benjamin Lam (blame76)
Categories: Prompt-Driven Development (PDD)
Original URL: https://benjamin-lam.de/2026/02/26/doom-scrolling-pdd/
Translated with Microsoft Copilot
— A marginal note from the space between two tabs.
Top comments (0)