Tagged “notebook_practices

  1. Bi-dimensional commit messages
    The useful dimensions of a change, at a glance
  2. Comment the code that is not there
    So your coworkers don't have to find out the hard way
  3. Data that grows together, goes together
    If it's conceptually interdependent, make it programmatically interdependent
  4. Four patterns for developer-friendly, production-grade NodeJS services
    Originally written for people onboarding a project I've been leading, to explain why services are structured the way they are, and to provide a set of reasoned guidelines
  5. [draft] Structuring projects to guide and inform (for React applications)
    A project's structure speaks. Does yours say useful things?
  6. The dangers of greedy functions
    Functions that ask for more than they need trick into writing risky code

See all tags.