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

YoungUpstarts

APRIL 29, 2020

However, there’s a big challenge that faces most employers who are unfamiliar with the remote work setup: what software tools do your staff need in order to stay in the game and run your day to day operations with minimal business impact? Fully edit any element in a PDF file, including main content (images, text, links, etc.)

Software Review 194

Software Review Software Employee Cloud 194

Startup Lessons Learned

AUGUST 30, 2008

Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# This basic pattern is useful in all aspects of product development. The basic idea is to avoid building something based on what you think it might need to do in the future.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

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

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

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. But there is more to technical debt than just the interest payments that come due. The failure of the feature had nothing to do with the quality of the code.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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. Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did).

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

YoungUpstarts

DECEMBER 6, 2011

Cloud solutions come in three key different flavors, being IaaS (Infrastructure as a Service), PaaS (Platform as a Service), and Saas (Software as a Service). With cloud, it is less necessary to own your IT infrastructure, much less your own software. Services can be deployed from the cloud as and when it is needed, like a utility.

Cloud 223

Cloud Asia Government Mobile 223

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

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. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. My experience is in Enterprise Software - where we are forced to chunk features into formal releases. Revisiting the Software Design Manifesto (and what. Thank you. I know it's going to help me immensely!

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

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

Startup Lessons Learned

AUGUST 2, 2008

Your natural tendency when an investor says yes will be to relax and go back to writing code. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Expo SF (May.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

ReadWriteStart

DECEMBER 8, 2023

Major companies, such as Unity, have also started developing tools and software for developers to build robust and innovative applications within this space. Adapting to emerging trends and staying agile will be crucial for startups as the metaverse grows. The potential for the metaverse is vast and varied.

Technical Review 133

Technical Review Generative AI Startup Agile 133

ConversionXL

NOVEMBER 10, 2020

We might have medium-term goals like “adopting agile methodologies” or “getting everyone on the same page with a project kick-off” as the outcomes for the reader. For example, the Jira Software team created a microsite dedicated to product-agnostic education about becoming an agile team. Distribution framework.

Agile 139

Agile Social Media Audience Software Review 139

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. In other words, a principled way to combine agility with stability.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 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. 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

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

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

SEPTEMBER 15, 2008

Code To make split-testing pervasive, it has to be incredibly easy. The only change you have to get used to as you start to code in this style, is to wrap your changes in a simple one-line condition. Now, it may be that these code examples have scared off our non-technical friends. October 4, 2008 10:33 AM Amitt Mahajan said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

MAY 31, 2010

And a special thanks is due to all of our presenters, panelists, and mentors. Kent Beck is deservedly famous for his many contributions in the software industry. Unfortunately, the video of our sllconf conversation is not online (due to technical problems), but we have a physical tape backup which we are endeavoring to get online soon.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

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

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

AUGUST 26, 2009

If you watch the video/audio below, youll get to see some of the questions I was asked after my presentation. I did my best to capture video and audio; a YouTube playlist and Slideshare slidecast are below: Slides (with audio): 2009 08 19 The Lean Startup TechStars Edition View more presentations from Eric Ries.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

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

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 5, 2010

When I wrote a review of Four Steps on this blog in November, 2008, I did my best to be candid and warn of a few shortcomings: And Steve is the first to admit that its a "turgid" read, without a great deal of narrative flow. Four Steps primarily centers its stories and case studies on B2B hardware and software startups. Expo SF (May.

Customer Development 166

Customer Development Developer San Francisco Customer 166

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. Combining agile development with customer developm. What counts as an iteration? Expo SF (May.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

AUGUST 24, 2009

When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. For example, the best book reviewers only review books published by the best publishers, which only accept manuscripts from the best agents. And how could they possibly review a blog? Is that a lot? Is that good?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Board Effect

SEPTEMBER 22, 2023

These boards are more agile and can make decisions quickly when necessary. Board management software assists small boards by helping to automate workflows and administrative tasks such as sending out meeting reminders or posting meeting minutes. However, the smaller size means each member has more responsibility and accountability.

Technical Review 52

Technical Review Technology Software Review Security 52

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. But that doesnt make it any less important to answer.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

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. Expo SF (May.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

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. We changed our model to B2B and adopted Agile around 2002. May 15, 2009 5:59 PM Eric said.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

NZ Entrepreneur

MARCH 11, 2020

It’s about becoming more agile. Today’s software and CRM systems give incredible visibility and sales insights to business owners who want to make data-driven decisions, based on accurate knowledge of what their customers really want. 2) Business Authenticity. Life as we know it is constantly changing. 5) Outbound Sales.

Social Media 64

Social Media Channel Technical Review Sales 64

Startup Lessons Learned

DECEMBER 14, 2009

For a consumer internet company in particular, this is often due to a lack of design thinking. In an entrepreneurial situation, this is hard, because artifacts that we are creating (products, code, marketing campaigns, even revenue) are of secondary importance. They get focused solely on growth. They get focused solely on growth.

Customer 156

Customer San Francisco Viral Lean 156

Duct Tape Marketing

DECEMBER 29, 2021

Click on over and give us a review on iTunes, please! But now you go on, you look at Google reviews and they talk about rusty, the technician that came to their house and did an amazing job. So in looking at those reviews and that's the best social listening that a brand can do by the way is, uh, that's the best consumer insight.

Technical Review 100

Technical Review Software Review Networking Cofounder 100