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. are the parts of the Joel Test I think are most out-of-date. Youd better.

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 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." Certainly no faster than the time it takes to release. How long does the software sit un-deployed? Software is generally always getting better or getting worse. .

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

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. Its enourmously helpful when you need to generate new ideas about what to do, or when you face a product problem you dont know how to solve. Expo SF (May. Take a look and let me know what you think.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

DECEMBER 7, 2008

And we cant hire new engineers any faster, because you cant be interviewing and debugging and fixing all at the same time! Even with the highest standards imaginable, theres no way to hire just genius hackers. Hire a CTO or VP Engineering. Worst of all, your teammates are constantly wanting to have meetings.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

SEPTEMBER 22, 2008

We had all the tools in place but we didn’t actually practice agile development. No fancy tools needed here — it’s about the mentality, attention to detail, and the actions that foster agile development, not the tools & systems you set up in place to facilitate this. Expo SF (May.

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. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Our instinct is sometimes to do giant big-bang rewrites.

Product Development 68

Product Development Developer San Francisco Product 68

Both Sides of the Table

JULY 5, 2010

In the era of Skype, web conferencing tools and collaboration software conventional wisdom says that distributed startup teams can be just as effective as those that are in person. The conversations bleed into the sales messages the next time, they wend their way into software designs and form the plan of attach against competition.

Distribution 335

Distribution Offshore CTO Hire Bulgaria 335

Startup Lessons Learned

JANUARY 12, 2009

But by the time I was building my first websites for commercial use , PHP had taken over. 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. Its one of the most effective paradigms for software devlopment in history.

PHP 166

PHP Software Review Ruby San Francisco 166