Startup Lessons Learned

OCTOBER 4, 2008

Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). While I was still in high school, I became a Java "expert" during a time when there was no such thing.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

YoungUpstarts

APRIL 25, 2019

An integrated workflow supports rapid deployment and flexible workflows. While workflows can be customized, automation provides for standardization of environments and processes. Open source solutions will be free or inexpensive but may take more time on the front end to configure and customize. Kubernetes.

Java 127

Java XML Open Source Continuous Deployment 127

Startup Lessons Learned

NOVEMBER 29, 2008

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. At the time, I was a die-heard Java zealot. Were there to serve customers direclty, as well as all of the other functions of the company.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

JANUARY 12, 2009

The inimitable Paul Graham has an excellent essay called The Python Paradox in which he argues: that you could get smarter programmers to work on a Python project than you could to work on a Java project. I didnt mean by this that Java programmers are dumb. I meant that Python programmers are smart.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

JULY 29, 2009

Unfortunately, customers hated that initial product. Unfortunately, we made two critically flawed assumptions: that customers would primarily consume first-party assets that we shipped to them on CD and that they would tend to congregate in a relatively uniform way. How likely will customers ultimately use that feature?

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

FEBRUARY 12, 2009

To wit: achieving product/market fit , getting customer validation , making something people want , things that matter , and of course the many excellent books on the topic, of which Ill mention just two of the best, Crossing the Chasm and The Innovators Dilemma. Is a market a set of paying customers? Remember Java? Tough sell.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89