High quality documentation leads to better results – less time is spent wrestling with the framework or head-scratching about why something is working the way it is, and more time is spent making your project its best.
“It’s going to be a music machine – like, full keyboard and everything – but
each of the keys is going to be mapped to – wait for it – cat sounds! We’ll call
it the ‘Meowsic Machine’! Oh, and we need it to be accessible to everyone via the
Web. Which is easy, right?
You are reminded that the universe can be a cruel place.
It’s now your job to make this happen.
A young developer, new to the Tao of the client-side, comes to a Master of the way, and speaks thusly: “Oh Master, our application nears completion; and lo, cat pics can be drawn upon, and captions fixated thereto, for the creation of humour and the bounteous enjoyment of our users.”
“This is good,” responded the Master.