#217 – RDD
These lines from rdd.io describe Résumé-Driven Development very well:
• Specific technologies over working solutions
• Hiring buzzwords over proven track records
• Creative job titles over technical experience
• Reacting to trends over more pragmatic options
As an Architect, you’re constantly in grave danger of becoming a proponent of RDD because you need to be on top of the new technological possibilities, architectural patterns, frameworks, tools, methodologies and trends. It’s only human to want to try all of that out so you can add it to your LinkedIn profile—and the Developers won’t stop you. Just remember that you’re (probably) not hired for your next job because of your knowledge of fancy new buzzwords, but because you helped your current company create an Intentional Architecture that suited their business needs and context—emergent and evolvable or not.