Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If not, whos going to insist we switch to free and open source software? Case Study: Continuous deployment makes releases n. But along the way, something strange happened. I dont think so.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 On deployment My favorite question to ask a software development team is "how do you do a release." You can tell a lot about a company from their deployment flow. I havent met anyone who would do a day-long deployment every day. How fast do they iterate?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. Were a software company, so what we do everyday is turn ideas into code. Case Study: Continuous deployment makes releases n.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

NOVEMBER 4, 2008

It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Agile software development. Agile allows companies to build higher quality software faster.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

APRIL 26, 2009

We combined three tactics: extensive use of free software, an open platform for user-generated content, and leveraged distribution channels. The net result was powerful: within six months of starting the company, we were able to get a basic version of our product into open beta.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

SEPTEMBER 8, 2008

It felt like software that grownups were supposed to use, and we didnt qualify. It cost us a few hundred thousand dollars to get our app up and running, but none of that was dollars spent on software licenses or professional services. Case Study: Continuous deployment makes releases n. It wouldnt boot. yeah, its awesome.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

SEPTEMBER 1, 2008

Lessons Learned by Eric Ries Monday, September 1, 2008 Test-Driven Development as andon cord You cannot control what you cannot see, and the hardest part of managing software projects is that the final product is so intangible. In almost all Agile Development systems, thousands of automated tests are run against every change to the software.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

MAY 27, 2009

It uses principles of agile software development, open source and web 2.0, Continuously discover what customers want to buy before building or making follow-on investments in new features. Ship new software at a dizzying pace: multiple times a day while improving quality and lowering costs.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 10, 2008

His post is ostensibly about how often to release new work (whether youre a blog writer, movie star, software team.) I’ve been in the software industry for a long time. Case Study: Continuous deployment makes releases n. But Seth Godin is a great writer, so I dont see why I cant crib from him whenever.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

JULY 29, 2009

Leverage product development with open source and third parties. For example, early on at IMVU, we incorporated in tons of open source projects. Let's consider cases: Can you have a piece of software with good product design and bad technical design? Case Study: Continuous deployment makes releases n.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

The Next Web

AUGUST 6, 2013

The engineering philosophy behind it makes total sense – move fast, build quickly, automate testing, validate your decisions through data, leverage open source when you can, build MVPs and get as close to continuous deployment as you can. Can it work for an enterprise software company?

Lean 132

Lean Startup Continuous Deployment Open Source 132

The Equity Kicker

OCTOBER 2, 2014

They were coming out of Alfresco where they’d built a custom solution to monitor their infrastructure as they’d moved from an on premise software company to a cloud play. A strong team, an attractive market and a good dose of momentum are the key ingredients for a seed stage software investment and Dataloop has those in spades.

Cofounder 95

Cofounder Continuous Deployment Seed Stage Cloud 95

Startup Lessons Learned

SEPTEMBER 18, 2008

For example, we used to be baffled at IMVU by the significant minority of people who would download the software but never chat with anyone. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. But Im going to share it anyway, because it feels like the right thing to do.

Software Review 68

Software Review Software Hiring San Francisco 68

www.subelsky.com

FEBRUARY 25, 2010

His descriptions of lean startup techniques and philosophies have had a big influence on the way I design and build software. Because it has an RSS feed, one could also use "Unresolved Hoptoad Errors" as a metric influencing the continuous deployment system. This keeps us from having to hit our database too much.

Lean 41

Lean Baltimore Ruby Maryland 41

Startup Lessons Learned

OCTOBER 16, 2013

We work in prototypically four-week iterations, with quality engineers and software developers working in close collaboration. Software development is all about managing complexity and the bigger and more mature the codebase gets, the more complex it gets. It wasn’t always this way. So what was going on?

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

OCTOBER 11, 2010

(I am often asked to explain how to apply Lean Startup approaches to domains beyond software. On the extreme opposite end are rapid iteration businesses like software or fashion. Thus, more and more industries are starting to look like the software business. In order to answer, I have taken to drawing a two-axis diagram.

Continuous Deployment 164

Continuous Deployment Technical Cofounder Cofounder San Francisco 164

Startup Lessons Learned

NOVEMBER 13, 2008

Best of luck, Your Software." (OK, When Eric writes, "By the time we started doing continuous integration, we had tens of thousands of lines of code, all not under test coverage." Most of this code was from a variety of open source PHP projects that were glued together with the shortest path to goal possible. Good stuff.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 8, 2009

In Computer Science research, it is often better to open source an innovation than to go through the process of protecting it and then licensing it to a new startup. Thirdly, revamp how intellectual property rights are applied to software and code. So should copyrights and patents on software code.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

SEPTEMBER 22, 2008

My favorite instance of this is scheduling software. Accurate - if youve ever been managed by task-tracking software, youll relate to the feeling that you either have to spend ludicrous amounts of time posting updates or the information goes stale. Case Study: Continuous deployment makes releases n.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 22, 2008

For example, trying to make server software more scalable. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Our instinct is sometimes to do giant big-bang rewrites.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

JANUARY 4, 2009

Incremental and proportional software complexity. We can take advantage of the many open source libraries out there that dont scale especially well, and write as much non-scalable code as we want. Case Study: Continuous deployment makes releases n. and more ► January (6) Lo, my 18891 subscribers, who are you?

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

JANUARY 12, 2009

Since then, PHP (as part of the LAMP stack ) has really been the dominant development platform, at least in the free software and startup worlds. When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. As always, Paul is right.

PHP 166

PHP Software Review Ruby San Francisco 166