Agile Continuous Deployment Document Software Review 
Startup Lessons Learned
JUNE 15, 2009
Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months.
Startup Lessons Learned
NOVEMBER 6, 2008
Lessons Learned by Eric Ries Thursday, November 6, 2008 Steveys Blog Rants: Good Agile, Bad Agile I thought Id share an interesting post from someone with a decidedly anti-agile point of view. Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 20, 2008
If engineers want more time to spend making their old code more pretty, they are invited to do so on the weekends. The idea is that once we move to the new system (or coding standard, or API, or.) The current code is spaghetti, but the new code will be elegant. Its become "legacy code" and part of the problem.
Startup Lessons Learned
AUGUST 8, 2009
Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. We owe a lot to this seminal document. The same might be said of good software. But what about Commodity?
Startup Lessons Learned
MAY 31, 2010
And a special thanks is due to all of our presenters, panelists, and mentors. Kent Beck is deservedly famous for his many contributions in the software industry. Unfortunately, the video of our sllconf conversation is not online (due to technical problems), but we have a physical tape backup which we are endeavoring to get online soon.
Startup Lessons Learned
JUNE 17, 2010
But according to the theory, this should have been covered by the various specs and documentation we were rigorous about producing. I was the junior guy on a project team; I was called in to do some technical due diligence for reasons that were obscure to me, because the team already had much more senior engineers assigned to it.
Startup Lessons Learned
FEBRUARY 22, 2009
See Paul Grahams Why Nerds are Unpopular to learn more) Take a look at this article on a programming Q&A site: How old are you, and how old were you when you started coding? We also learned that law is code , and that leadership was needed to build thriving communities in a digital age. only two kids took it up!
Expert insights. Personalized for you.
167 
Let's personalize your content