876 karma · joined August 1, 2016
Known as "Three Strikes and You Refactor"[0]:
- The first time you do something, you just do it.
- The second time you do something similar, you wince at the duplication, but you do the duplicate thing anyway.
- The third time you do something similar, you refactor.
> As we expect the language to evolve rapidly, we strongly recommend using the regular releases instead of the LTS releases for large projects; while this does mean you need to upgrade more often, both us and our users have found that it is generally easier to catch up on 2 months worth of changes 3 times as often than 6 months of changes in one go. We will also be re-evaluating the length of our release cycle; one possibility is that we will move to releases every 4 weeks, with these releases being supported for 6-8 weeks.
That cycle will work for FB where they are constantly iterating and also have early insight as to where the language is going before they get there but for anyone on the outside or for slower moving projects, that cadence seems fairly punishing.
Is that a big change from how they release now?
I used to run or cycle at least 5 days a week but since my daughter was born (and stopped being an infant) it is a struggle to keep a regular exercise regimen.
I try to run with her in a jogging stroller when I can but this is much more susceptible to foul weather than when I could just adjust my own clothing.
I suspect it had to have been people in on the scam because I don’t see how you could conceivably convince strangers to withdraw cash for you at that scale without raising eyebrows
https://www.angelsenvy.com/guide/whiskey-history/why-charrin...
> People have suggested that the inside of barrels were originally burnt to remove the leftover flavors of goods previously stored within, which sounds reasonable enough ... So why do barrel coopers still char the interior? ... Charring the wood actually primes the wood, which impacts the spirit’s flavor in several important ways that have nothing to do with smokiness ... charring essentially opens the wood up, making it easier for bourbon to extract flavors.
> Because it is now popular, and relatively expensive, wine hipsters turn their nose up at it.
Could it be that the so-called hipsters enjoyed the wine priced at $9.99 but not when the price nearly doubled?
Good whiskey takes a while to mature (the lowest PVW ages for 15 years) so if there is a spike in demand, producers cannot react quickly.
Its interesting that there is an article on the front page [0] right now singing the praises of Ghost (ironically named in this case) which does exactly the opposite.
From their careers page [1]:
> Unfortunately due to the volume of submissions that come in whenever we open a position we aren't able to respond to every single application, but if yours is successful - you'll hear back from us within around a week.
The source material [0] that the quote is taken from has a footnote that says "The Cistercians held that rich food increases sexual appetite"
It would seem that the "corruption" here is related to keeping ones libido in check.
[0] https://books.google.com/books?id=cBqgOXfMxAoC&pg=PA26&lpg=P...
Thats incorrect. Calling Thread#interrupted[0] clears the interrupt status and returns true if the current thread was interrupted. Thread#isInterrupted()[1] only returns the value of the interrupt status on the thread receiving the method call. The interrupt status is unaffected by that method call.
[0] https://docs.oracle.com/javase/8/docs/api/java/lang/Thread.h...
[1] https://docs.oracle.com/javase/8/docs/api/java/lang/Thread.h...
Wikipedia[1] also offers some definitions of the hobo slang used in the code:
Boil Up - specifically, to boil one's clothes to kill lice and their eggs; generally, to get oneself as clean as possible
Jungle - an area off a railroad where hobos camp and congregate
There is also the friction of the software itself. Whiteboarding and freewheeling discussion is possible but it doesn’t have the same feel to it
Often new leaders & managers start in an established team and want to change something to "make their mark" or have an impact as soon as possible, often with disastrous results (because they don't yet have the context to make informed decisions).
The advice is to spend time with your team to learn the ropes, figure out the internal politics, hear the common pain points and _then_ start addressing things, hopefully with some quick wins (like canceling a wasteful meeting or appropriating a larger conference room) that due to organizational inertia, went unaddressed.
That is incorrect.
The attackers made requests that were forged to have the sender IP address of Github to multiple public memcached instances. Memcached then responds back to Github instead of the attacker.
This is documented in more detail in the Cloudflare vulnerability report[0]
https://blog.cloudflare.com/memcrashed-major-amplification-a...
> According to Army officials, the delay in distributing the software from the United States to all Patriot locations was due to the time it took to arrange for air and ground transportation in a wartime environment.
I'm not knowledgeable at all on how software for missile batteries was distributed in 1991 from the US to the Persian Gulf but 11 days doesn't seem unreasonable to me.
https://www.cooksillustrated.com/articles/37-foolproof-pie-d...
> Select what shows via searches on Bing, Google, etc. as well as on public profile badges and permitted services like Outlook, when the viewers are not logged-in members or did not bind their LinkedIn account to their account on such services.
Its not anyone who isn’t logged in but rather a subset of unauthenticated users who discover your profile through a specific set of avenues
Clicking on the informational icon next to “public” reinforces what they mean:
>All LinkedIn members as well as others who find you through search engines (e.g. Google, Bing) or other servies.
The American version is “everything but the oink”
I have a question on this quote
> The standard JVM garbage collection strategy is “stop the world.” That is, when the JVM needs to reclaim unused memory, it needs to pause all other processing so it can safely garbage collect. These pauses are sometimes measured in seconds. That is going to destroy your tail latencies.
Thats why applications rarely use the default serial collector.
Does your comparison still hold against the CMS and G1 collectors, which do a much a better job at eliminating "stop the world pauses"?
To my knowledge, it was Flame that did this not Stuxnet, and it was an attack on MD-5, not SHA-1 [1]
A quick glance seems to indicate that cockroachdb takes about 9 minutes [1] and infuxdb about 15 minutes [2]
[1] https://teamcity.cockroachdb.com/viewLog.html?buildId=380603...
If the solution passes some objective criteria that we have, it then forms a significant component of the on site interview where we discuss their solution in depth and have them talk about the decisions they made and opportunities for improvement. Not only does this allow us to ensure that they actually wrote the submitted solution but it gives the candidate the chance to speak from a position of authority on their own code.
His anecdote about Google/Amazon using leap smears to solve the problem is telling. I suspect that they were unable to see outside their own bubble to think about how others may be impacted.
> We did what we always do when there's a problem without a clear solution: we waited
The original problem described the issue and the potential consequences very well and the problem didn't change between the initial report and when cloudflare hit it. It was only until a Serious Industrial User (to borrow a term from Xavier @ OCaml) got bit in a very public way that they actually began thinking about what a clear solution would look like.