Starting a new J2EE project is a daunting undertaking. The technology choices alone are myriad and bewildering. Can you afford to fail by not using RDD?
Chances are you've not heard of this new approach to software development. Not many have right now, but it's growing fast. It's no exaggeration to say that those who follow RDD wonder how they ever managed without it.
RDD uses an industry standard toolset to simplify J2EE technology strategies and implementation choices. Furthermore, RDD supports all common J2EE solutions in the marketplace, with support for new ones is being added all the time. So RDD can accommodate your future needs.
The unique and powerful algorithm underlying RDD takes into account the current skillset and any gaps, with the result that your project is guaranteed to use the most appropriate technology. No RDD project has ever ended up in a technological cul-de-sac.
Research has conclusively shown that RDD practitioners have increased marketability and earning potential. There is a direct correlation between the use of RDD and personal empowerment.
 |
“RDD enables me to change my BMW every six months, instead of every two years.” |
RDD is Resume-Driven Development. Find those buzzword gaps on your CV and plug them.
2003–2024 John Topley
Comments
There are 3 comments on this post. Comments are closed.
Hilarious, I hope this acronym catches on :)
All this time I've been using RDD without realising it! Now I can put a 3 letter acronym to it I'll have to put it on my CV... Thanks John!
Don't mention it, John. It's good that there's a .NET port of RDD now available.