Respecting Upstream | Morgan Gallant

There's generally some good advice in software best-practices manuals, i.e. global variables are probably bad, and writing some documentation is likely a good idea. One of the things I don't see written in most software manuals, which I really wish would be included (and is good life advice in general): respect what came before you. First, a bit of context. A few months back, I started a little software studio which aimed to build everything from scratch with as few software dependencies as possible. Since then, I've done a good bit of thinking about what it means to be "dependency-free", and how it's an ideal that isn't possible realistically, and likely something which shouldn't be aimed for in the first place. A particularly snarky individual could probably argue that all software built today isn't "dependency free" inherently, since the developer likely didn't write the compiler, develop the operating system, build the computer, or manufacuture the silicon. Ok fine, fair enough sma

saved by

• Arielle Lok
• Aaron Pham