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

DECEMBER 7, 2008

Its common to find a hacker at the heart of almost any successful technology company. 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. He throws off volumes of code, and it works. All is not lost, though.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Transformify

MARCH 14, 2020

These days, due to coronavirus outbreak, many businesses have asked their employees to work from home. At the same time, the stock markets collapsed, and most businesses already report skyrocketing losses, unmet revenue targets and insufficient stock due to production slow down in China, India and the rest of the world.

Hiring 98

Hiring Bulgaria Italy Spain 98

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

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. As a technical fix, it was brilliant. I remember one such meeting vividly. So they react in two ways.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

AUGUST 2, 2008

Lessons Learned by Eric Ries Saturday, August 2, 2008 Paul Graham on fundraising I have found no better primer on the current realities of starting a new technology company in a startup hub like Silicon Valley than Paul Grahams essays. Your natural tendency when an investor says yes will be to relax and go back to writing code.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

YoungUpstarts

DECEMBER 26, 2013

Gigs vary in categories like advertising, video and animation, graphics and design, programming and tech, music and audio, gifts, fun and bizarre, online marketing or writing and translation. There is even a special instructions autoreply when someone rents, allowing them to access any garage pin codes or directions to access gated spaces.

Securities and Exchange Commission 263

Securities and Exchange Commission San Francisco Miami United Kingdom 263

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

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. Three concepts I found particularly helpful: Process = discipline.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

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

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. Although many of the non-technical folks in the room didnt understand what was happening in the moment, plenty of hackers were on high alert. We all owe you.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

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

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. Robert August 25, 2009 5:25 AM Bernard said.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JULY 2, 2009

That’s because Five Whys will often pierce the illusion of separate departments and discover the human problems that lurk beneath the surface of supposedly technical problems. But if we stay stuck at the technical parts of the problem, and never uncover the human problems behind them, we’re not going far enough.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

JANUARY 12, 2009

Since then, PHP (as part of the LAMP stack ) has really been the dominant development platform, at least in the free software and startup worlds. When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. Every change required a server restart.

PHP 166

PHP Software Review Ruby San Francisco 166

crowdSPRING Blog

JULY 7, 2010

Legal Contracts for Software Developers Who Hate Contracts (w/free contract template to use today) – [link]. Today Finland officially becomes first nation to make broadband a legal right – [link]. Inspiration: Asian Style Tattoos – [link]. 65 Unique And Innovative Website Footer Designs For Inspiration – [link].

Social Media 96

Social Media Small Business Design Media 96

crowdSPRING Blog

JULY 7, 2010

Legal Contracts for Software Developers Who Hate Contracts (w/free contract template to use today) – [link]. Today Finland officially becomes first nation to make broadband a legal right – [link]. Inspiration: Asian Style Tattoos – [link]. 65 Unique And Innovative Website Footer Designs For Inspiration – [link].

Social Media 96

Social Media Small Business Design Media 96

Startup Lessons Learned

JUNE 24, 2020

His main scientific goal, whether it's addressing cancer, SARS-CoV-2, or something else, is "to bridge this gap between all the new really exciting technologies that I could see emerging and the actual practical applications of treating patients." I grew up in Finland. In addition, the transcript of our conversation is below.

Founder 60

Founder Technical Review Leadership Software Review 60

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

JANUARY 30, 2009

Build a world-class technology platform, with patent-pending algorithms and the ability to scale to millions of simultaneous users. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. Ship it when its done, not a moment before. We can skip the chasm. Fail faster.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

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. Its this second point I want to emphasize.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

AUGUST 24, 2009

The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. But the same technologies that make life difficult for traditional marketers also offer them unprecedented new opportunities.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

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. Its design goals arent geared towards efficiency in terms of technical costs.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

ConversionXL

AUGUST 23, 2017

While some weren’t able to share the entire process due to privacy issues, they did share a specific section in the process… 1. Finland-based Leadfeeder is a top (Google) analytics tool that shows the companies that visit your website. Let’s get inspired by these companies’ successful customer journey map examples. Leadfeeder.

Customer 130

Customer Channel Design Retention 130

Startup Lessons Learned

SEPTEMBER 18, 2008

From a technical point of view, its amazing. 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.

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. I joined a financial services tech startup in 1999. May 14, 2009 5:23 AM David said.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

pandodaily.com

NOVEMBER 29, 2012

“The tech industry creates roughly 10 awesome companies per year,” he says. “Founders don’t think their problems are due to trends. She has been covering technology news for over 15 years, most recently as a senior editor for TechCrunch. Scanadu: Technologically-savvy healthcare. Open Sesame! (A

Technical Review 93

Technical Review Silicon Valley Incubator Syria 93

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

AUGUST 26, 2009

Im also excited to share two long-form reviews from actual attendees. Technically you argue it goes back 30 years when StorageTek was founded. More recently it's skewed to software & web. Revisiting the Software Design Manifesto (and what. There used to be a ton of storage startups here.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

SEPTEMBER 11, 2009

In fact, I am convinced that if you could find some of IMVU’s earliest adopters, they would say something like this: “sure, those guys at IMVU HQ were helpful in writing code and stuff, but in the end they were just the hired help. peer review is NOT working. It was really the community who built that product.&#

Community 158

Community Management Lean Software Review 158