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. There are three stages: We start with ideas about what our product could be.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. Please leave feedback!) Do programmers have quiet working conditions?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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. These tests are written by the engineers themselves, and they must all pass every time.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 8, 2008

So one of the first things we did was to hire an Oracle expert and get to work. It felt like software that grownups were supposed to use, and we didnt qualify. Meanwhile, we were building our app in PHP, using a generic DB driver and mysql, "for the time being." I was building a new startup in 1999, and wanted to do it right.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

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.) Heres my favorite part: If youve got a team, part of the team should obsess about the backlist, honing it, editing it and promoting it, while the rest work to generate (as opposed to promote) the frontlist. .&#

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

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. Like gmlk, I usually subscribe the first time I find something useful. Your posts are well-written with a good overview as well as concrete tips. More of the same.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

SEPTEMBER 22, 2008

My favorite instance of this is scheduling software. This has lots of benefits, but one strong one is that it causes everyone to check the status of the build all the time. And even when new tools are needed, my experience has been that you can only figure out what tools you need once you have done the relevant task by hand.

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. SEM on five dollars a day Andrew Chen: Growing renewable audiences Marc Prensky's Weblog: Cell Phones in Class A new version of the Joel Test (draft) Smarticus — 10 things you could be doing to your c. Our instinct is sometimes to do giant big-bang rewrites.

Product Development 68

Product Development Developer San Francisco Product 68