3 ms·
> Abstract academic terms are certainly useful insofar as they provide a shared language to discuss systems and discover research, but... it really does actuall
by bob1029 5y ago
> Abstract academic terms are certainly useful insofar as they provide a shared language to discuss systems and discover research, but... it really does actually seem to be the first principles things, the physical facts, like cache lines and latency ("practical engineering constraint solving" as you put it well) that drive the best designs, and far ahead of things like database normalization.
If you have a problem domain that deals with thousands (or more) of types/facts/relations, you will quickly find that starting with code and how tightly you can pack your data in memory to be a massive mistake. The computer is arguably the most important stakeholder in all of this design work, but it is not the only critical one for most businesses. Being able to express a complex state machine to a domain expert who doesn't know what visual studio looks like is the biggest challenge I run into in the real world.
"Correct" is more important than "fast" every single day of the week where I work.
- jorangreef 5y ago"If you have a problem domain that deals with thousands (or more) of types/facts/relations, you will quickly find that starting with code and how tightly you can pack your data in memory to be a massive mistake." To be fair, this depends entirely on the business requirements of the software being designed. For example, a safety critical airbag deploy mechanism may need to make hard real time decisions so that memory layout (let alone dynamic allocation) is anything but "a massive mistake", or a file system may need to account for the spatial locality of corruption by writing superblock headers to different locations on disk. I was also thinking of software design, not business applications that can be solved with SQL, and specifically in the context of infrastructure systems designed by experts such as Jeff Dean or Martin Thompson.