3 ms·
I worked as a Rails developer at ThoughtWorks for three years, from 2008 to 2011, on three different projects, including the one they called "the largest Rails
by davidrupp 9y ago
I worked as a Rails developer at ThoughtWorks for three years, from 2008 to 2011, on three different projects, including the one they called "the largest Rails project in the world" at the time. [1] I didn't see any of the toxic behavior Zed recounts. Rather, I got to work with some of the best developers -- and smartest people -- I've ever met, and had a lot of fun while leveling up my career.
[1] https://conferences.oreilly.com/rails2009/public/schedule/detail/8706 https://conferences.oreilly.com/rails2009/public/schedule/de...
- davidrupp 9y agoI wrote a blog post about it at the time. [1] Wouldn't change a word of it today. [1] http://davidrupp.blogspot.ie/2010/01/why-should-you-want-to-work-for.html http://davidrupp.blogspot.ie/2010/01/why-should-you-want-to-...
- jarsin 9y agoI got fired for being a "Rails trouble maker" in late 2009. Never saw your blog back then but if I did I would have applied.
- JamesBarney 9y agoI will be incredibly impressed with Apax if they are able keep this type of culture thriving.
- Analemma_ 9y agoNice to hear it. Certainly other parts of Zed's rant didn't really stand up to close scrutiny, so I figured I'd ask someone who was really there.