kscaldef

Yeah, that was my reaction as well. My wife and I each drink a couple liters a day. Our Sodastream is one of the best purchases we ever made. We save money, we're not lugging bottles home from the store, and it's better for the environment.

I don't believe this satisfies the Condercet criterion either. Consider these rankings of preferences:

    20% A ...
    20% B ...
    15% C ...
    15% D C ...
    15% E C ...
    15% F C ...

In a two-round run-off, one of A or B will be elected, despite the fact that 60% of voters prefer C over either A or B.

Your SSN was never intended to be a secret, and the fact that anyone ever treated it as such was a flawed idea.

Unless you actually randomly select the words, I'm fairly sure that the analysis of strength of that strategy is flawed. And if you do randomly select the words, I'm not sure how easy they are to recall. And, I'm really skeptical how easy it is to recall different word sequences for 100 different web sites.

I've quizzed most of the people I've encountered who claim to use this technique. They all use four words that "pop into their head". That's quite a big different from using random words, and almost certainly much weaker.

I object to Facebook making this decision for me. I _didn't_ add too many friends. My newsfeed _wasn't_ overrun. Yeah, I had to hide a few annoying Apps, but no big deal.

And then, one day, I stopped seeing posts from lots of people, including many of the people I most wanted to see posts from. It took a while before I even realized this was happening. Then I slowly had to go through and fix the settings for people to tell FB that "yes, really, show me all the posts". And, still, every couple of days Facebook forgets that I've set my sort to "Most Recent" and goes back to "Top Stories" and not showing me everything. This gets tiresome, to say the least.

I'm not sure why it should be, as there's no irony to be found. That sentence is neither contorted nor incomprehensible nor a muddle nor a disaster. One might argue on the issue of whether it's pretentious, but given the target audience of other academics I would lean towards saying it's not.

Have you tried LeechBlock?

If your wife expects you to support her financially. Fortunately, such arrangements are no longer mandatory.

Off-hand the following categories occur to me: co-workers, classmates, random people at user groups you attend (or any other club-like group), family members. In all these cases, you don't have control over the complete set of people you interact with, so "wanting to be in the company" of them is not relevant.

> Hmm, I'm not sure I like the idea of intentionally trying to steer the candidate off on a tangent. It feels like a trap.

And, yet, it's quite a realistic model of what happens in meetings and presentations all the time.

> In an interview, the interviewer literally has all the power, and saying "no" or refusing to answer a question posed by the interviewer seems rather difficult.

You could say the same with regards to managers or other higher-ups in real workplace environments. It's an important skill to be able to say no, or deflect gracefully.

In this situation, saying "I'm not going to answer that question" is the wrong response. Something like "that's an interesting question, but it will take more than 5 minutes to answer. I'd be happy to go into more detail later if you'd like." is.

