When stuff like this makes the front page on a regular basis, it's already a joke site:
283 karma · joined October 17, 2013
Like this?
http://i.imgur.com/W1s9crO.jpg
In all seriousness, I feel it is only a matter of time before someone dies as a result of their home automation being hacked.
A good people manager works to keep their employees comfortable, aims to avoid conflicts (and resolves them if they arise despite these efforts), mentors and coaches people to develop new skills, and shields them from politics. Doing the work of an individual contributor just gets in the way of that. The manager should be familiar with and understand what their people do, but leave the actual performing of that work up to them.
http://www.theatlantic.com/technology/archive/2012/11/when-t...
It seems today's politicians are (at least in some cases) familiar with what it takes to build reliable software. Perhaps the problem is that they are only willing to see that it's done when it benefits them directly, but not when their constituents need it.
For how many years were people dismissed as nutjobs and "conspiracy theorists" when they talked about NSA spying? Now we know it was all true. Would you like to make a bet as to whether or not the US military-industrial complex acts in its own self-interest when comes to the "War on Terror"? When it comes down to it, there is nothing particularly "extraordinary" about these claims.
> You have made these accusations without any evidence.
The evidence is circumstantial and based on past behavior patterns of the US government. Read "Decent Interval" and its follow-up "Irreparable Harm" by Frank Snepp, or "State of War" by James Risen (for something more recent) to get started on this history. Again, there is nothing "extraordinary" about the previous poster's claims.
https://github.com/cisco/openh264/blob/master/codec/encoder/...
Where does "15" come from? I suppose if I'd written a codec like this before, or if I stared at the code long enough, I could figure it out, but wouldn't it be better to use an enum or a #define?
[1] http://www.justice.gov/opa/pr/2010/September/10-at-1076.html
[2] http://www.macworld.com.au/news/apple-and-google-face-salary...
Not that I agree with the guy in the video in any way, but I 100% •guarantee* the protestors (and the writers at the Guardian for that matter) have their own ideas about who the "right people" people are to live in SF, and that these ideas are not exactly absent from their motivations when protesting or discussing these issues.
VC-backed, too!
Many companies pay for the corporate Google Apps service which provides email, calendar, chat, etc. The argument of "you're no longer the customer, you're the product" doesn't apply here, since ... well, you're paying for it. And yet, Google has insisted on integrating Google+ here as well. You can't even fire up your corporate chat which your company pays for without being harassed to create a Google+ account and create some "circles".
Not that long ago, I recommended to anyone who would listen that any small-to-medium sized business should use Google Apps for their email & calendar needs. It was a great service that met all the basic needs without getting the way. Today, I no longer make that recommendation. Instead I tell people to stay as far away from Google as possible, as they clearly cannot be trusted even when supposedly being paid for a premium service. This whole deal is going to be the downfall of Google.
If some snot-nosed teenager scanned a book and posted it on the web, the court would squash him like an insect. But a multi-billion-dollar company with an army of lawyers at their disposal scans every book and puts them all online, suddenly that's "fair use".
It's like the old saying: if you owe the bank $100 you have a problem, but if you owe the bank $100 million, the bank has a problem.
This also further goes to show: if you want Facebook's attention, do something with photos.
It is of course possible to write a post-receive hook that denies non-fastforward pushes to specific branches, but really, git should include a config option out of the box to do this at a more granular level. A common workflow is the expectation that people should be able force-push to their own topic branches all they like, but never to the default branch (except in extreme circumstances). Being able to easily set this via a config option would be very helpful in keeping working repos more "safe" from this kind of thing.
The only explanation as to why they are continuing to push forward on this front even in the face of increasing criticism is that it must be working, at least in the sense that the number keeps going up. However, these UX nightmares are eventually going to catch up with them and drive people away. In short, they are going to win the battle but lose the war.
Before anyone jumps on me for not seeing it from the cyclist's perspective, I spent several years commuting by bicycle, frequently going home after dark. During that time, I made damn sure I had enough lights and reflectors for car drivers to see me. I was never under the impression that basic safety was anyone's responsibility but my own.
That of course doesn't mean that there aren't car drivers out there who are careless around cyclists, but cyclists themselves have to take the first steps, such as making sure you are visible to everyone around you, (including avoiding getting into other people's blind spots), and above all maintaing awareness and caution at all times. I realize I probably sound like a school teacher, but they say these sorts of things for a reason. A cyclist with cavalier, reckless, or lackadaisical attitude towards safety is an accident waiting to happen.
If they can make it, so can any other company.
http://en.wikipedia.org/wiki/5_Whys
which is almost always a good thing.
https://news.ycombinator.com/item?id=6564469
and of course the reaction was denial & vitriol.
It bears repeating: the world's governments can be divided into exactly two groups -- those that are monitoring the internet, and those that are trying to. Vigilance must be applied to all of them, not just some.
Just do a textual search for "insurance" in the article. Zero results found. Yep, it's "disruption" all right! Full speed ahead!
I thought this was common knowledge?
Yeah ... no. I got fed up with taxi service in SF about 2 years ago and started using Uber. At first I was astounded: very clean cars, very nice drivers who were accommodating and pleasant (all I want is a quiet ride without the radio blaring or the driver shouting into his phone the whole way). Best of all, the drivers were knowledgable about the city and didn't need me to tell them turn-by-turn how to do something basic like get across town. It was what I always wanted, and totally worth the extra cost vs. a regular taxi.
It's hard to put my finger on exactly when it started, but in the last few months the "black car" service has degraded to the point where it feels like the old taxi days. Usually the car is dirty, smells bad, the driver has the radio blasting loud (and doesn't exactly react all that well if I ask to turn it down or off), and the driver's attitude is frequently incredibly grouchy (I've had to listen to them complain about their jobs quite a bit lately), and worst of all, they don't know their way around the city at all.
Just to make sure I wasn't experiencing what Mr. Kalanick is suggesting in terms my expectations being calibrated differently, I have made it a point to take regular taxis a few times lately. Instead of a categorically different experience (which is how I would have described the difference between Uber and a taxi in the past), the only differences now between the taxi and the Uber "black car" service seem to be the price and the color of the outside of the car. Oh, and in some cases the regular taxi drivers actually know the city better than the Uber drivers.
I don't really blame Uber for all this, as I'm sure it's really hard to maintain that level of quality while growing at double-digit rates. But I do think they need to take a good hard look at the "black car" service and make sure the drivers know what kind of experience they are supposed to provide. It really should not feel like a taxi with a different coat of paint on the outside.
People hear what they want to hear.