View from Seed
NOVEMBER 6, 2014
You always want to be careful with how tightly you schedule things to make sure you stay agile and responsive to evolving business needs, but you also need to make sure your overall journey makes sense and that you’re building things in the right order, as well as taking on risks in a measured way.
Both Sides of the Table
APRIL 20, 2010
They’ll have a view on whether Ruby on Rails is worth the hassle. Others think you should never build anything highly scalable on Ruby. They know how to estimate work units, how to manage the agile development process and how to get the most out of their teams. I’ve heard both arguments from CTO’s.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Spencer Fry
FEBRUARY 12, 2013
Learn Ruby the Hard Way by Zed Shaw 4/5. Learn Ruby the Hard Way is what I started with when I began programming. Ruby on Rails was my goal, but my friends urged me to start with at least a basic understanding of Ruby before venturing down the Ruby on Rails path. Agile Web Development with Rails by DHH 3.5/5.
TechEmpower
FEBRUARY 13, 2013
Besides, more development time means the client can be more agile with functionality and has a greater potential for success. Allow me to be brutally clear: the more our clients' budgets go to Amazon or Rackspace, the less budget goes to continued development time. Development time is how we earn money. Playing it safe.
Feld Thoughts
OCTOBER 30, 2013
Though the notion of a “lean startup” that uses both Agile and Customer Development approaches is ostensibly strongly customer focused, the purpose of these methodologies is for the company to find an maximize its market, not specifically to optimize the user experience. I think he totally nails it. What do you think?
Hearpreneur
SEPTEMBER 22, 2021
They invented Ruby on Rails, were one of the earliest proponents of remote work, and took customer service to new heights. For me, it's a live example of agile and sustainable business. Basecamp is a business that I respect much for what they've accomplished and who they've become. Photo Credit: Jeremy Goldman.
www.bothsidesofthetable.com
MAY 13, 2012
They’ll have a view on whether Ruby on Rails is worth the hassle. Others think you should never build anything highly scalable on Ruby. They know how to estimate work units, how to manage the agile development process and how to get the most out of their teams. I’ve heard both arguments from CTO’s.
Expert insights. Personalized for you.
334 
Let's personalize your content