dahvyd

4 ms·

1. 1.▲
   by dahvyd 14y ago

   Sure, if I were publishing a public API I'd want to document the functions available, but the fact is, the vast majority of the code we write at my shop is not consumed outside our own codebase. Why duplicate the effort of writing documenta
2. 2.▲
   by dahvyd 14y ago

   > the core OS enjoys tremendous success and market share. How is that relevant? OSX has at best around 10% global market share? I'm talking market dominance here. > How do you determine the invariants of your APIs when writing cod
3. 3.▲
   by dahvyd 14y ago

   Consider the standard Java cough paradigm used by multitudes of developers, and on by default in many Java IDEs: /* Gets the person's name @returns the person's name */ public String getName() { return name; }
4. 4.▲
   by dahvyd 14y ago

   I work at a shop where we use comments sparingly if at all. Our primary product has 14m LOC and 400k unit tests. We enjoy over 75% global market share in our extremely lucrative industry. We didn't get where we are today by being "lazy" as
5. 5.▲
   by dahvyd 14y ago

   The problem with comments is that they decay into irrelevance and worse, lies (that chapter of Clean Code will live with me forever). You can't write a unit test to ensure comment correctness, but you can for code correctness. Hence the cod