A slew of the anime pfp anon on Twitter wouldn’t shut up about this book so decided to give it a go.
~10% through, seem key notes
- Interesting that he juxtaposes
- Science – You shouldn’t know what you are doing
- Engineering – you should know what you are doing
- I get this is mostly semantics on what we call science vs engineering these days, but nonetheless interesting
- To make predictions, the past is best used to serve as a means to determine what underlying forces are at play in historical outcomes
- “The past has always been determined by trends but this future fs is full of possibilities of our own determination” historical accounts can’t always be trusted in determining the historic future
- It is rarely practical to produce the same product by machines than human hand
- This can be unpacked to a lot of domains actually
- What does the product solve, what of the product is needed to solve that, what is not
- ‘During my time working at Los Alamos on the Atom Bomb’ oh okay my guy didn’t know you had it like that lmfao
Through chapter 3
- History of computers – hardware bound
- Clear cut example of S curve in development
- Heavily prophesizing of the 2020’s breakthrough funny enough
- ’We keep thinking of better ideas before we finish our last’ hahhaah
- TIL flops is just floating point operations per sec
- ’Mostly talk and published papers’ bar
- Once your bss says no it’s very hard to get a new answer so don’t let them say no
Through Chapter Histoy of Software
- Humans rely on repetition
- Written language is different than spoken language
- We need a language that models the human animal
- Most will snear at new advancement in their field…’sissys play’
- Fundamental limitations on hardware – Heat, Speed of Light, Distance of a molecule. Software, not clear.
