Documentation Driven Development 👐 Web AddiCT 🇿🇦

I’ve recently been attempting to port our iDRIVE.co.za site into CakePHP framework for many reasons, with my previous experience with Ruby on Rails, it’s been going alright so far.

While searching for some plugins and code snippets I could use to ease the process I came across this development methodology which seems to me the an excellent approach to any software development.

It’s called Documentation Driven Development (DDD), basically you write the documentation for the system your going to develop before actual development. This has whole bunch of benefits especially for those people with Documentation Deficiency Disorder like me.

Have a look at a more detailed description of Documentation Driven Development at the place where I found it. I’ll definitely give it a try in the near future.

Question: What do these things all have in common? Everybody know…

👐Let’s Explore Barcodes: Types, Uses and Characteristics. When it comes to barcodes South Africa has many different forms and every one of them has its own exclusive symbolism and…

👐The jfGi.cc Origin Timeline (updated) This is a journey of multiple ideas spanning from the origins of the first chatbot spearheaded in 2007, ideating and the creation…

👐The Role of Digital in Estate Administration: Harnessing Technology to Ease the Transition Estate administration can be a daunting and complex process, especially when dealing with the loss of a loved one. Traditional methods often…

Tania says:

24 July 2006 at 14:19

Pavatile’s boss uses a similar approach with numerous people in the company — not just for programming. Several employees have personal tasks databases in which new tasks have to be documented and the rationale of the task (how it fits in with specific business goals) must be recorded so that you will remember what you are working towards. The task document allows you to insert comments or additional instructions, and even attachments. Some people’s paper filing systems also integrate with the task numbering. It sounds huge and comprehensive, but it’s actually quite simple; and yes, although it means you have to spend extra time documenting things, it actually makes you more efficient if you use it.

Miguel says:

24 July 2006 at 16:19

TYFYC. This does seem the best approach. Only that it is long and tedious, but then again rather get the job done right first time rather than jump right in and confuse yourself.

Just for today. You're one too.

Documentation Driven Development

Question: What do these things all have in common? Everybody know…

Leave a Reply Cancel reply