Startup Lessons Learned

JANUARY 18, 2010

Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment. Eric Of all the Lean Startup techniques, Continuous Deployment is by far the most controversial.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

NOVEMBER 7, 2008

And if you do get a handful of people taking you up on the offer, youll be able to send them a nice personal apology. And if you do get a handful of people taking you up on the offer, youll be able to send them a nice personal apology. If youre worried about disappointing some potential customers - dont be. We finally settled on a $1.99

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 14, 2008

Lessons Learned by Eric Ries Sunday, September 14, 2008 How to listen to customers, and not just the loud people Frequency is more important than talking to the "right" customers, especially early on. Youll know when the person youre talking to is not a potential customer - they just wont understand what youre saying. that we learned different.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Hearpreneur

OCTOBER 1, 2016

No matter if the business is a Goliath like Wal-Mart, or a local business owned by a couple or family, the business has roots in an idea. For each business owner, the story of their journey can range from monetary needs or the passion for a unique project. Each story is different though the reasons may remain the same. 1 – A Personal Project.

Entrepreneur 48

Entrepreneur Non-Compete LLC Social Media 48

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Yet, especially in times like these, it’s easy to rail against the badness of being in debt; it’s a very human feeling. Remember Hamlet?

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 10, 2008

Joel is focused on the fact that in many environments, programmers are considered "just the hired help" akin to manual labor, and not treated properly. I have been thinking a lot about what a new version of this test would look like, given what Ive seen work and not work in startups. This is still an essential practice, especially on the web.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

MAY 14, 2009

Through case studies, exercises, and discussions, Eric Ries will guide entrepreneurs of all stripes through the key areas that determine success for startups: product, engineering, QA, marketing, and business strategy. I have a lot of good news to report on this front. You can register for both dates on the new official signup page.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

A Smart Bear: Startups and Marketing for Geeks

OCTOBER 4, 2017

By which they mean: Without stupid rules that assume employees are dumb or evil, without everything taking ten times longer than it should, without wall-to-wall meetings, without resorting to hiring anything less than the top 1% of the talent pool, and so on. Small companies operate this way by necessity, and it works!

Government 223

Government Startup Cofounder Technical Support 223

rob.by

MARCH 8, 2012

If a software geek really wants to try building something for no pay, they’re going to work for themself instead of following another cashless entrepreneur. He argued that software engineers don’t finish what they start, and that you’re better off paying a technical person than partnering with one. There’s execution.

Technical Cofounder 42

Technical Cofounder Cofounder Software Engineering Fractional CTO 42

Startup Lessons Learned

OCTOBER 20, 2008

If engineers want more time to spend making their old code more pretty, they are invited to do so on the weekends. Its tempting to blame the business leaders ("MBA-types") for this mess. And in a mess this big, there is certainly blame to go around. But they are pushing for the things that matter to customers - features.

Software Review 164

Software Review Engineer Management Technical Review 164

SoCal CTO

DECEMBER 1, 2010

How to Take Down Facebook -- Hint: It Ain't Twitter. (aka: aka: An Open Letter to the Next Big Social Network) - 500 Hats , November 1, 2010 I've held off writing this post for a long time, because I couldn't quite get my head around all the issues. but: Something is Still Missing. Ralph Waldo Emerson. One out of ten of Americans are out of work.

Technical Review 175

Technical Review Technology Product CTO Hire 175

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. On the one hand, it gives you insight into what kind of employee the candidate might be. The six key attributes spell ABCDEF: Agility.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

AUGUST 8, 2009

At each half-day meeting, wed work as a group on a specific lean startup technique. In between sessions, this cohort of companies would have the opportunity to act as a learning community, sharing what theyve learned and supporting one another as they try to put the techniques into practice. August 9, 2009 10:28 AM Chris said.

Lean 102

Lean Programming San Francisco Continuous Deployment 102

Startup Lessons Learned

FEBRUARY 22, 2010

