VirtualBox does have a headless mode, which is how I use it. Combine it with phpVirtualBox for a web-based front-end and you can admin from anywhere or any system.
Autostart, autosave, auto-snapshot, etc can be achieved with simple startup and cron scripts.
It's such a big company it's in plural.
As much as I loved Joshua Malina, Rob Lowe was fantastic as Sam Seaborn.
This was probably due to Sorkin and Schlamme checking out for season 5 though. Malina could have had better dialog if Sorkin had written any of it...
The issue as I'm sure you know isn't "opened", but rather "opened within a certain length of time." Obviously given unlimited time you can get into anything, and you probably can get into an ATM a lot faster than a decent safe. But once you have the explosion routine down pat, you can probably be away with the ATM money in *seconds*. In terms of practicality and low risk, that's hard to beat.
Well, we have a ways to go before we lead the world in government corruption, but we're world class when it comes to petty political venality.
One dude took my whole set of code and rewrote it.
Ah...that guy. Every office has that guy. I hate that guy.
Seriously though, my mother just had similar done for tremors, these "brain pacemaker" procedures are actually pretty routine now.
You can have/use this idea for free:
Before a system will build said code, have the build system verify the code not only by the public key/code hash, but as a secondary method - the code fingerprint of the author in question.
This turns a creepy idea into something worthwhile.
I have yet to meet a really competent programmer. I don't consider myself much beyond capable - but I have too many flaws in my output to be considered really brilliant.
I have worked with or dealt with the output of other programmers who's performance was egregious - most egregious was the contractor who's naive use of a commercial java framework managed to produce the effect of a memory leak in java (e.g. hamstrung java's built-in garbage collection mechanism).
Experience has taught me practical measures of quality programmers in no particular order:
1. They must know how to program at the most simple level (e.g. competency in structured programming in C would be a good starting point - a basic understanding of LISP programming a plus) before tackling more complex programming tasks. I get the sense there are a lot of cut-and-paste programmers out there who really don't understand what the underlying code they are creating is actually doing.
2. Have an innate ability to focus on simple solutions, rather than being clever. KISS principle must be understood and brought into every design decision from the start. That is not to say there are no complexities, but understanding what is simple given the problem at hand - some simple things are complex when compared to other systems - and having the ability to avoid needless complexity.
3. Literate - must be able to not only communicate effectively externally - but also their comments in code should illuminate the subject matter in a clear, concise manner. Ideally should be able to get workable technical documentation straight from their comments - via doxygen or the like (perldoc, pydoc etc).
4. Their code must be maintainable and extendable. If an average programmer cannot maintain the code, and is required to rewrite the system from scratch - then you have failed as a quality programmer. Change is inevitable - how resilient your system is to change is a measure of your ability as a programmer.
5. They must understand a lot about technology outside of the world of their application. Their application will live in a world of networks, machines (physical and virtual), storage systems, communication protocols, and APIs - they must understand the implications of software design choices given a set of environmental requirements. The best programmers not only know how to code up systems, but also how to give advice about what their systems will be capable of doing given the environment, or lack thereof - and act upon that if it is possible to adjust via changes to software alone (e.g. choosing multithreading/multiprogramming design over single thread of execution).
6. They must be able to create secure code. If the company they work for doesn't produce a guide to that, then they should develop that on their own - and live by it - and consistently improve it. If they are using frameworks/libraries written by someone else, they should audit or test it to be sure the underlying implementation is secure.
7. Must be able to get along with others and work as part of a team; ideally if they are really a quality programmer, I would expect them to also mentor and share their ideals and capabilities with their peers to bring everyone up as much as possible. Quality programmers are not primadonnas.
That's it from my standpoint.
I never really thought about them being any different. I always thought of them as being the same.
It looks like Suzuki and Honda have both ATVs and UTVs. I found on another site the major difference is the seating arrangement (side-by-side for UTV). The UTV can have seatbelts, and have motorcycle type controls rather than golfcart/car type controls.
I've always thought about it by engine and general style. Well, I learned something today.
What I said before about seeing them still applies. When I lived in a rural area, I saw people riding ATVs on the road, but they would also get pulled over if a cop saw them. I got pulled over a few times riding a street/trail bike, even though it had all the required equipment, license plate, and I had (and have) a motorcycle endorsement. Because of the gearing, it had lots of torque, but maxed out at 60mph.
It looks like they plan to do the cooler thing, the printed body on a performance rolling chassis. It'll probably be looking at them again in a few years.
I sure hope his hack is free/open-source.