Skip to content

Instantly share code, notes, and snippets.

@dgcoffman
dgcoffman / Moving Quickly, Safely.md
Last active June 1, 2023 05:43
Moving Quickly, Safely

Don't run in place

  • Don't upgrade a dep unless you can articulate how the new version is better.
  • Don't switch tools unless you have a good reason. Because you heard the new thing was good, or because you think the current tool is bad is not a good reason. How is the old tool failing? List the ways. Steelman the argument that you should not switch.
  • Don't re-write anything unless you have a good reason. You not personally having written the old thing isn't a good reason.
  • Some framework fads are more worthy of adoption than others.
    • React.createClass -> classes -> function components -> containers -> HoCs -> render props -> hooks. Rewriting the same code through all of these changes is the full time job of a useless engineer.
    • Be judicious, wait a while and see how things work out for other people. Ideally, wait until you see the backlash after the initial hype. If you haven't seen any backlash, you might not have waited long enough to adopt.

Don't externalize your internals

@protrolium
protrolium / build-caffe.md
Last active August 23, 2017 00:05 — forked from kylemcdonald/build-caffe.md
How to build Caffe for OS X.

Theory of Building Caffe on OS X

(with addendums, tangents, and other follies)

Introduction

I have followed Kyle McDonald's Theory of Building Caffe after what could be described as some careless brew updates and obliviousness to the conflicts between various versions of OS X, CUDA, CUDA drivers, CuDNN, and Caffe itself. I am replicating Kyle's steps here and adding a few more which were unique to my case and may not necessarily work for everyone. The goal is to run python -c "import caffe" without crashing.

Official Caffe OS X Installation Guide

http://caffe.berkeleyvision.org/install_osx.html