{"id":5709,"date":"2018-12-12T13:51:57","date_gmt":"2018-12-12T18:51:57","guid":{"rendered":"http:\/\/www.killersites.com\/blog\/?p=5709"},"modified":"2018-12-12T13:51:57","modified_gmt":"2018-12-12T18:51:57","slug":"proper-documentation-is-next-to-godliness","status":"publish","type":"post","link":"https:\/\/www.killersites.com\/blog\/2018\/proper-documentation-is-next-to-godliness\/","title":{"rendered":"Proper Documentation Is Next To Godliness"},"content":{"rendered":"

Documentation is super important in development. How important, you ask..?<\/em><\/p>\n

…Very.
\n[Throw head back and laugh charmingly & disarmingly – then suddenly and intensely<\/em>]\u00a0 …But seriously it is.
\nWhile it’s not the norm, it is becoming more common that programmers don’t leave proper documentation, be it self describing code, comments (little notes that you leave to yourself in your code) or more formal documentation (ex: what type of database structure did you choose and why?).<\/p>\n

Granted, sometimes you’re doing something fairly straightforward, like a simple authentication object; it’s not really necessary. But for other projects, you’re only really hurting yourself. When you come back in 3 months or 6 months and you don’t recognize the thought process behind the choices you made, you’re going to double or triple your workload.<\/p>\n

Also, it’s just a good professional courtesy from one coder to another. “The worst thing for coders is to have to go into a code base where there’s no documentation, you have no idea what the developers were thinking at the time, and it’s very hard to patch, expand, bug repair; extend a code base where you don’t know the reasoning behind the basic architectural decisions.”\u00a0 Take the time and make everyone’s job much easier and enjoyable…especially yours.<\/p>\n