Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "cache invalidation"
-
"There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors." - Phil Karlton3
-
1. There are 10 types of people in the world: those who understand binary, and those who don't.
2. How many programmers does it take to change a light bulb?
None. It's a hardware problem.
3. A SEO couple had twins. For the first time they were happy with duplicate content.
4. Why is it that programmers always confuse Halloween with Christmas?
Because 31 OCT = 25 DEC
5. Why do they call it hyper text?
Too much JAVA.
6. Why was the JavaScript developer sad?
Because he didn't Node how to Express himself
7. In order to understand recursion you must first understand recursion.
8. Why do Java developers wear glasses? Because they can't C#
9. What do you call 8 hobbits?
A hobbyte
10. Why did the developer go broke?
Because he used up all his cache
11. Why did the geek add body { padding-top: 1000px; } to his Facebook profile?
He wanted to keep a low profile.
12. An SEO expert walks into a bar, bars, pub, tavern, public house, Irish pub, drinks, beer, alcohol
13. I would tell you a UDP joke, but you might not get it.
14. 8 bytes walk into a bar, the bartenders asks "What will it be?"
One of them says, "Make us a double."
15. Two bytes meet. The first byte asks, "Are you ill?"
The second byte replies, "No, just feeling a bit off."
16. These two strings walk into a bar and sit down. The bartender says, "So what'll it be?"
The first string says, "I think I'll have a beer quag fulk boorg jdk^CjfdLk jk3s d#f67howe%^U r89nvy~~owmc63^Dz x.xvcu"
"Please excuse my friend," the second string says, "He isn't null-terminated."
17. "Knock, knock. Who's there?"
very long pause...
"Java."
18. If you put a million monkeys on a million keyboards, one of them will eventually write a Java program. The rest of them will write Perl programs.
19. There's a band called 1023MB. They haven't had any gigs yet.
20. There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors.10 -
There are two hard problems in computer science: naming things, cache invalidation and off-by-1 errors4
-
There are two hard things in computer science: cache invalidation, naming things, and off-by-one errors.
-- Jeff Atwood5 -
There are two hard things in computer science: cache invalidation, naming things, and off-by-one errors.
This is really the stuff I have to deal on daily basis. -
Today i found variable called "booleanValue". So it IS true, that there are two hard things in computer science: cache invalidation and naming things...3
-
The reason I stick around at my current job is thanks to a mentor who has helped me reach greater potential.
He's our senior architect.
It began with him simply bouncing ideas off me. I was a rubber duck basically. After a while I began to understand these ideas. All sorts of design patterns, cache invalidation problems and solutions, and so much more.
It was almost as if through osmosis that I began to research things and learn more and more about topics I had only barely seen in high-level articles and papers.
Once I began to contribute to the discussion, he helped foster that. I went from being a rubber duck to a protege.
My pay here isn't what it should be. The problems we're faced with are stressful and often times wear me out. I stay because I'm self-taught and I yearn for learning as I always have.
This isn't just my job, but my passion. I love what I do, and I get up happy to come here every day knowing I'll learn something new while doing what I love.1 -
"There are only two hard things in Computer Science: cache invalidation, naming things, and off-by-one errors."
-
The two hardest things in software are naming things, cache invalidation, and avoiding off-by-one errors.2
-
Fuck XCode! -
Yesterday I had the stupid idea to rename an icon file. Checked that XCode was building the application still fine. Ran it over the build server: Failed, complaining about the old missing icon file! Checked again and again, but there was no friggin' reference to the old file in the whole repo.
Log in to the machine clear the build folder and try to build the component again. Bang still same error and the references to no longer existing files reappear.
Turns out XCode was caching those references somewhere in the home directory as "DerivedData" and after deleting those, I could build again... but why on earth are you building a cache if you cannot properly invalidate it? Just to waste our time?
(@xcodesucks)3 -
There are only 2 hard problems in software:
1. Naming things
2. Cache invalidation
3. Off by 1 errors3 -
My old man used to say there are two hard problems in Computer Science: cache invalidation and naming things. :D5