On Establishing Technical Documentation at Mekari


We all hate time wasters. Documentation often is seen as one of these time wasters, mostly because it is boring to do. Planning is often seen as kind documentation, so there is a natural tendency to just skip this step for efficiency. However, people forget the hidden cost of skipping this documentation step: no agreement on shared understanding may cause the project will take a lot longer than people think, and this is only the beginning of other disadvantages of not having proper documentation.

Continue reading
https://panjigautama.com/category/management/documentation/
panjigautama.com
crawl=CC-MAIN-2022-49
43603
application/http; msgtype=response
sha1:UANY3OJQGT46AJ2Q6Q72UKOK6YPECNXI
<urn:uuid:b9bca239-ad0e-42c9-a913-a1a32f6b07eb>
2022-12-03T18:43:10Z
178.128.221.54
text/html
sha1:KI7PKCWKU2XELRHWXHYIHCNCRTE5GZGW
<urn:uuid:9a186c9d-9414-4f23-bfee-0bbc9c3e01b6>
https://panjigautama.com/category/management/documentation/
response
<urn:uuid:0bddef7b-aaa4-4371-8883-a3eafa202203>
isPartOf: CC-MAIN-2022-49
publisher: Common Crawl
description: Wide crawl of the web for November/December 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-51
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/