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 argument itself got me thinking a lot about design and its role in building products.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Platform selection and technical design - if your business strategy is to create a low-burn, highly iterative lean startup, youd better be using foundational tools that make that easy rather than hard.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

YoungUpstarts

MARCH 31, 2014

100 Tokyo is a website that showcases hot products, events, people and places in Japan’s largest metropolis, covering subjects such as design, fashion, art, food, technology, architecture, tourist attractions, accommodation, events and more. Ideaspotting 100 Tokyo Tokyo website'

Japan 162

Japan Singapore Architecture Social Media 162

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

OCTOBER 5, 2009

It’s important to invest in good architecture so that your website will scale once customers arrive. If you make that investment, and then customers arrive, and the site stays up, most companies will reward the people who built the architecture and, thus, prevented the scaling problems. Why do they harbor that paranoia?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. So far, this is just a summary of what all of us who have attempted to build web-scale architectures considers obvious. But startups rarely have either luxury. Easy to understand.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

JANUARY 30, 2009

Insist on high levels of usability, UI design, and polish. Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. Take a look and let me know what you think.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Hearpreneur

JANUARY 24, 2018

Starting my own architecture and interior design firm, Spacesmith, has given me the ultimate creative freedom to come up with an idea, envision an outcome, and then figure out how to make it happen. It is ‘the love of my life’. Thanks to Dr. Mirela Mitan, MMXV Infinitude ! #3- 3- Freedom to meet, learn and be creative.

Entrepreneur 95

Entrepreneur PPC Green Japan 95

YoungUpstarts

SEPTEMBER 20, 2012

That’s right, there are no cubicles or private offices for senior staff – you can imagine how a senior executive transplanted from an Asian office culture (say from Japan’s Sony or South Korea’s Samsung) breaking down in an apoplectic fit when they first find out they’d be sitting next to a low-level code monkey.

Singapore 234

Singapore Non-disclosure Agreement South Korea Indonesia 234

Startup Lessons Learned

JUNE 17, 2010

The artists on the team had called in the big guns, and VP-level folks were there to explain the importance of certain aspects of the visual design that threatened to be cut. I was invited to a feature decision meeting, where the team was closing in on a detailed spec. The meeting was tense. The engineering team wasn’t happy either.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

OCTOBER 20, 2008

Most of the other processs changes - mandatory design reviews (prelimninary, critical, etc), - documenting all our procedures, and so on - were to support those two factors. It might be more precise to categorize them of two kinds of flaws: flaws in implementation, and flaws in design. Eric, Is this post about Architecture?

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

JULY 13, 2009

Reinertsen weaves together ideas from lean manufacturing, maneuver warfare, queuing theory, and even the architecture of computer operating systems and the Internet. Product development deals in designs, which are fundamentally intangible. Team New Zealand designed the yacht that won the Americas Cup.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

DECEMBER 7, 2008

I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. When the architecture needs modifying - why do we need a meeting? Building a good application architecture is not just coding. Its common to find a hacker at the heart of almost any successful technology company.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

crowdSPRING Blog

AUGUST 2, 2017

Unique, simple and smart – these have been core elements in great graphic design for many decades. In fact, like other cultural norms, design often follows trends. When it comes to design, especially for business, trends and fads can be confusing. The same should be said about logo design. This is not unusual.

Architecture 63

Architecture Design Japan Boston 63

Startup Lessons Learned

SEPTEMBER 7, 2008

We talk about taking advantages of the incredible agility offered by modern web architecture for extremely rapid deployment, etc. As usual, Im heavy on the theory and not on the specifics, so I thought Id share some additional thoughts that came up in the course of the classroom discussion. Take a look and let me know what you think.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

SEPTEMBER 8, 2008

You dont need to invent a new architecture, and you dont need to even build your architecture up-front. Were in a new wave of platform evolution. Now you can build an app at true web scale without incurring any software costs, or any fixed hardware costs. 1 comments: flixsterwidgettest said. yeah, its awesome.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

crowdSPRING Blog

AUGUST 2, 2017

Unique, simple and smart – these have been core elements in great graphic design for many decades. In fact, like other cultural norms, design often follows trends. When it comes to design, especially for business, trends and fads can be confusing. The same should be said about logo design. This is not unusual.

Architecture 48

Architecture Design Japan Boston 48

Startup Lessons Learned

NOVEMBER 13, 2008

It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. Wish I could figure out how to apply it to the average data warehousing project which has a single shareed database right at the heart of the entire solution. Take a look and let me know what you think.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 29, 2008

and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox. Its nearly impossible to get a good read on all six attributes in a single interview, so its important to design an interview process that will give you a good sampling of data to look at.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

FEBRUARY 16, 2009

This is one of the most powerful aspects of web architecture, and it often gets lost in other client-server programming paradigms. Its design goals arent geared towards efficiency in terms of technical costs. To return to the case of the thick-client MMOG, there are some additional design constraints. Thanks for the comments.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

DECEMBER 28, 2009

A typical "new feature" release is, in my experience, about 80% changes to underlying APIs or architecture. You might have the interaction designer who designed it take a look to see if it really conforms to their design. Switching these customers directly to continuous deployment sounds harder than it really is.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

JANUARY 28, 2009

The engineering team has decided its reached a breaking point, and is taking several weeks to bring it up to modern standards, including unit tests, getting started with continuous integration , and a new MVC architecture. On the other, they already have a team fully engaged on making their product architecture better.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

SEPTEMBER 22, 2008

A second idea is that less is more in product design: A key tenet of the philosophy is that uncluttered products with fewer, better features are preferred to similar products with more features. Someone has managed to convince themselves that they have to do their big architecture change in one fell swoop.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

APRIL 26, 2009

Making UGC work requires good tools, open standards, and proper incentive design. Open APIs and data-oriented architecture (aka "web 2.0"). Personally, the framework Ive found most helpful is MTVs "create, share, validate" feedback loop. By focusing on giving creators all three, we were able to reap the rewards of their shared efforts.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

SEPTEMBER 8, 2009

Policy makers need to know: regulations designed to manage big-companies actually protect those companies by stifling innovation (and competition) from startups. You can see the design of the program here. September 8, 2009 6:25 PM dbsaid. Big companies can afford entire departments dedicated to compliance. conference attendees.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

JUNE 15, 2009

Both sides start to think of their point of view in moralistic terms: “those guys don’t see the economic value of fast action, they only care about their precious architecture diagrams&# or “those guys are sloppy and have no professional pride.&# Take a look and let me know what you think.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Cracking the Code

OCTOBER 10, 2008

Given the different architecture and high service level expectations in the SaaS industry, companies are faced with questions about latency, data access and security through replicated local datacenters, in-country customer support personnel, packaged integration with other regional software and SaaS products, and other similar issues.

Software Review 48

Software Review North America Europe Metrics 48

techcrunch.com

OCTOBER 23, 2010

Tech Gadgets Mobile Enterprise GreenTech CrunchBase TechCrunch TV Disrupt SF More TechCrunch TV Beta Invites Crunchies Elevator Pitches Gillmor Gang Podcasts TechCrunch Europe TechCrunch Trends TechCrunch France TechCrunch Japan Whats Hot: Android Apple Facebook Google Microsoft Twitter Yahoo Zynga Subscribe: From Nothing To Something.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84