View from Seed
NOVEMBER 6, 2014
Below, he answers questions about developing products from scratch, as well as the difficult technology choices and tradeoffs CTOs must make. NextView Ventures: You just experienced something that most developers don’t ever see: zero code base at a company. For example, we picked Clojure for our development work.
Both Sides of the Table
APRIL 20, 2010
They’ll have a view on whether Ruby on Rails is worth the hassle. Some CTO’s swear that it is a huge improvement in development timeframes and doesn’t cause performance issues. Others think you should never build anything highly scalable on Ruby. They often aren’t great at planning development work.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Spencer Fry
FEBRUARY 12, 2013
I've listed them in the order in which I read them over the course of my development. Learn Ruby the Hard Way by Zed Shaw 4/5. Learn Ruby the Hard Way is what I started with when I began programming. Agile Web Development with Rails by DHH 3.5/5. It's a step-by-step approach on building a Ruby on Rails application.
TechEmpower
FEBRUARY 13, 2013
As software developers, we're technophiles, so we enjoy these cycles and quite often find humor listening to the energy spent arguing on either side of issues. Not to downplay developer happiness. The web development continuum has sound, safe, but stodgy on one side and shiny-obsession at the risk of unknown stability on the other.
Hearpreneur
SEPTEMBER 22, 2021
Tesla has always put a huge emphasis on product development and technological advancement. 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. Thanks to Christina Giaquinto, Modular Closets !
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. What do you think?
www.bothsidesofthetable.com
MAY 13, 2012
They’ll have a view on whether Ruby on Rails is worth the hassle. Some CTO’s swear that it is a huge improvement in development timeframes and doesn’t cause performance issues. Others think you should never build anything highly scalable on Ruby. They often aren’t great at planning development work.
Expert insights. Personalized for you.
334 
Let's personalize your content