Startup Lessons Learned

SEPTEMBER 18, 2008

Chances also increase if there seems to be a Ruby bent to the content. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Thats just me, though. Im sort of surprised you have no comments.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

APRIL 9, 2009

No engineering team. But where it makes sense, that team may also include engineers building new experiments or prototypes to try with customers. And instead of design, engineering, QA, and operations we have a solution team implementing a startup-centric version of agile development. You need a problem team and a solution team."

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

JANUARY 12, 2009

At IMVU, when wed hire a new engineer, we could get them to ship code to production on their first day, even if they had never programmed in PHP before. Good article, this is exactly the reason Im still primarily a PHP developer rather than Ruby or Python. In most cases, simple changes are simple to make. 49comments: Joel Hughes said.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

FEBRUARY 12, 2009

If the company is looking for programmers, you convince them they absolutely need Ruby programmers. Now, theres nobody with 10 years experience in doing ETL QVC in Ruby, so now your 3 years is starting to look pretty good. Case Study: Continuous deployment makes releases n. Remember Java? Expo (and a call for he.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89