Startup Lessons Learned

SEPTEMBER 15, 2008

This gets me into trouble, because it conjures up for some the idea that product development is simply a rote mechanical exercise of linear optimization. You just constantly test little micro-changes and follow a hill-climbing algorithm to build your product. They just ask "which hypothesis should I show?"

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 6, 2008

I know some of those compilers are no longer available (some are hosted, others are not), so I took the liberty of putting up a copy of the PHP Greasemonkey Compiler. Thoughts on scientific product development Lo, my 5 subscribers, who are you? As I make more, youll find them (with source) at my Greasemonkey Compiler page.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

NOVEMBER 29, 2008

Lessons Learned by Eric Ries Saturday, November 29, 2008 The ABCDEFs of conducting a technical interview I am incredibly proud of the people I have hired over the course of my career. This second objective plays no small part in allowing you to hire the best. Hiring decisions are among the most difficult, and the most critical.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

JANUARY 1, 2009

I think it may have something to do with your tendency to focus on concrete experiences you have been through with IMVU, especially those concerning customer relations and hiring. I cant say exactly why, but it has managed to stand out from the crowd. Regardless, keep on with what you have been doing. eric: briefly, you rock dude.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JANUARY 6, 2009

Why vanity metrics are dangerous ► November (1) ► October (7) ► September (9) ► August (8) ► July (8) ► June (7) ► May (8) ► April (5) ► March (11) ► February (10) ▼ January (10) Achieving a failure Refactoring yourself out of business Three freemium strategies Lean hiring tips Why PHP (..)

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JANUARY 27, 2009

Why vanity metrics are dangerous ► November (1) ► October (7) ► September (9) ► August (8) ► July (8) ► June (7) ► May (8) ► April (5) ► March (11) ► February (10) ▼ January (10) Achieving a failure Refactoring yourself out of business Three freemium strategies Lean hiring tips Why PHP (..)

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

Startup Lessons Learned

JANUARY 11, 2009

Why vanity metrics are dangerous ► November (1) ► October (7) ► September (9) ► August (8) ► July (8) ► June (7) ► May (8) ► April (5) ► March (11) ► February (10) ▼ January (10) Achieving a failure Refactoring yourself out of business Three freemium strategies Lean hiring tips Why PHP (..)

San Francisco 68

San Francisco Social Network Lean Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 9, 2009

Or, for something more substantive, how about the top five-most-read posts: Why PHP won Dont launch Five Whys Work in small batches The engineering managers lament But wait, theres more! Read the very first comment (thanks tfitz!) or relive my very first subscriber survey - when there were a grand total of five. First OODA reference: Ideas.

San Francisco 84

San Francisco Continuous Deployment Lean DC 84

adam.heroku.com

MAY 18, 2012

Everyone has to be a generalist and able to work on any kind of problem - specialists will be (at best) somewhat bored and (at worst) highly distracting because they want to steer product development into whatever realm they specialize in. Stage 2: The first hires. Don’t do that stuff.

Developer 92

Developer Database Architecture API 92

Startup Lessons Learned

MAY 7, 2009

As the product matured, they were able to ratchet up the quality to prevent regression on features that had been truly embraced by their customers. Second, leveraging a dynamic scripting language (like PHP) for building web applications made it easy to quickly set up a simple, non-disruptive deployment process.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

www.quora.com

JANUARY 16, 2011

Sure, it garners the "winning " reply above, but in reality I find the answers below by Cody Riddar that directs the asker to go hire an inexpensive prototype development team much more helpful than the "leading answer" that gives the "Quora rockstar engineer" point of view. I'll give you a 50% here.

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42

www.kalzumeus.com

FEBRUARY 6, 2013

We need whomever is responsible for product development and/or ops to, effectively, carry a pager for drop-everything-and-do-it-now resolution of security issues, just like we’d do for e.g. the server has fallen over or “our building is, physically, on fire.” Hacker for Hire, Hire a Hacker, Hack Facebook -.

Security 101

Security Software Review Ruby Startup 101

Startup Lessons Learned

NOVEMBER 13, 2008

Most of this code was from a variety of open source PHP projects that were glued together with the shortest path to goal possible. 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." We had closer to several hundreds of thousands of lines of code.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JANUARY 12, 2009

Lessons Learned by Eric Ries Monday, January 12, 2009 Why PHP won When I first learned to program on the web, Perl + CGI was the dominant platform. But by the time I was building my first websites for commercial use , PHP had taken over. Writing unit tests or mock objects in PHP is an exercise in constant frustration.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

JANUARY 4, 2009

Why vanity metrics are dangerous ► November (1) ► October (7) ► September (9) ► August (8) ► July (8) ► June (7) ► May (8) ► April (5) ► March (11) ► February (10) ▼ January (10) Achieving a failure Refactoring yourself out of business Three freemium strategies Lean hiring tips Why PHP (..)

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

JANUARY 30, 2009

Hire the absolute best and the brightest, true experts in their fields, who in turn can hire the smartest people possible to staff their departments. By hiring experts, conducting lots of focus groups, and executing to a detailed plan, the company became deluded that it knew what customers wanted. We can skip the chasm.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 28, 2009

Because, unless you are working in an extremely static environment, your product development team is learning and getting better all the time. Most importantly, I encouraged the leaders of the company to bring awareness of the business challenges to the product development team. Great post, Eric.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

steveblank.com

JULY 8, 2011

interactions, widgets, effects Django – high-level Python framework Cappuccino – open source framework for app development Kodingen – cloud development environment, code editor, hosting service, collaboration platform. Simple editing. Reply Jarek , on February 27, 2011 at 11:51 pm said: What about CRM?

Software Review 110

Software Review Startup Silicon Valley Analytics 110

www.vccafe.com

MARCH 11, 2013

PHP-FPM (a patch for php4/5 to greatly improve FastCGI SAPI usage). pgbouncer (Lightweight connection pooler for PostgreSQL, from the developers of Skype). cakePHP (PHP). Drupal (PHP). Kohana (PHP). Zend Framework (PHP). WordPress (PHP). Aptana Cloud (svn, IDE, php, java, rails etc…).

Software Review 53

Software Review Technical Review Startup 53