Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software? I dont think so.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Both Sides of the Table

JANUARY 16, 2010

Yet 2010 is already showing me how connected our lives and our health are starting to become. My favorite new software tool is DailyBurn. So as I contemplated the kick off to 2010 I thought again about Weight Watchers. Problem is – Weight Watchers software TOTALLY SUCKS. Seemed such a fantasy back in 1992.

Technical Review 278

Technical Review Software Review Alabama Silicon Valley 278

Steve Blank

DECEMBER 7, 2009

As we were out looking for our Series B round, our company had gotten the attention of “name of big VC firm here” who wanted a play in enterprise software. During the due-diligence process, I sat down with one of the partners who pulled out a set of slides and asked me: ”Have you seen these?” Are These Your Slides?

Silicon Valley 261

Silicon Valley Non-disclosure Agreement NDA Startup 261

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. When a developer wants to check-in code, this is a very scary moment.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Both Sides of the Table

JANUARY 28, 2012

Fred Wilson wrote two posts in 2010 that were very influential with the startup community. But on the other hand if you have a product with a very high gross margin (software, virtual goods, etc.) Try reading a bunch of reviews, checking 5 different restaurants to try and compare the differences. They do both well.

Mobile 334

Mobile Web Software Review San Francisco 334

Startup Lessons Learned

OCTOBER 5, 2008

Each specialist takes up his part of the spec (UI, middleware, backend) and cranks out code. So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan. In exchange, the team agrees to show each piece of working code to the product manager for his approval.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. For software, the easiest batch to see is code. Every time an engineer checks in code, they are batching up a certain amount of work. This is easiest to see in deployment.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Both Sides of the Table

NOVEMBER 25, 2010

I decided to put both of those issues to bed in 2010. Two weeks after winning the deal and well into implementation planning we released a new version of our software. How could a company like ours be so callous as not to support their software (even one more than 4 years out of date)? we would support 6.0 which was in beta).

China 333

China Silicon Valley Software Review Technical Review 333

View from Seed

JULY 31, 2014

In the past 18 months at NextView, we’ve made 13 new investments (out of the 36 we’ve made since the inception of the firm back in 2010). This is hardly a unique investment category, but that’s because the shift in how software is purchased and delivered has been so fundamentally transforming. Recent Investment Overview.

Seed Stage 272

Seed Stage B2C Technical Review Disintermediation 272

Startup Lessons Learned

MARCH 25, 2010

Lessons Learned by Eric Ries Thursday, March 25, 2010 Speed up or slow down? for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. In the early days, chaos stayed under control.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Both Sides of the Table

NOVEMBER 25, 2010

I decided to put both of those issues to bed in 2010. Two weeks after winning the deal and well into implementation planning we released a new version of our software. How could a company like ours be so callous as not to support their software (even one more than 4 years out of date)? we would support 6.0 which was in beta).

China 328

China Silicon Valley Software Review Technical Review 328

Both Sides of the Table

MARCH 5, 2010

This was in large part due to the marketing efforts of Jason that created a great top end of the funnel (100+ companies applied) and the herculean efforts of Tyler Crowley who spent days going through all of the submissions and serving up 5 very interesting companies. The second event was in Boulder.

San Francisco 254

San Francisco Technical Review Los Angeles Software Review 254

Both Sides of the Table

APRIL 5, 2010

He came to the United States in 2001 to study Software Engineering at Auburn University. While he was waiting for the paperwork to be reviewed he moved to Boulder, Colorado and took a job with a local tech company there. We then moved our Chief Software Architect over. I hope that didn’t have a stature of limitation!

Technical Review 282

Technical Review Canada Green South Carolina 282

Startup Lessons Learned

APRIL 4, 2010

Lessons Learned by Eric Ries Sunday, April 4, 2010 Kent Beck keynote, "To Agility, and Beyond" Kent Beck will give the opening keynote at the Startup Lessons Learned conference on April 23. Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Both Sides of the Table

MAY 23, 2012

Looking ahead at the next decade I am excited by what I believe will be viewed as one of the best and most rational investment periods for venture capital due to seven discrete factors: 1. If you want to understand the details of why this is, I covered it in detail in this post, Understanding Changes in the Software Industry.

Venture Capital 347

Venture Capital Technical Review LP Mobile 347

deal architect

APRIL 15, 2012

It was early in 2010. An SAP employee reviewed an early draft and encouraged me to reach out. I was finishing up research for The New Polymath. I had a generous page in the manuscript on Hasso Plattner’s in-memory vision.

Software Review 267

Software Review Employee Software 267

Startup Lessons Learned

JULY 29, 2009

But there is more to technical debt than just the interest payments that come due. In particular, try these three things: Invest in technical debts that may never come due. Yet there is one silver lining when it does happen: we wind up throwing out working code , debt-riddled and elegantly designed alike.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Both Sides of the Table

APRIL 2, 2010

Unfortunately over the period of 2000-2010 the VC industry hasn’t performed well and therefore the number of funds going forward is likely to reduce greatly. Some wait 5-7 years but usually this is because it’s proving more difficult to raise a new fund due to market conditions or the lack of returns in their current fund.

Venture Capital 269

Venture Capital Balance Sheet Early Stage Software Review 269

VC Cafe

JULY 5, 2010

The workshop participants, of which there were about 30, brought diverse experience and expertise to the table – from young entrepreneurs with just a few years of experience in the consumer web, to seasoned executives with decades of experience in semiconductors, telecommunications and enterprise software.

Software Review 116

Software Review Technical Review Community Due Diligence 116

Steve Blank

SEPTEMBER 14, 2009

For instance, I’ve been warned when being introduced by other entrepreneurs not to trust certain older VCs due to their disposition towards using young startups to do their friends favors, prove a point, gain some insight, etc. My experience of 2001-2004 is very remote from what you are describing.