gerrit's permission system goes a good ways in the direction you're talking about. (Unfortunately, it's rather baroque and poorly documented.) You can specify who can submit patches, who can approve them, who can merge, whether a repository allows merges at all or requires rebasing or cherry-picking, etc.

Maybe they have private offices.

Most co-working spaces that I've looked into had options for fixed desks. Even if they don't, it might be nice to think you can go get lunch or a coffee without someone taking your desk (or ethernet cable)

A lot of this stuff is open to interpretation by auditors. SOX doesn't literally specify any of this sort of stuff.

In my experience, SOX usually ends up meaning that developers don't have access to production systems, or significantly limited access. However, a continuous deployment system should generally be very much in the spirit of SOX, in that it's pretty hard to do without well-defined, highly-repeatable, automated and auditable processes.

    You could swap `book' and `author' with `code' and `programmer' and you get the open source model.

Except that typically programmers write open source code which they then use directly themselves to do other things they want to do. An author probably doesn't get much pleasure or utility out of reading their own book.

    Writing a good story could open doors to writing a movie scenario...

Except that presumably you want that to be given away for free too.

    Data must be free, and this is far more important than how someone can make money on it.

A book is not "data".

Personally, I'm willing to lose monotonicity. I mean, it's only Twitter. If I don't see every single message because I didn't scroll back far enough, I don't really care.

TFA: "Herd immunity occurs when a few unvaccinated children are protected by the fact that almost everyone around is vaccinated and therefore cannot infect them. It's important for those for whom vaccines have not worked, those who have immune problems, or those who cannot be vaccinated due to specific health risks"

You're missing the point in two ways

a) "Starbucks" serves in this situation as a generic term for an espresso drink of your choice. Like Kleenex or Xerox or what-have-you. When someone says "people will spend $4 on a coffee at Starbucks without thinking about it" they don't mean at Starbucks specifically, they just mean "some coffee shop that isn't 7-11 or Dunkin Donuts or McDonalds".

b) Even within the category of espresso-serving, $3ish coffee shops, the argument still applies. In a strange town (), in the absence of other reliable information, I will probably go to Starbucks because I know that I'll get a somewhat over-roasted, but drinkable, latte. If I walk into a random independent coffee shop, there's some chance I'll get an excellent cup of coffee. But, experience has also taught me that it's more likely that I'll get something that's no better, or frequently worse, than Starbucks. Similarly, if I'm out of saline or need some allergy medicine while traveling, I'm likely to grab it at Walmart, because all their stores are laid out the same and I can find what I need blindfolded. There is value in predictability in many situations.

() caveat that this applies to travel in the US, and generally for work. In various European countries, I'd bet on the random local shop. And if I'm traveling on vacation, there's value in experiencing something new and local. But, if I just want my morning coffee on the way in to the office, easy and predicable wins.

Much more extensive and detailed information is provided by https://github.com/hoxu/gitstats

I think there's a plus and a minus to the class navigation features of IDEs. Undoubtedly they make it faster to find your way through a thread of code, helping you to avoid breaking concentration and flow. However, I also observe that many of my colleagues who exclusively use an IDE never actually learn the structure of the codebase. Starting in on a bug or a task from scratch, they don't have the instinctive knowledge of what file & method to go to straight away to start working on the problem which I feel like I've gained via time spent navigating the codebase more manually.

I'm glad that hosting dinners has worked well for you, but my experiences attempting the same almost exactly mirrored the descriptions in the NYT article. I.e., long and exhausting back-and-forths trying to find a day that works for all parties. Even trying a fixed day, as you did, didn't work so well, as it became this complicated and frustrating experience of having to "book" someone's Weds weeks in advance and keep track of which of our friends and acquaintances were available when.

Many companies have a policy for bereavement leave. The amount may depend on your relationship to the deceased. For example, it might be a week for a parent, spouse, or child; 3 days for a grandparent; etc.

Hmm... I suppose policies may vary, but in my experience exactly the opposite tends to be true. Sick days and personal days vanish at the end of the year while vacation days generally accumulate (sometimes with a cap, though). It's fairly common for people with separate pools to use "sick" days to just take a day off to recharge or run errands. (Although, technically, employers often have the right to demand a doctor's note, but seldom actually do so.)

    This is how people work and it will not change anytime soon. Everybody needs weekly check-in with the company (represented by the manager) to stay in course.

I call bullshit. I have over a decade of experience in this industry and have only had regular 1-on-1s with my managers over the last year. Despite this, I've always been a highly valued contributor to the companies I've worked for. If anything, the last year has been the worst / most-dysfunctional of my career (although, this is probably not related to having 1-on-1s, but rather unrelated organization chaos). I have always talked regularly (i.e. daily) with my manager, but formal 1-on-1s were never part of the equation.

While many projects / companies work as you say, the linux kernel development model has always been much more like how github does forks. Git was designed to be truly distributed and de-centralized, although many people choose not to use it that way.

My double degree required completing 150 credits, rather than 120 credits for a single degree with double major (the equivalent of an addition year of courses). I can't recall at this point if there were any additional course requirements, but I don't think there were.

Really? I think there's far, far more mocking and pity and criticism going the other way.

Frankly, the most of the "parties" at most conferences _aren't_ good. Mostly, "party" just means an open bar and, if you're lucky, some light nibbles, either in the exhibit hall of the conference center or in a tacky hotel restaurant.

I figured this was likely to explain almost all of it:

    Founding Team Composition: Silicon Valley founding teams are 34% more likely to be technical heavy than founding teams from NYC. Whereas NYC founding teams are almost 2x as likely to be business heavy than Silicon Valley founding teams.