YoungUpstarts

SEPTEMBER 4, 2014

Reach out to your loyal customers and offer incentives for them to write reviews and rank services. If you run a business than offers higher priceditems, such as equipment vending, instead of requiring a 100% cash payment, leasing allows the customer to obtain the equipment they need for a manageable monthly payment.

Customer 168

Customer PPC Software Review Finance 168

Startup Lessons Learned

DECEMBER 8, 2008

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

APRIL 4, 2010

Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. 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

Startup Lessons Learned

MARCH 25, 2010

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. This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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. The idea is that once we move to the new system (or coding standard, or API, or.) The current code is spaghetti, but the new code will be elegant. Its become "legacy code" and part of the problem.

Software Review 164

Software Review Engineer Management Technical Review 164

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

David Teten

SEPTEMBER 23, 2017

We’ve seen some modest progress in people upgrading from Excel to Google Sheets; use of some CRM; and a cloud-based storage service. Sebastian Soler recently launched Knowledge.vc , which uses software and machine learning to enhance deal sourcing and diligence for VC firms. 5) Due diligence. 4) Manage deal flow.

Private Equity 60

Private Equity Venture Capital Equity Technical Review 60

SoCal CTO

DECEMBER 1, 2010

The United States is now a debtor nation to China and that the bill is about to come due. Equity-Only CTO and Equity-Only Developers - SoCal CTO , November 1, 2010 I had a recent email dialog with the founder of a company looking for a CTO for their startup. These are probably the two sites where I've posted the most reviews.

Technical Review 175

Technical Review Technology Product CTO Hire 175

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

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

Feld Thoughts

NOVEMBER 18, 2013

His most recent company, Filtrbox, participated in the inaugural Techstars class (Techstars Boulder 2007) and was a win for all parties involved; Filtrbox was acquired in 2010 by Jive Software (NASDAQ: JIVE). For the first the months, the team meets often and strategizes on what they want to build while some code gets written.

Burn Rate 152

Burn Rate Equity Software Review Early Stage 152

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 10, 2009

Our code pushes take another six minutes. Since these two steps are pipelined that means at peak we’re pushing a new revision of the code to the website every nine minutes. On average we deploy new code fifty times a day. Code reviews and pairing Great practices. Throwing out a lot of code.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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. The batch size is the unit at which work-products move between stages in a development process. For software, the easiest batch to see is code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

ReadWriteStart

JANUARY 29, 2012

Over Saturday and Sunday teams focus on customer development, validating their ideas and building a minimal viable product. You also get a $50 credit for hosting and cloud computing services per each team, something that came in handy for those teams doing some Big Data implementations. It was a nice mix.

St. Louis 135

St. Louis Kansas City Norway Kansas 135

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. What is customer development? Dates are irrelevant.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

JULY 29, 2009

But there is more to technical debt than just the interest payments that come due. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. In particular, try these three things: Invest in technical debts that may never come due.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

AUGUST 2, 2008

Your natural tendency when an investor says yes will be to relax and go back to writing code. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? When an investor says he wants to invest in you, or an acquirer says they want to buy you, dont believe it till you get the check.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Both Sides of the Table

FEBRUARY 7, 2010

My first company launched in 1999 and we were offering a SaaS document management in the cloud (we were called ASPs back then). We made lots of assertions about what features we thought people would want, how to price them and how to overcome the objections that people have to managing data in the cloud. Another example.

San Diego 267

San Diego Entrepreneur Philadelphia Cloud 267

Startup Lessons Learned

MAY 31, 2010

And a special thanks is due to all of our presenters, panelists, and mentors. When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs. Kent Beck is deservedly famous for his many contributions in the software industry. We all owe him our thanks for persevering.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

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. 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.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

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.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 15, 2008

I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customer development process. To promote this metrics discipline, we would present the full funnel to our board (and advisers) at the end of every development cycle. Check your assumptions, what went wrong?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JUNE 17, 2010

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. And like feedback on a simple microphone sound system, this would occasionally boil over into screeching.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

www.women2.org

MARCH 8, 2012

After quitting my job and starting Sorced , I spent a few months validating my business concept by creating the product mockups and doing customer development. My delusions of coding grandeur quickly subsided and realized that I was not going to hack it. The Alchemist Series: Customer Development and Metrics.

Cofounder 47

Cofounder Technical Review San Francisco Founder 47

Startup Lessons Learned

FEBRUARY 16, 2009

Lets start with a distinction between shipping new software to the customer, and changing the customers experience. The idea is that often you can change the customers experience without shipping them new software at all. Id like to add one extra thought to Joes thought experiment.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

MARCH 3, 2009

At IMVU , these were quite common (after all, were shipping code 50 times a day). They are collected and reviewed after an appropriate interval (e.g. In response to Sean - Intel still runs a very formal process of setting expectations, evaluating employees and reviewing progress on a quarterly basis. love your openness at IMVU.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

MAY 14, 2009

Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. This shift allowed us to crank out working software quickly as a service. It was a disaster.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Rob Go

SEPTEMBER 9, 2013

Lean Startup Circle Boston – Meetup dedicated to the lean startup and customer development methodology. Raizlabs – Mobile Development. Intrepid – Mobile development. Extension Engine - Software engineering and design. Walter Frick - Harvard Business Review. Great for recent grads or career switchers.

Boston 71

Boston Technical Review Community Cofounder 71

Startup Lessons Learned

FEBRUARY 22, 2009

See Paul Grahams Why Nerds are Unpopular to learn more) Take a look at this article on a programming Q&A site: How old are you, and how old were you when you started coding? We also learned that law is code , and that leadership was needed to build thriving communities in a digital age. Can I send you a review copy?

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

JULY 2, 2009

For example, a site outage may seem like it was caused by a bad piece of code, but: why was that code written? The net effect of all this was to make new engineers incredibly productive right away – in most cases, we’d have them deliver code to production on their very first day.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

OCTOBER 5, 2009

Due to an interaction effect between your hardware, solar flares, and quantum flux, this virus will crash your computer and erase your hard drive sometime soon. In the past, we invested in brilliant architecture, code reuse, refactoring, modular design, etc. I have detected a secret virus in your CPU. The curse of prevention Beware!

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

MARCH 27, 2009

I believe it is a full, company-wide turn through the OODA loop (for a software business, see especially Ideas-Code-Learn ). You need a process for systematically reviewing your costs and eliminating those that slow you down. Customer Development Engineering : techniques for accelerating your product development.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

SEPTEMBER 18, 2008

All I see is a name, an icon, a price, the developers name, and a review star-rating. The reviews are all over the map. But even clicking through to see a screenshot and some reviews is incredibly time consuming, given the hundreds of apps in most categories. I cant really tell. Seth Godin: How often should you publish?

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 27, 2010

Over time, such teams either explode due to irreconcilable differences or dramatically slow down. As I found out to my dismay, this is a dangerous game: in many cases, you’re asking trained professionals to violate their own code of best practices, for the good of the company. Any excesses are likely to be moderated by others.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167