Programmers are bad at managing state (2020)
nolanlawson.com
Programmers are bad at managing state (2020)
1–10 of 60 posts
Re: Programmers are bad at managing state (2020)
#2"There are only two hard things in Computer Science: cache invalidation and naming things.
-- Phil Karlton"
This is cache invalidation.
Re: Programmers are bad at managing state (2020)
#3"There are only two hard things in Computer Science: cache invalidation and naming things. -- Phil Karlton" This is cache invalidation.
I always heard this with "off-by-one errors" included in that list of two.
Re: Programmers are bad at managing state (2020)
#4"There are only two hard things in Computer Science: cache invalidation and naming things. -- Phil Karlton" This is cache invalidation.
There are only two hard things in Computer science: cache validation, off bdata races. y one,
Re: Programmers are bad at managing state (2020)
#5Whenever someone mentions state I think of Rich Hickey's talk "Simple Made Easy" in which he seems almost terrified of state and strives always for pure functions, because as a human he has a hard limit as to how much state he can keep in his head at once when reasoning about the program. He's right. I've worked on enough bad code, including sometimes my own, to know that programmers are bad at managing state.
"Simple Made Easy" - Rich Hickey (2011) https://www.youtube.com/watch?v=SxdOUGdseq4
Re: Programmers are bad at managing state (2020)
#6Re: Programmers are bad at managing state (2020)
#7Re: Programmers are bad at managing state (2020)
#8Whenever someone mentions state I think of Rich Hickey's talk "Simple Made Easy" in which he seems almost terrified of state and strives always for pure functions, because as a human he has a hard limit as to how much state he can keep in his head at once when reasoning about the program. He's right. I've worked on enough bad code, including sometimes my own, to know that programmers are bad at managing state. "Simpl…
[deleted]
Re: Programmers are bad at managing state (2020)
#9[flagged]