rob.by

MARCH 8, 2012

Finding Technical Cofounders Is Hard. Yesterday, Michael Pope posted an article titled Technical Cofounders Are a Myth. He begins by explaining how he arrived at his conclusion: I began the hunt to find a technical co-founder – a software engineer who works for no cash – to help me build my dream website.

Technical Cofounder 42

Technical Cofounder Cofounder Software Engineering Fractional CTO 42

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 8, 2008 The lean startup Ive been thinking for some time about a term that could encapsulate trends that are changing the startup landscape. After some trial and error, Ive settled on the Lean Startup. I like the term because of two connotations: Lean in the sense of low-burn.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

blog.chrisomeara.com

OCTOBER 23, 2010

Chris OMeara Main | Probing Code Quality » 01/31/2010 Startup CTO: Could It Work? A CEO friend of mine recently asked my opinion about Tony Karrers Startup CTO or Developer article. I think the part time CTO could work. A few had the title CTO but they all fit the technical rock star and hacker profile.

Fractional CTO 40

Fractional CTO CTO Hire Startup Cofounder 40

David Teten

OCTOBER 1, 2015

Should you co-found your company with a software development shop? I’ve talked with a number of software development shops who are eager to get into the business of cofounding companies, i.e., getting product revenue and equity instead of just consulting revenue. What are the terms of their relationship with the founder?

Software Developers 60

Software Developers Software Development Software Review Technical Cofounder 60

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 previously co-founded and served as Chief Technology Officer of IMVU. He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). Thanks much.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 22, 2008

You get increasing growth by optimizing the viral loop , and you get revenue as a side-effect, assuming you have even the most anemic monetization scheme baked into your product. Paid - if your product monetizes customers better than your competitors, you have the opportunity to use your lifetime value advantage to drive growth.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

JULY 28, 2010

kaChing has been very active in the Lean Startup movement. With case studies like this, we aim to illustrate specific Lean Startup techniques through the stories of current practitioners. Yet there’s a lot of mystery around pivots, and entrepreneurs ask all the time how you know it’s time to commit to a new direction.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Up and Running

MAY 23, 2016

Noah has been a key figure in the making of LivePlan, our own SaaS product. Step 1: Start with a lean plan. It’s the fastest way to get your idea onto paper, and it’s the very first step in the lean planning process, which is much easier and more iterative than traditional business planning methods.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Thats not the goal of a lean startup. One such practice is to pivot from one vision to the next.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

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. And we cant hire new engineers any faster, because you cant be interviewing and debugging and fixing all at the same time! Just change it. All is not lost, though.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

SEPTEMBER 28, 2008

Lessons Learned by Eric Ries Sunday, September 28, 2008 The lean startup comes to Stanford Im going to be talking about lean startups (and the IMVU case in particular) three times in the next two weeks at Stanford. Labels: events , lean startup 5comments: Hitchens said. The Lean Startup Intensive is tomorrow at Web 2.0.

Lean 68

Lean San Francisco Continuous Deployment Startup 68

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

Hearpreneur

JULY 8, 2017

Todd McGuire is the Chief Technology Officer and co-founder of startup incentaHEALTH and we had to the opportunity to hear from him about starting business, the future of the company and what entrepreneurship means to him. I am the co-founder and CTO of the digital health care company incentaHEALTH.

Technical Review 48

Technical Review Fractional CTO CTO CTO Hire 48

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. You cant do science and be defensive at the same time. By starting a new product off with as few features as possible (1?),

Product Development 68

Product Development Developer San Francisco Product 68

The Next Web

DECEMBER 4, 2013

Denis Duvauchelle is the CEO and co-founder of Twoodo , the ultimate online collaboration tool. “I These categories came from Yonder conference , a conference held to discuss just such challenges and solutions: hiring and onboarding. Hire those you trust. I can’t work effectively at home.”. when to meet face to face.

Management 152

Management SCRUM CTO Hire Distribution 152

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. One major theory that has influenced the way I think about processes comes from Lean Manufacturing , where they use these same techniques to build cars.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

MAY 7, 2009

