/ˈɑːr.diː.diː/
Definition
A product-development methodology in which architectural choices are guided less by business needs and more by an engineer’s desire to make their LinkedIn profile look like a TechCrunch headline. Success is measured not in user outcomes but in GitHub stars, conference talks, and recruiter DMs.
Common Manifestations
- Replacing a five-line script with a distributed event-driven microservice “for scalability.”
- Introducing Kubernetes clusters for an app that serves twelve users.
- Suggesting a complete rewrite “to modernize the stack” every 18 months.
- Adding AI, blockchain, or quantum computing “just in case.”
- The phrase “it’s a great learning opportunity” used to justify every bad decision.
Usage Example
“We didn’t need Kafka, but it looks great under ‘Technical Skills’. Classic RDD.”
HR Guidance
RDD is a key driver of professional growth, attrition, and infrastructure bills. While it rarely delivers value to customers, it consistently delivers new career opportunities to developers. Encourage responsible self-branding, and ensure someone eventually builds what was actually requested.