But with southwest you have the cattle drive to get on the plane and the need to check-in (ASAP!) 24 hours before the flight to get a good spot in the queue. I check southwest when planning trips because of other benefits, but I don't feel less stressed with Southwest.
By default it handles the case of concurrent retrieval on the same key (the second one will just wait for the first one to finish and use that value rather than starting a duplicate computation). It also lets you configure more interesting things like eviction strategies, removal notifications, and statistics.
Last year was a lesson for me in why caches are a hard problem as I had to debug many cache issues from other people not thinking things through... (At least one of the issues was my own fault. :)) Since then whenever someone suggests we use a cache I instinctively pull out a set of questions[0] to ask. The three questions Guava has you consider can also lead you to using memcached or the like instead but my set tries to answer the question "Do you even need a cache?" and if so, generating helpful design documentation.
Is the code path as fast as it can possibly be without the cache? Do you have numbers?
Will the cache have a maximum size, or could it grow without bound?
If it grows without bound, either because of unbounded entries or because of unbounded memory for any particular entry, under what conditions will it consume all system memory?
If it has a maximum size, how does it evict things when it reaches that size?
Are you trying to cache something that could change?
If so, how is the cache invalidated?
How can it be invalidated / evicted manually by another thread or signal? (Debuggability, testability, inspectability/monitorability, hit rate and other statistics?)
Is there a race condition possibility for concurrent stores, retrieves, and evicts?
How constrained are your cache keys, that is, what does it need to know about to create one?
Do they need to take into account global info?
Do they need to take into account contextual information (like organization ID if your application server runs in a multi-tenant system, or user ID, or browser type, or requested-language)?
Or do they only depend on direct inputs to that code path?
Spoiled and overpriced sounds like you don't value them. Is this a reaction to their attitude in the interview or does it start at the resume or email communications?
It starts early at the resume/email communications. I expect to see in communications that a candidate can present themselves in a mature, professional manner. That's something you tend to learn with experience, though it also feels like common sense.
Face to face. I'm talking about people who don't feel the need to in anyway justify why they're there. The discussion is basically a critical assessment of us combined with a mortal combat approach to salary discussions.
Let's be honest: the corporations that hire us will drop us as soon as it becomes convenient to the bottom line, and as likely as not without a severance package.
You owe it to yourself to get the best possible compensation package, because no one else will do it for you.
That happens to all workers, but because technical workers are in short supply, that's why they tend to be spoiled and overpriced. Everyone else learns humility.
I'd like to hear more about it, but maybe there is too much content behind it for the editorial. Are women more likely to accept a bad work environment? Are women more likely to be encouraged to keep quiet? Is being encouraged to keep quiet more likely to be effective on women than men?
I have a stovetop one and without the lid on it's just a big pot. You can brown meat and cook normally in it. The electric ones may have restrictions on that.
