370 karma · joined May 10, 2010
Will they know what's going on under the hood though?
Taking somebody from ground zero and teaching them enough to be able to debug problems that the hires would need to know in order to be proficient, self starting engineers.. I'm really skeptical about that being done in 8 weeks.
Most of the little tricks and crap I've learned over the years have been through trial and error, and working on many different projects.
More specific examples: for loops not creating scope in javascript and asynchronous calls introducing race conditions due to not understanding them. Those aren't things that are in curriculums, though when trying to build some features most people will encounter them.
I'm not sure if these postgres servers are. However one interesting note is that the "maximum database size" of the heroku server is 2TB, while RDS is 1TB.
If you're familiar with some of the heavy hitting problems in computer science right now, such as vertically scalable architecture, garbage collection, how difficult it is to debug multithreaded applications, you might want to check out Node.JS, as it is my #1 bet for large adoption of engineers in the near future. It's the first project of it's kind, in the age of GitHub, that can really be called a trending software platform. It allows you to do very rapid iteration of development, without having the hassle of how to handle large amounts of IO and other problems that will make you bang your head against your desk with if you were using other systems.
Above all though, the most interesting projects for you to work are probably what you would learn the most from.
I want push notifications for replies, though :). Premium feature? Could make something to poll myself but I'm cool with spending a few monies for it.
Where I work, everybody has linux development machines, but use their machine of choice as their actual workstation. This either forces people to use vim/emacs through SSH, or set up some local file sharing so that they can use their bloated eclipse thing.
Personally, I've spent months each with a few of the popular editors around, and I fall back on vim just because my .vimrc has been tuned so much over the past few years that it's just painful to use anything else. I don't even care if the editors have more features.
Now, if I had a fancier terminal, where my mouse click picked the right vim split view instance, or highlighting text in a split view vim selected only text in that window, instead of the whole line of the terminal, I would use that. MacVim is pretty much the perfect tool for me, but it's local and not remote (and also not inside a terminal that I can split up with screen).
He did specifically say "was not designed" for these kind of applications, but that doesn't mean the application layer can't take care of it. In fact I would argue that with Node, you have the possibility of having greater control over your clustering and failover logic.
Writing CSRF-safe logout would mean that you can't have an href to a static link, and you'd to implement some sort of unique id/key and/or a form post behind the scenes.