It is far easier to collaborate on a first principle model. At this level, all discussions are at the level of data structures, key operations, sources of complexity, and so on. It is good to separate this from at the database, programming language, or library you may use to execute those operations, which elegantly avoids those minefields.
The Napkin Math Methodology for System Design
from sirupsen.com
Filed under:
Same Source
Related Notes
- Organizing into services taught teams not to trust each other in mo...from gist.github.com
- I was taken with this cybernetic description of an aircraft factory...from interconnected.org
- These are qualities of a good system that we should strive to fulfi...from Josh Beckman
- The point is to impose a pattern on the way a manager copes with pr...from Andrew S. Grove
- BIG SYSTEMS EITHER WORK ON THEIR OWN OR THEY DON’T. [[Big systems s...from John Gall and D.H. Gall
- "Jobs to be done" is an attempt to identify demand withou...from Josh Beckman
- A pattern as a form/context pair and a generic set of centers [[Som...from Ryan Singer
- Centers and generative process: Any structure is some elements in ...from Ryan Singer