I do lots of small commits as save checkpoints and new branches for each point of exploration. Rebase/reset to create clean commits. Each final commit is a complete thought.
My favorite article on the life cycle (growth & collapse) of online communities is “Attacked from Within”* from the old kuro5hin site. I’ve always been curious to how it’s suggested solutions to the moderation problem would turn out.
The wayback machine* has Zachary Amsden's opinion in 2007 why the vmkernel (and other components) are not in violation of GPL. It's an interesting read.
He concludes:
> 1) There is no argument that depending on a Linux console OS makes any part of ESX subject to GPL that is not already opene sourced. We have open sourced those GPL components of the system which we have modified and given the changes back to the community.
> 2) There is no argument that loading the vmkernel by bootstrapping it with Linux makes the vmkernel subject to GPL. In fact, in the funniest counter-example, Linux itself used to be boostrapped under MS-DOS by running the command loadlin (note the 7 character name, since DOS would not allow enough characters for load-linux).
> 3) There is no argument that distributing GPL binary drivers makes any piece of software distributed with them or using them subject to GPL. In fact the converse appears to be explicitly stated in the GPL itself.
> This case is specifically regarding a combined work that VMware allegedly created by combining their own code (“vmkernel”) with portions of Linux's code, which was licensed only under GPLv2. As such, this, to our knowledge, marks the first time an enforcement case is exclusively focused on this type of legal question relating to GPL. However, there are so many different ways to make combined and/or derivative works that are covered by GPL that no single case could possibly include all such issues.
I also find it unlikely it's just the name and license number. They used to return all of a driver's information (name, phone, address, drivers license, license plate, etc) from the rest endpoint they were using on their website. They closed that hole it after it we disclosed it to them.
I think most new "netbooks" have been converted into 11.6 form factor to include a proper full sized keyboard. The only real reason netbooks had 10" displays was because intel required it when purchasing an atom (along with their 2gb memory limit). Atoms haven't gotten any real architectural (IPC) changes since their release and Intel has been repositioning the brand/hardware towards tablet/phone devices. Since manufacturers have been freed from the 10" constraint, such most manufacturers have been building larger screened low end laptops which is really what the market wants. As such you might want to reconsider your options. Depending on the architecture of the Celeron, it may actually be faster and more battery efficient than an Atom. The options seem to be:
1/ Deal with an extra inch of real estate
2/ Buy a 7/10" tablet & add a keyboard. Some like the Asus transformer pad includes a keyboard dock. You can also try rooting/chrooting a linux distro onto the tablet all the bells and whistles.
My company uses lastpass to share passwords. Any passwords that is saved to the 'shared accounts' folder is automatically shared to everyone on the team.
Their funds are finite and the increased cost of a football would take away funds for other goods and services which they deliver. They need to prioritize their the current needs and demands, not just optimize for the long term cost of a football.
You should take a look at http://vcs-home.branchable.com/ They have a mailing list and a bunch of resources to do similar things.
Right now I use movein[1] to maintain my dot files. Each dotfile is held in it's own repo which is checked out to $HOME via GIT_DIR and GIT_WORK_TREE environment variables. The mr[2] command ties the git repos together as it if was one repo. I use additional repos or branches to handle variations within dotfiles. For work, I try to keep things confined to the relevent directory eg. using local.vimrc[3]
I do pretty much the same thing but using simplenote. Simplenote has a lot of clients including one for vim and emacs so it's pretty easy to find one on the platform of your choice.
This is precisely why they use reverse a linked list- it's common enough that everyone understands it, and if not, it can be quickly explained, and everyone understands that you 'just need to flip' the arrows, yet we get many people who don't get it.
For what it's worth I don't really care much about your resume other than the fact that it is a signal for if you _may_ be a good hire. My job as an interviewer is to test if you are a good hire and you need to be able to pass that test. I ask easy programmings questions as a smoke test of technical competence. I banter about your interests and past achievements to see if we are able to communicate and get along (as well as probe for bullshit). I ask hard problems to see how you think and your motivation to get the job done.
Having been in a big company, the primary reason we did lots of coding is to ensure that we have enough signal that you can code. One bombed interview may not mean much, but any more may be an indication that you cannot get the job done without some amount of babysitting.