Skip to content
Unknown's avatar

Surfing Complexity

Lorin Hochstein's ramblings about software, complex systems, and incidents.

Tag: documentation

Code is for reading, docs are for writing

  1. The documentation is out of date, you’ll have to read the code. Make sure the code you write will be readable by others.
  2. Write documentation. Yes, it will go quickly out of date, but in the act of explaining how the software works to others, you’ll force yourself to acquire a better understanding of how it works.
Lorin Hochstein software Leave a comment December 12, 2011December 12, 2011 1 Minute
  • lorinhochstein.org
  • Bluesky
  • Mastodon
  • Form may follow function, but use doesn’t follow design
  • The coming coordination calamity
  • Reliability as a game of improving the odds
  • Flipping the bozo bit on flips the learning off
  • How incidents can teach us about what’s already working well
Blog at WordPress.com.
  • Subscribe Subscribed
    • Surfing Complexity
    • Join 249 other subscribers
    • Already have a WordPress.com account? Log in now.
    • Surfing Complexity
    • Subscribe Subscribed
    • Sign up
    • Log in
    • Report this content
    • View site in Reader
    • Manage subscriptions
    • Collapse this bar