352 karma · joined December 19, 2010
There are tens more languages that are more modern and "aspirational"
http://lwn.net/Articles/392307/
Seems like either the quality wasnt there or the linux people where resistant to change.
Some more info here. http://en.wikipedia.org/wiki/User:AzulPM/Managed_Runtime_Ini...
Its a pitty that this type of GC hasn't found widespread use because it gives us the best of both worlds, in terms of automatics memory management and performance.
edit for spelling mistake
Here is one for $9 http://www.ebay.com/itm/1430mAh-Internal-Replacement-3-7V-Li...
As a side note I also dont think there is anything stopping a London black cab driver from signing up for Uber.
1. Stay focussed. 2. Keep your team as small as possible.
TDD is not designed to be a good technique for developing algorithm's but rather for designing OO systems and discovering the collaborations between various objects within a system. This doesn't mean you can forget about solid OO design principals and just somehow land up with a good design just because you use TDD.
All in all its a great introduction to the service, really well put together.
One things I would do is make the permalink visible as soon in the flow as possible.
edit
Could potentially be used a a form of ddos mitigation if the browser was required to design a tiny bit of hash cash for each request, although I haven't really thought through all the details.
Step 1) Send the candidate a small unattended coding test they can do in a couple of hours. If they pass great if they dont offer them feedback.
Step 2) Invite them in for a pair programming test this should take max one hour, they can spend 15-30 minutes with one or two people on the team solving a problem.
You wouldn't believe the amount of people who have amazing looking CV's but when it comes to actually coding they just are not up to scratch.
There is also obviously personality fit and other subtleties but thats the basics.