The wifi drivers are the only area that doesn't have perfect linux support, but the 3.18 kernel is a drastic improvement, and more are coming.
Also, the price is right, mine was only $1000.
675 karma · joined June 25, 2012
San Francisco -> Berlin -> NYC
Core Maintainer, Pelias Geocoder (http://github.com/pelias/pelias/) Founder of geocode.earth (https://geocode.earth): open source geocoding hosted services and consulting Formerly of Mapzen
https://juliansimioni.com
The wifi drivers are the only area that doesn't have perfect linux support, but the 3.18 kernel is a drastic improvement, and more are coming.
Also, the price is right, mine was only $1000.
It's not a signal of the end of our battle for privacy, but it's something.
As someone with a computer science degree who was warned of such risks and studied the Therac-25 in my classes, this sentence made me realize how far we have to go as professionals. Something seemingly so simple as incrementing a number, one of the most common things done in a program, can cause serious problems (of course we have more help with this now than in the mid 80's). Other people must read things like that and cement any distrust they have in computers and computer programmers. And they're probably right to.
However there truly was never an unknown software bug discovered in flight. Lots of known software bugs had workarounds, partially because there was a hard deadline of about 4 months where the software couldn't be changed before the launch. Pretty amazing.
Its popular to dismiss the AGC as simple and uninteresting, but it was a challenging engineering task, and it never once had a failure in flight.
There's lots of resources on the internet to read more. A great book on the topic is Digital Apollo by David Mindell
Somewhat related, I notice a trend where journalists seem to treat Moore's Law as if it were a law in our judicial system, rather than simply an observation that has been clearly stated by someone knowledgeable and prominent in the field and has held true for some time.
Sentences such as "Since that time, his[Moore's] Law has been modified", makes me wonder if the author is envisioning some legislative body voting on a resolution to change the rate at which new transistors shall be added to the next generation of CPUs, or something silly like that.
Anecdotally this seems to match up with my experiences coding. Sometimes I'm more or less just churning out code, and music is great. If theres an ops crisis, or I'm trying out something new, music can hurt rather than help.
Edit, forgot the article: [1] https://medium.com/what-i-learned-today/be3172896a0f
Proclaiming "I won't use Sqwiggle because then people could see me" is exactly the same as saying "I won't work at my desk because people can see me". Both traditional offices and Sqwiggle allow one to achieve privacy if they'd like. For an office, you go into a conference room or something similar. To achieve the same effect with Sqwiggle, you simply close the program or browser tab.
Sqwiggle's stated goal is to replicate the ease of determining colocated team members' status/activity when you are not colocated. No one is insisting you run it 24/7, just like no one insists you live your life at your desk at work.
A very strange and dismissive article overall. The paragraph starting with "I don’t think Sqwiggle will be around long though" seemed especially cynical.
However, the distinction is that whatever you are working on RIGHT NOW is not what's all important. You may and should love what you're doing right now, but attaching too much of your identity to your current product/role/company will cause you pain if the product/company fails, or prevent you from taking opportunities elsewhere where you can contribute to your overall goals more than where you currently are.
Does this require action on the part of the original bitcoin owner? Or in this case has the FBI seized all the keys/credentials required to do this themselves?
To reuse a great Mel Brooks line, the girls have an opening they're looking for you to fill, but it's not the interesting kind: at best a Sr Software Engineer at some massive company writing Java on a team that "is just like a small startup in a big company".
We were racing against time and lost. A lot of time was spent transferring ideas between people, and implementing something that wasn't quite right. I can't imagine any startup in the same situation not having at least SOME similar overhead. For a small startup without funding, this can't be optimal.
But this is a problem because you won't get any jobs if you say your skill in the language they use is 3/10. And of course you have to compete against people even less skilled than yourself who rate themselves at 9/10.
Maybe the way to solve this is to take the space used for skills and use it to show off your projects. If you're new to a language, your most interesting project will be something small and simple. But for the languages you're most comfortable in, you will likely have built something awesome.