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.

Japan 162

Japan Singapore Architecture Social Media 162

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. We didnt think wed able to compete with that.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. So dont just kill the feature - iterate.

Product Development 68

Product Development Developer San Francisco Product 68

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

Build a truly mainstream product. Build the product in stealth mode to build buzz for the eventual launch. The whole company and board play-tested the product to see its new features first hand. Everyone had fun; the product worked. Even a great architecture becomes inflexible. Focus on quality.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

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. In this scheme, all of the data related to a specific feature of a product are stored on the same machines. Two of my favorites are from Flixster and LiveJournal. Easy to understand.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Unfortunately, customers hated that initial product.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Take a look and let me know what you think.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

www.lanceglasser.com

MAY 13, 2012

Product development. Queuing theory and product development. The Essential Product Investigation Phase Gate. So you want to ship the product early? The minimum viable product. Thank you Japan. Stock buybacks. The Year of the Black Swan. Definitions of common financial terms. General Management. Bah, humbug.

CTO 40

CTO CTO Hire Technical Review Architecture 40

Startup Lessons Learned

JUNE 17, 2010

The art team would often be involved in the specification phase of a new feature, since they were responsible for the look-and-feel of the product. When the art team would review the final product, they were inevitably outraged – it deviated from the spec in ways they considered major.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Hearpreneur

JANUARY 24, 2018

It might be the products or the customers they deal with, or it could even be the fact that they are the ones in charge of it all. In other words, I love to challenge the cosmetic industry by creating products which I know are revolutionary and will help everyone be more efficient. 1- Growth. It is ‘the love of my life’.

Entrepreneur 95

Entrepreneur PPC Green Japan 95

Startup Lessons Learned

NOVEMBER 13, 2008

Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. Each five whys email is a teaching document. and so forth.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. He has a good team, and theyve shipped a working product to many customers.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. We talk about taking advantages of the incredible agility offered by modern web architecture for extremely rapid deployment, etc.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. The "just fix it" mentality is counter-productive here.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

AUGUST 8, 2009

One of the topics that raised heated debate was whether I had conflated technical design with product design , because I made the admittedly counter-intuitive claim that sometimes good technical design actually leads to increased technical debt. 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 8, 2008

You dont need to invent a new architecture, and you dont need to even build your architecture up-front. You can turn your entire application infrastructure investment into a pay-as-you-go variable cost, and bring new products to market at speeds an order of magnitude faster than just 10 years ago. yeah, its awesome.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. For a marketing job, for example, its reasonable to expect that a candidate will have done their homework and used your product (maybe even talked to your customers) before coming in.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

JANUARY 28, 2009

They have a product that has a moderate number of customers. Still, theyre not really hitting it out of the park, because their product isnt growing new users as fast as theyd like, and they arent making any money from the current users. 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

DECEMBER 28, 2009

Most customers of most products hate new releases. Thats a perfectly reasonable reaction, given that most releases of most products are bad news. Even worse, the sad state of product development generally means that the new "features" are as likely to be ones that make the product worse, not better.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

FEBRUARY 16, 2009

Joe Ludwig goes through his current release process and determines that the current time to make and deploy a release is about seven and half hours, which is why his product is released about once a month. This is one of the most powerful aspects of web architecture, and it often gets lost in other client-server programming paradigms.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

JUNE 15, 2009

This condition makes it much easier for teams to innovate, experiment, and achieve sustained productivity. And, of course, the code rarely performs in production the way it does in the testing or staging environment, which leads to a series of hot-fixes immediately following each release.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

crowdSPRING Blog

AUGUST 2, 2017

Some are useful but others can be distracting and counter-productive. The aesthetic was widely known in Japan as Ma, an architectural philosophy which translates to “the space between” Instead of that space standing for a gap, the philosophy of Ma views it as the negative space, the silence, and the root of meaning.

Architecture 63

Architecture Design Japan Boston 63

crowdSPRING Blog

AUGUST 2, 2017

Some are useful but others can be distracting and counter-productive. The aesthetic was widely known in Japan as Ma, an architectural philosophy which translates to “the space between” Instead of that space standing for a gap, the philosophy of Ma views it as the negative space, the silence, and the root of meaning.

Architecture 48

Architecture Design Japan Boston 48

Cracking the Code

OCTOBER 10, 2008

Like SaaS products themselves, we now intend for these laws to be periodically refined through major releases to reflect the changing landscape of the SaaS world. Save Asia for post-IPO Single instance, multi-tenant, single datacenter - Have only one version of the code in production. Bessemer SaaS Law #6.

Software Review 48

Software Review North America Europe Metrics 48

Startup Lessons Learned

SEPTEMBER 8, 2009

I'll add two ideas: The modern structure of university patent licensing and technology transfer works really well in the life sciences and other fields with expensive product development processes. You can view it at [link] September 9, 2009 3:34 PM Hamish MacDonald said. Take a look and let me know what you think.

DC 90

DC Washington San Francisco SBIR 90

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