11,979 karma · joined June 18, 2008
Personal blog at alexandros.balena.io
I am also @alexandrosm on twitter.
Contact me at alexandros@balena.io, I'm friendly!
On the second point, Gattaca is a fictional tale, and as such should not be used as evidence to "show" anything. It is, at best, a hypothesis, and one not optimised for accuracy, or subjected to any scrutiny at that. http://lesswrong.com/lw/k9/the_logical_fallacy_of_generaliza...
we do abstract networking control as resin is dependent on the network to keep operating, but the application can take control (and responsibility) of networking if needed.
It may help if you think of your car as just another server. Any connection between the server and client can be encrypted of course, using well-known tools. Besides that, the car can be made to not accept updates that are not signed by the manufacturer, so your only exposure is to the manufacturer.
Of course someone may have physical access to your car and be able to write new software locally, but then they may also be able to do mechanical sabotage, so it's not a new risk.
So you basically have to trade off one kind of security (the manufacturer can update my car remotely) with another (security bug announced in the software my car runs, I am now a sitting duck).
It definitely takes a shift in perspective, but in the brave new world where cars (and other things) run millions of lines of code, over-the-air updates are a necessity. (but of course I'd say that).
I've written a bit more about this conundrum here - https://resin.io/blog/you-cant-secure-what-you-cannot-update...
Diffs and other improvements that affect bandwidth requirements should be complete in the next two months, before we announce pricing. Our agent requires standard web ports, so a firewall that allows web browsing should allow a device to connect. We are funded by a well-known Silicon Valley VC, this will be announced in a few weeks.
Pricing isn't finalised yet (will be announced in 2 months) but drop me an email at alexandros@resin.io and I'd love to let you know our current thinking.
Seen as a meta-experiment it is incredibly weak, with a tiny, biased sample. High-profile results that have a simple enough procedure so they can be combined.
As such, it can't get even close to support what they're (whoever -they- actually is, it may not be the actual researchers) trying to claim. What about less high-profile stuff? What about more complex setups? If 20% of your most rock-solid results are not reproducible, I wouldn't be so quick to celebrate. Imagine if 20% of basic physics or maths results weren't actually true...
As a side-point, I am often shocked that we don't see more research into how to make software teams more productive coming out of places like Google/Facebook/Microsoft etc, given that these companies (claim to) live and die by the effectiveness of their engineering. If a large amount of their expenditure is in software, to the point they'll buy entire companies just for the engineers, why aren't they financing the large-scale experiments that will settle certain questions for good?
What other parts would you like to see?
Whether this is what most other people mean with the terms you just used, is another point entirely.
I'm on the record as having several severe criticisms of EY/MIRI, but being neoreactionaries is not one of them.
Big guys can afford the transaction costs of preferential treatment, small guys have to get by like everyone else. In both cases the provider is a government-backed monopoly. You can port the net neutrality arguments to this issue with a simple term substitution. All I am saying that if someone is 'for' net neutrality, it's hard to be 'against' tax neutrality.
Having said that, in a world where these deals happen, Tesla is right to extract the best deal they can, regardless of what would be the global optimum.
What would you suggest as a scientific idea ready for retirement?
Location
--------
Remote, or on-site in Athens, Greece
About us
--------
We are building a seamless code delivery platform for embedded devices (like the Raspberry Pi). Think of it as Heroku for the Internet of Things if you must. We've already ported Docker to ARM CPUs and have hit quite a few more Linux, Docker & ARM related milestones internally. We are a company founded and led by developers and have a strong engineering-led culture. As long as there is progress, we are flexible with regard to location and work hours.
About you
---------
We are looking for Linux talent to work on our cloud services, deployed as Docker containers, but also to work on supporting arbitrary Linux-capable devices. The product is still young so you'll get a chance to have real impact on how the end result looks and feels to our users. Besides strong Linux skills, familiarity with Docker will help a lot. Much of our codebase (on cloud and device) is in node.js so JavaScript skill is a plus.
The Process
-----------
Send us your CV (a pointer to source code online is a great plus). Those that pass a phone interview will receive a small but paid project as a test. If we like working with you and you like working with us, you'll be offered a full-time job.
Get in touch
------------
send your CV to hello@resin.io