Silicon Valley 237

Silicon Valley IPO Technical Review Venture Capital 237

Both Sides of the Table

OCTOBER 10, 2010

It has long been believed that people from lower-income neighborhoods can’t learn as well as middle & upper class ones due to environment issues such as problems at home and trouble in the neighborhood. So what is the problem and proposed solutions from the film maker? This hugely resonated with me. How is that American?

Technical Review 340

Technical Review America Software Review Sacramento 340

Steve Blank

MARCH 19, 2009

And since the card was useless without any application software, what other software products did they use on it? What reviews did they trust? They said the product reviews in these publications were by far the biggest influence on which card to buy. (This made our PR problem manageable and focused. Which ones?

Silicon Valley 213

Silicon Valley RSS Software Review Technical Review 213

Startup Lessons Learned

AUGUST 3, 2009

My experience is in Enterprise Software - where we are forced to chunk features into formal releases. While it is still possible - and recommended to experiment with customers in order to determine the minimum that they need, the exercise is bit more complicated due to the formality of the release process. Bring your questions.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

ReadWriteStart

MAY 22, 2012

When Bob Herman founded Tropolis Group in 2010, he decided to finance with credit cards so he could take advantage of a cash-back rewards program and use the bounty to buy supplies for the business. So far, Herman has put about $60,000 on his credit cards, using them mostly to finance software development.

Technical Review 118

Technical Review Software Review Angel Investor Startup 118

Entrepreneurs-Journey.com by Yaro Starak

SEPTEMBER 28, 2010

Read on and let me help you decide… My Money Comes From My Email List The majority of people who will read this blog post will come from my email newsletter because I sent a message about this review. I haven’t received any negative feedback since I upgraded the software, so that is a good sign.

Software Review 93

Software Review Development Team Review Technical Review Email 93

Startup Lessons Learned

DECEMBER 7, 2008

When I want to know about some concurrency issues between services in his cluster, he doesnt blink an eye when I suggest we get the source code and take a look. Hes just as comfortable writing code as racking servers, debugging windows drivers, or devising new interview questions. He throws off volumes of code, and it works.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

The Next Web

JANUARY 27, 2013

It’s been slightly over two years since I attended Startup Weekend in September 2010, which literally changed my world for the better. Now, two years later, it is a good time to share some important lessons that I learned after taking the Red Pill that day in September 2010. They told me it was impossible to pick up coding.

Netherlands 159

Netherlands Technical Review Software Review Cofounder 159

ConversionXL

JULY 22, 2021

Much like you periodically review your digital marketing campaigns to get the most from them, a technical SEO audit evaluates site performance to identify areas for improvement. . All pages on your website are assigned an HTTP status code. Each code relates to a different function. 4xx status codes. 5xx status codes.

Technical Review 162

Technical Review SEO Software Review XML 162

Software By Rob

OCTOBER 14, 2010

And after talking about this subject at length, I found myself again evangelizing it last week at the Business of Software conference. And these days with how easy it is to build an application, your code isn’t worth much, either. Ideas (and in many cases the code itself) are not worth as much as we think.

Software Review 77

Software Review Marketing Technical Review Software 77

Both Sides of the Table

DECEMBER 5, 2010

Yes, social networks of 2010 have much better usability, have better developed 3rd-party platforms and many more people are connected. Was it massively better software, better companies, better markets? I know in 2010 this doesn’t seem obvious to everybody but it’s my judgment. then bought GeoCities for $3.6

Social Network 318

Social Network Networking Internet Technical Review 318

Both Sides of the Table

JUNE 17, 2013

In my first enterprise software company we developed a methodology for sales that we called PUCCKA. Take for example the years 2010-2012 where every brand out there seemed to be buying Facebook “Likes.” This article initially appeared on Inc. Click here. This post is about the “P” or pain.

Sales 367

Sales Software Review Social Media Customer 367

crowdSPRING Blog

JUNE 9, 2010

Book Review: Delivering Happiness by @Zappos CEO Tony Hsieh – [link]. Book Review: Delivering Happiness by @Zappos CEO Tony Hsieh – [link]. Book Review: Delivering Happiness by @Zappos CEO Tony Hsieh – [link]. Modern Element Trends In Minimal Webdesign of 2010 – [link]. – [link].

Social Media 93

Social Media Small Business Design Software Review 93

The Startup Magazine

JANUARY 8, 2019

When he was 21, he came to America to further his education and quickly earned two Masters of Science degrees – the first in Computer Science and the second in Software Engineering. The software generates instant dynamic reports, such as financial revenue, gender ratio, and more. Looking to Solve Problems. Success and Sustainability.

Technical Review 137

Technical Review CTO Hire Silicon Valley Software Engineering 137

ReadWriteStart

DECEMBER 19, 2010

If you are looking for some books on entrepreneurship to read, or even to gift, here are some recommended books from 2010. There were a number of great business books published this year, many of which we reviewed here as part of ReadWriteWeb's " Weekend Reading " series. You can read our review here.

Software Review 155

Software Review Technical Review Cofounder Startup 155

Startup Lessons Learned

JUNE 17, 2010

Lessons Learned by Eric Ries Thursday, June 17, 2010 No departments Big companies have departments. I was the junior guy on a project team; I was called in to do some technical due diligence for reasons that were obscure to me, because the team already had much more senior engineers assigned to it. Startups are companies.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

MAY 7, 2009

Getting features and fixes into hands of users was the greatest priority - a test environment would just get in the way and slow down the validation coming from having code running in production. When a new engineer started at IMVU, I had a simple rule: they had to ship code to production on their first day. Heres the key point.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.

Software Review 87

Software Review Design Software San Francisco 87