1–10 of 76 posts
My short history of Engine Yard and my Resignation
brainspl.at
You might as well just link to the blog entry directly: http://brainspl.at/articles/2010/08/13/4-years-at-engine-yar...
[edit] looks like I cannot change the url myself. if a moderator can change irt I'd appreciate it.
I found it surprising that Rails needs this level of hand-holding to keep it running though. Rails devs, is this really the experience you have deploying your applications?
I think I'd prefer to pay less for hosting, and have some experts on retainer for when they're really needed.
They're cool people in any case, and I wish them good luck.
I'm interested in education, hiring, and matters of accreditation. Those last few paragraphs really got my attention. I'm glad I read all the way to the end.
"Oh the stories I could tell if only I could. But I feel that telling this positive story of the history of EY is the classy way to go out and I wish Engine Yard all the best in the world"
Any unrest?
Well written. I had never heard of the author or his company, yet unlike so many of the articles that come through here, it had enough context baked in that you could follow it without a Google search. I found it surprising that Rails needs this level of hand-holding to keep it running though. Rails devs, is this really the experience you have deploying your applications?
There are easy options for simple apps. As things get complicated, there are managed hosting options that are hyper-specialized to Rails, such as EngineYard.
There was a time when administering a Rails app was a much more hairy proposition than it is today, though.
Is there anything in this "Oh the stories I could tell if only I could. But I feel that telling this positive story of the history of EY is the classy way to go out and I wish Engine Yard all the best in the world" Any unrest?
This is a really hard problem IMHO. Obviously it depends on your business model, but I've found it at times an unsolvable problem...