As entrepreneurs, more than any other industry, we’re in the meritocracy business. There’s been a lot of hand-wringing about gender equity in the high-tech and entrepreneurship worlds lately. Or, maybe it is true that women make better entrepreneurs than men. This is a good thing. (I

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you. This is not for the faint of heart.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

JANUARY 11, 2009

The unexplored value of CPI ads is this: social networking apps give you the opportunity to practice advanced marketing techniques like true one-to-one marketing or permission marketing. The difference is intent: when youre searching for a specific topic, ads have a chance to fulfill your interest in that topic. In other words, not very much.

San Francisco 68

San Francisco Social Network Lean Continuous Deployment 68

Startup Lessons Learned

FEBRUARY 10, 2009

I can personally attest that these guys know what they are talking about; I saw them do it first-hand. It’s also not a new technique here, we’ve been practicing continuous deployment for years; far longer than I’ve been a member of this startup. I will always be full of awe and gratitude for what they accomplished.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. Yet it’s helpful to begin by tackling a specific class of problems. Always explicitly identify the person running the meeting.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

MAY 1, 2009

Lessons Learned by Eric Ries Friday, May 1, 2009 Lean Startup webcast post-game Wow, what an incredible turnout for webcast this morning, right on the heels of a phenomenal crowd at startup2startup last night. Its been a great twelve hours for the lean startup! In a future post, Ill attempt to unpack this definition in detail. What a thrill.

Lean 60

Lean San Francisco Startup Continuous Deployment 60

Startup Lessons Learned

NOVEMBER 13, 2008

Yet there is one specific technique that I learned most clearly from this book: asking why five times. Instead, we can use the technique of asking why five times to get to the root cause of the problem. After reading it, you might not even realize that there are cars involved in Toyotas business. why did that code get written?

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

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! (As always, this is a fictionalized account; Im blending several people Ive known into a single composite. And please forgive the fact that I use male pronouns to describe the archetype. But life is not easy, either.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

MARCH 27, 2009

Lessons Learned by Eric Ries Friday, March 27, 2009 Cash is not king Cash on hand is just one important variable in a startup’s life, but it’s not necessarily the most important. What matters most is the number of iterations the company has left. While some cost-cutting measures reduce that number, others increase it.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

DECEMBER 8, 2008

Continuous integration is a technique for reducing those piles of code. First, a word about why continuous integration is so important. Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. The more code, the bigger the pile. Step 1: get a continuous integration server.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

infochachkie.com

DECEMBER 5, 2011

Hands-on startup advice for emerging entrepreneurs. Lousy Products Might Break Your Bones – But A Name Will Seldom Hurt You John Greathouse – Posted in: Entrepreneur , Strategic Planning. Successful entrepreneurs have a bias toward action, as illustrated in Tom and Huck. infoChachkie. Thanks for visiting!

Naming 40

Naming Technical Review Product Product Name 40

Startup Lessons Learned

JANUARY 4, 2009

Most components in a modern data center are completely stateless, meaning they just do batches of work that is handed to them, but dont store any data long-term. Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

DECEMBER 16, 2008

Facebook , LinkedIn , and other successful social networks have elevated this technique to a high art. Photos, on the other hand, is probably the primary reason I go to Facebook every day. Our goal is to understand the metrics, mechanics, and levers of engagement. Levers of engagement Lets start with the levers of engagement.

Viral 140

Viral San Francisco Lean Continuous Deployment 140

blog.expensify.com

APRIL 24, 2012

Update: The end is near, Expensify is hiring a.NET programmer! As you might know, we’re hiring the best programmers in the world. Expensify Blog. Expense Reports That Don't Suck. CEO Friday: Why we don’t hire.NET programmers. Learn more… Saturday edit: Wow, quite a response to this. Sunday edit : Still going!

Java 107

Java PHP Software Review Coder 107

Startup Lessons Learned

MARCH 20, 2009

I think the OReilly audience is particularly important, as so many entrepreneurs got their start in technology (as I did) from their worn-down copy of Programming Perl. What concepts, techniques, or stories do you think will resonate? They started out as digital cash for PDAs, but evolved into online payments for eBay.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

NOVEMBER 5, 2008

Act Each morning, volunteers would arrive and be handed packets with instructions. Lessons Learned by Eric Ries Wednesday, November 5, 2008 Learning from Obama: maneuver warfare on the campaign trail I had the privilege of volunteering for the Obama campaign in swing states for a few weekends during the final push towards victory.

Campaign 84

Campaign San Francisco Lean Agile 84