They were deploying to production with every commit before they had an automated build server or extensive automated test coverage in place. Initially, IMVU sought to quickly build a product that would prove out the soundness of their ideas and test the validity of their business model.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

Austin Startup

AUGUST 11, 2017

By Kevin Sproles, founder and CEO of Austin’s Volusion “The best companies are deliberate about culture. The co-founder of Hubspot hit it on the head with this quote. First, put in the time Every important aspect of your business needs the appropriate amount of time and dedication. They design it and defend it.”

CTO Hire 48

CTO Hire Austin Cofounder eCommerce 48

Startup Lessons Learned

SEPTEMBER 2, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. . The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 13, 2008

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? In a mature company with a mature product, the goal is to pay for lots of people to come to your website. chatted five times?

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

www.chubbybrain.com

SEPTEMBER 28, 2011

After a thorough analysis of those 32 start-up post-mortems, we have determined the common reasons founders gave to compile this list of the top 20 ways to have your startup fail. 19 – Not working on it full time. This is a very specific audience dictated by my decision not to build a consumer product. #17 Startups are hard.

Cofounder 89

Cofounder Startup Technical Cofounder CTO Hire 89

Startup Lessons Learned

SEPTEMBER 10, 2008

Of the techniques he mentioned, I think four are fundamental and critical for any lean startup: TDD (or the even more politely named TATFT ) Continuous integration Automate your deployments Collect statistics The tools to help you do these things are getting better and better every day, but dont confuse tools with process. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 12, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. for Harvard Business Revie.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 14, 2008

In the very early days, the trick is to find anyone at all who can understand you when you are talking about your product. In our first year at IMVU, we thought we were building a 3D avatar chat product. As product people, we thought of competition in terms of features. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. He wrote it in 2000, and as far as I know has never updated it.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JANUARY 12, 2009

When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. Add onto that the incredible amounts of infrastructure code that we reused, and we were able to bring our product to market months earlier. I am CTO of a SaaS vendor, and we use PHP.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 5, 2008

October 13, 2008 9:44 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Steve Blank

OCTOBER 5, 2009

A Phone Call After I left MIPS Computers I was in New York tagging along with a friend (a computer architect whose products at Apple a decade later would change the shape of personal computing) who was consulting for a voice recognition startup. Unlike Intel chips, MIPS chip architecture also made it possible to plug in a math co-processor.

North Carolina 125

North Carolina Silicon Valley Fractional VPE Part-Time VPE 125

SoCal CTO

DECEMBER 1, 2010

I continue to collect great content that is the intersection of startups, products, online and technology. Equity-Only CTO and Equity-Only Developers - SoCal CTO , November 1, 2010 I had a recent email dialog with the founder of a company looking for a CTO for their startup. Was it a Startup Founder Developer Gap

Technical Review 175

Technical Review Technology Product CTO Hire 175

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: continuous deployment 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 1, 2008

Lessons Learned by Eric Ries Monday, September 1, 2008 Test-Driven Development as andon cord You cannot control what you cannot see, and the hardest part of managing software projects is that the final product is so intangible. These tests are written by the engineers themselves, and they must all pass every time. Expo SF (May.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 18, 2008

Many of them have really cool products shipping or about to be released, and I wholeheartedly agree with my friends at the iFund that the next generation of applications is going to be amazing. The store determines which products sit on which shelves, and which yours sits next to. Ive also been playing around with the App Store.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 8, 2008

So one of the first things we did was to hire an Oracle expert and get to work. 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. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

SEPTEMBER 10, 2008

I see startups struggle with this all the time. You have customers, they are using your product, and you are trying to help them. Too often, startup founders talk about how they are pushing to get to “critical mass&# and how “economies of scale&# are going to kick in. But then what? And fix the ones from before.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

techcrunch.com

OCTOBER 23, 2010

So for this first post, here’s the best advice I can give you: join an awesome founding team and get your product out the door ASAP. One of the things I do as a founder of a later stage startup is to meet with early stage entrepreneurs to help them get their companies going. Then, forget everything else, VCs included, and just build.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

Startup Lessons Learned

SEPTEMBER 10, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. for Harvard Business Revie.

San Francisco 60

San Francisco Continuous Deployment DC Lean 60