352 karma · joined July 21, 2011
Sometimes vendors will informally buy locations from other vendors.
I think it is an interesting question but a bad one most of the time unless you take into account all the other external factors that don't include the language it self.
https://github.com/tmm1/test-queue
One thing that really sped up our test suite was by creating an NGINX proxy that served up all the static files instead of making rails do it. This saved us about 10 minutes off our 30 minute tests.
This is a demo from youtube. Looks even more shaky than the default camera app.
Race Against the Machine,
by Erik Brynjolfsson, Andrew McAfee
http://www.amazon.com/Race-Against-The-Machine-Accelerating-...
It has some ideas on how to get from where we are to there. I think the philosophies of Race Against the Machine and Capital in the 21st century are pretty insightful and the truth may be somewhere in between the two.
We had to add a few patches to get features we wanted such as graceful shutdown and fix up the way the CLI api worked.
Chef was tested, but the way the tests were implemented were done extremely poorly. When testing a class they stubbed their own internal classes. Basically what ended up happening was none of the interaction between the methods were being tested. I was amazed that this class worked at all. This happend quite a bit too. I understand that what chef is trying to do is very difficult but maybe the problem is that they are trying to do too much.
I don't want my ops tool doing everything, I only want it to setup my servers and make sure that they are all the same.
Groupon has a pretty good internal solution that they are trying to open source soon. They released the client a few days ago. Now if only they had some documentation and the server.
But don't use chef... seriously... It is poorly tested, and lets you do way too many stupid things. Same with puppet.
Check out salt stack
I have found that tips for traveling are all over the internet so I have none to give really. The advice you heard me tell you now is told by many others in travel blogs. http://reddit.com/r/travel
Right now I am in South America, I am using couchsurfing.com and using hostels. I have an apartment right now which cut down costs a lot but still hang out with the local couchsurfing community. I cook nearly all the time so food is pretty cheap. I am lucky that I can program and work remotely but I have friends who do data entry work, translation, english tutoring. I have friends who volunteer in hostels for free room and board or use http://www.helpx.net/
As for traveling, mostly by bus, or budget airlines(which are as expensive as buses). And I do not move often.
Hanging out with couchsurfers has really kept my daily COL. I personally hate most tourist traps and by hanging out with couchsurfers usually you get amazing local cultural experiences for either free or cheap. IE My host in Venezuela took me to his girlfriend's niece's baptism party where I sang, drank, and danced with 70 year old venezuelan women.
I find I am happiest not going on a guided eco tour, or going to the top of some tall thing(building or mountain), but sharing thoughts and experiences with different/local people.
All the things that I own at this point in time fall into at least one of these three categories.
1. Help me reach goals or aspirations (computer, camera)
2. Make my life simpler and safer (Water bottle, Telephone, multi-tool, clothes, accessories)
3. Provide or improve an experience (kindle, speakers/headphones)
The one thing these three categories share is function. Everything you own should have function and it should be consistently used/appreciated.
Here is to a life, instead of bought, lived.
I have been playing around with it and it simplifies a lot of the things that bother me about erlang. It breaks some functional conventions for code readability such as rewriting the same variable
I like to think of knowledge as a resource with compound interest for the individual and especially for the company. Knowledge is built on what you already know and the more you learn the more ideas and knowledge you can generate. Teaching another is the key principle of pairing. If done correctly somebody should always be learning and teaching.
Here is a gist of the code in ruby if anybody wants to steal it. I stole it from somewhere else and thus you have the history of programming.