Remove Presentation Remove Software Engineering Remove Software Review
article thumbnail

Technical Advisors: Every Web/Mobile Startup Must Have One

SoCal CTO

I did a presentation recently for a graduate class from The Founder Institute around getting online/mobile products out the door. I LOVED it because, the presenting part was over quickly and we got into specific issues that the founders had in terms of getting things built. Review the code being built.

article thumbnail

Massacre at IBM

Steve Blank

consisted of product manager, hardware-engineering manager, software-engineering manager, applications analyst, and software designer. We followed that with an hour-long design review, including disclosure of product limitations. For after-dinner drinks we polished the new presentation and said a short prayer.

San Jose 261
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: Continuous integration step-by-step

Startup Lessons Learned

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.

article thumbnail

Lessons Learned: Stevey's Blog Rants: Good Agile, Bad Agile

Startup Lessons Learned

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. Principles of Lean Startups, presentation for Mapl.

Agile 76
article thumbnail

How To Work Better with Your Co-Founder

ReadWriteStart

It's challenging to build, design and deploy software. Almost every software engineer I've ever worked with is irrational in how fast they believe they can build software. A few years ago at SxSW, Jason Fried gave a presentation on " Stuff We've Learned at 37 Signals." Never Minimize the Value of Your Co-Founder.

Cofounder 121
article thumbnail

Revisiting the Software Design Manifesto (and what's changed since.

Startup Lessons Learned

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.

article thumbnail

Lessons Learned from a Software Developer’s First Attempt at Launching a Startup

Software By Rob

Karl is a software engineer with more than 10 years of experience who specializes in agile web development and web services integrations. He authors a software development blog at [link]. There comes a time in a software developer’s career where they reach a crossroads and ask themselves, “What next?