391 karma · joined December 12, 2008
“The more an owner, for his advantage, opens up his property for use by the public in general, the more do his rights become circumscribed by the statutory and constitutional rights of those who use it.”
I'm not a 10x person, but I have worked with some. I don't think they are unique to programming..there are 10x folks in every field.
Sometimes you don't need a 10x person, and if you don't, it can seem like they don't matter. In those cases, a few 1x people will do just as well. But I do believe that sometimes you _do_ need a 10x person, and if you do, you can't do the same things without them. In those cases, I'd absolutely take a 'toxic' 10x person over the nice-but-1x alternative.
Part of the issue is that there's more work for programmers than ever, and most of that work is of the 1x variety.....if you're just banging out CSS for some small-business website, it doesn't matter whether you have Jeff Dean do it, or a new grad from Omaha Community college. If, however, you need to write a new globally consistent database abstraction at scale, then the new grad probably won't cut it. If you actually need that thing, then it wouldn't matter if the new grad was the nicest person on earth, and Jeff Dean the most 'toxic' (though actually I understand that he's a very nice person).
" The followers advice is dropping the curly brackets for these one-line ifs to make them all happy. "
I have never understood why anyone would do this. It's a bug waiting to happen (as goto fail showed), for truly marginal benefit
if (foo)
bar();
if (foo) {
bar();
}If either of these assumptions is incorrect, then your question is meaningless.
It is uniformly excellent, and well worth the time commitment required to listen to the whole thing.
I've also enjoyed watching several episodes of "The Great War" on youtube, which seems to be of a similar quality. ( https://www.youtube.com/user/TheGreatWar )
I realize this isn't a substantive argument about the issue at hand, and will be rightfully downvoted..but I think this might be the first time I've _ever_ been so daunted by the ridiculousness of an idea, that I can't begin to formulate arguments against it, solely because I can't tell how to frame the argument.
Without the possibility to use the hijacked plane to take hostages to a friendly destination, or to use the plane as a missle, it's no more attractive as a target than any other public space.
What if I spend my basic income on drugs and hookers? are you willing to let me starve? what about my kids? If not, then the basic income can't actually replace the existing social programs.
If nobody need to work, then if employers want employees, they have to pay more to get them, which makes prices rise, which makes your 'basic' income insufficient again.
I don't get it.
It's much more likely that over-prescription of oxycontin is the root cause of any increase in heroin use.
How about donor organs? is there some infinite source of hearts and livers out there I'm unaware of?
Once you accept the fact that a given resource is rivalrous, you have to come up with some way to distribute it. Currently, that mechanism is money. If you get rid of that, then you have to replace it with _something_..whether it be algorithms, favor-economies, or central planning.
Now if you want to argue that insurance companies distort the market, then I probably agree with you (though I think there is room for interesting discussion here...). Certainly I think a single-payer solution is preferable to the current status quo, which mandates that individuals purchase insurance from private companies.
As I get older, I have mellowed a great deal, and I understand how smart people can reasonably disagree about a large number of things...but I honestly can't fathom how intelligent people can fail to grasp that you can't possibly have a 'right' to a finite, tangible resource which you yourself don't produce.
“Though all winds of doctrine were let loose to play upon the earth, so truth be in the field, we do injuriously by licensing and prohibiting to misdoubt her strength. Let her and falsehood grapple, who ever knew truth put to the worse, in a free and open encounter.”
Even if they are applied to specific companies (to favor domestic companies, for instance), then they still have largely the same effect, since they allow the domestic competitors to compete in the market inefficiently, raising prices on the consumer.
1. It is attempting to unify a bunch of previously disconnected functionality into a single program. Typically unix is composed of small single-purpose utilities that perform a single function, rather than a giant monolithic blob of code (with obvious exceptions, like emacs).
2. Partially because it has been around for so long and has so much history, and partially because it follows a unix tradition of using plain text configuration and shell scripting to solve problems.
3. The systemd folks believe that sysv init isn't capable of doing things that are important to modern systems (ex. dependencies between services, reacting to devices coming and going, intelligent daemon management, etc), and that doing those things correctly requires that an init system be 'more' than people previously thought it needed to be. They are also very....confident in their ideas, and don't hesitate to re-implement functionality (like logging) if it makes is easier to interoperate with their other code.
People opposed to systemd believe that it is too complex for such a critical piece of system functionality. They also resent the fact that systemd seems to require tight coupling to the rest of the system, and that it is aggressively pushing into so many linux systems. Many of them also probably have a long history with sysv init, and are comfortable with the way that it works. (Some portion also probably recall pulseaudio, which had similar grand visions, was similarly aggressively pushed into use before it was fully baked).
4. I think 1-3 probably cover most of this.
sure
for ()
foo
saves you a line, but it's a bug waiting to happen.2. Well, it certainly is true that more code and more functionality is likely to contain more bugs. Whether your pid 1 needs to be doing all the things that upstart does is obviously a contentious issue.
3. This is a toss-up. I usually like 'crash loudly' over 'fail silently', but I think rejecting the patch outright was a poor decision.