Two Things
41–50 of 51 posts
Re: Two Things
#421) You are playing The Game 2) You just lost The Game
Re: Two Things
#43"There are only two hard things in Computer Science: cache invalidation and naming things" - Phil Karlton http://people.famouswhy.com/phil_karlton/ (NB: "hard" things) While we're being flippant: Every problem in computer science can be solved by adding another level of indirection - except for the problem of too many levels of indirection
and off-by-one errors http://martinfowler.com/bliki/TwoHardThings.html
Re: Two Things
#44For Biology, "Ontogeny recapitulates phylogeny" is wrong. http://en.wikipedia.org/wiki/Recapitulation_theory Instead I would say: 1. Some things can replicate better than others. 2. Things replicate imperfectly, causing change over time.
Re: Two Things
#45Another thing I ask people, just out of curiosity since it's not insightful at the same level, is to just go through their average day. Sort of like a bottom-up description of their work/study/whatever live, instead of the top-down answer you get when you ask "so, what do you do".
Some people may think it's weird, though.
Re: Two Things
#46- Do it today
- Repeat
Re: Two Things
#471. There are no safe assumptions.
2. Relate.
Re: Two Things
#48Two things about The Game: 1) You are playing The Game 2) You just lost The Game
Re: Two Things
#49Computer Science: 1. Your code always does exactly what you tell it to and never anything more. 2. You probably don't actually know what you're telling it to do.
3. It's never a bug in the compiler (except when it is).
Re: Two Things
#501. As it gets complicated add indirection/abstraction
2. Its about talking to people not machines