Cofounder Continuous Deployment Early Stage Engineer 
Startup Lessons Learned
AUGUST 26, 2009
The companies I spoke to all agreed that the community there was extremely supportive, especially in the critical ulta-early-stage. Then, create an encouraging environment for early-stage companies. Provide early seed capital, and be the ones to make those introductions. And do your customer development.
Startup Lessons Learned
SEPTEMBER 14, 2008
Later, when the company was much larger, we had everyone on our engineering team agree to sit in on one usability test every month. It wasnt a huge time commitment, but it meant that every engineer was getting regular contact with an actual customer, which was invaluable. Case Study: Continuous deployment makes releases n.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
APRIL 14, 2009
In an early-stage startup especially, revenue is not an important goal in and of itself. Let’s start with a simple question: why do early-stage startups want revenue? It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality.
Startup Lessons Learned
NOVEMBER 17, 2008
Another advantage of the early stages is that most dont have to juggle too many competing priorities. Some companies and founders refuse to serve existing customers, and are always lurching from one great idea to the next. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
JULY 30, 2009
A discounted price is available for early stage entrepreneurs and students. Building on this, I’ve recently become fascinated with the notion of continuous deployment , a concept that has been popularized by Eric Ries and others. Case Study: Continuous deployment makes releases n. Read the rest.
Startup Lessons Learned
JUNE 9, 2009
benjaminjoffe : early adopters of buggy product are visionary customers, sometimes smarter than founders! Many founders dont like to hear that visionary customers are as smart, maybe even more so, than they are. Yet its one of those features thats only ever requested by investors and engineers - never by customers.
Startup Lessons Learned
AUGUST 8, 2009
I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. Great engineers see it and smile. This is called set-based concurrent engineering (SBCE). [1]
Expert insights. Personalized for you.
113 
Let's personalize your content