Duct Tape Marketing

NOVEMBER 9, 2022

Click on over and give us a review on iTunes, please! John Jantsch (00:00): This episode of the Duct Tape Marketing Podcast is brought to you by Marketing Against the Grain, hosted by Kip Bodner and Keion Flanigan is brought to you by the HubSpot Podcast Network, the audio destination for business professionals. Duct Tape Transcript.

Marketing 93

Marketing Differentiation Sacramento Small Business 93

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. Do you fix bugs before writing code? Completely necessary.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

A Smart Bear: Startups and Marketing for Geeks

AUGUST 30, 2010

Rob Walling generously allowed me to reprint this excerpt from his new book, "Start Small, Stay Small: A Developer's Guide to Launching a Startup" available in paperback and Kindle from Amazon and in PDF and ePub from StartupBook.net. Most of us have worked in corporate environments where you're never allowed to go back and refactor code.

Software Review 284

Software Review Startup Technical Review Hosting 284

Startup Lessons Learned

NOVEMBER 13, 2008

A new bit of code contained an infinite loop! why did that code get written? Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Most engineers would ship code to production on their first day.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JULY 29, 2009

But there is more to technical debt than just the interest payments that come due. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. In particular, try these three things: Invest in technical debts that may never come due.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software? I dont think so.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Duct Tape Marketing

NOVEMBER 1, 2017

And it worked great for the audio book, too, because then I didn’t have to do the whole thing by myself. The one side, I think it’s a really interesting point you bring up, which is does it immediately lean toward to creating new products and services? Could you leave an honest review on iTunes? So, there you go.

Cost 55

Cost Marketing Audience Media 55

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. When a developer wants to check-in code, this is a very scary moment.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

DECEMBER 8, 2008

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.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. The batch size is the unit at which work-products move between stages in a development process. For software, the easiest batch to see is code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

OCTOBER 5, 2008

Each specialist takes up his part of the spec (UI, middleware, backend) and cranks out code. This system naturally lends itself to a pipeline approach, which the product manager organizes. So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

DECEMBER 7, 2008

When I want to know about some concurrency issues between services in his cluster, he doesnt blink an eye when I suggest we get the source code and take a look. Hes just as comfortable writing code as racking servers, debugging windows drivers, or devising new interview questions. He throws off volumes of code, and it works.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Startup Lessons Learned

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. Over time, such teams either explode due to irreconcilable differences or dramatically slow down.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

JULY 2, 2009

For example, a site outage may seem like it was caused by a bad piece of code, but: why was that code written? The net effect of all this was to make new engineers incredibly productive right away – in most cases, we’d have them deliver code to production on their very first day.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

JUNE 17, 2010

I was the junior guy on a project team; I was called in to do some technical due diligence for reasons that were obscure to me, because the team already had much more senior engineers assigned to it. And like feedback on a simple microphone sound system, this would occasionally boil over into screeching.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

FEBRUARY 10, 2009

Our code pushes take another six minutes. Since these two steps are pipelined that means at peak we’re pushing a new revision of the code to the website every nine minutes. On average we deploy new code fifty times a day. Code reviews and pairing Great practices. Throwing out a lot of code.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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 same might be said of good software. Here we have the beginnings of a theory of design for software.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

SEPTEMBER 15, 2008

And we were fortunate to have Steve Blank , the originator of customer development, on our board to keep us honest. Code To make split-testing pervasive, it has to be incredibly easy. Whenever you are developing a new feature, or modifying an existing feature, you already have a split-test situation. Great post Eric!

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

MARCH 25, 2010

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. This is the first post that moves into making specific process recommendations for product development.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

MAY 7, 2009

Getting features and fixes into hands of users was the greatest priority - a test environment would just get in the way and slow down the validation coming from having code running in production. When a new engineer started at IMVU, I had a simple rule: they had to ship code to production on their first day.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

OCTOBER 5, 2009

Due to an interaction effect between your hardware, solar flares, and quantum flux, this virus will crash your computer and erase your hard drive sometime soon. In the past, we invested in brilliant architecture, code reuse, refactoring, modular design, etc. I have detected a secret virus in your CPU. The curse of prevention Beware!

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

MARCH 3, 2009

Take a failed product launch. At IMVU , these were quite common (after all, were shipping code 50 times a day). They are collected and reviewed after an appropriate interval (e.g. With due respect to the author’s obvious smarts, these ideas are too logical to be new. This policy doesnt leave much room for excuses.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

AUGUST 30, 2008

Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# This basic pattern is useful in all aspects of product development. This process is called refactoring.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Startup Lessons Learned

AUGUST 3, 2009

Critical also, as the lean company/start-up can not be lean by just using lean principles in IT and not in Product Development/Management - a common misinterpretation of the Toyota Production System. My experience is in Enterprise Software - where we are forced to chunk features into formal releases.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

FEBRUARY 22, 2009

See Paul Grahams Why Nerds are Unpopular to learn more) Take a look at this article on a programming Q&A site: How old are you, and how old were you when you started coding? We also learned that law is code , and that leadership was needed to build thriving communities in a digital age. Can I send you a review copy?

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

APRIL 4, 2010

Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

MAY 31, 2010

And a special thanks is due to all of our presenters, panelists, and mentors. Kent Beck is deservedly famous for his many contributions in the software industry. Unfortunately, the video of our sllconf conversation is not online (due to technical problems), but we have a physical tape backup which we are endeavoring to get online soon.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

AUGUST 2, 2008

Your natural tendency when an investor says yes will be to relax and go back to writing code. When an investor says he wants to invest in you, or an acquirer says they want to buy you, dont believe it till you get the check. Alas, you cant; you have to keep looking for more investors, if only to get this one to act.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

AUGUST 26, 2009

If you watch the video/audio below, youll get to see some of the questions I was asked after my presentation. I did my best to capture video and audio; a YouTube playlist and Slideshare slidecast are below: Slides (with audio): 2009 08 19 The Lean Startup TechStars Edition View more presentations from Eric Ries.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

AUGUST 24, 2009

When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. For example, the best book reviewers only review books published by the best publishers, which only accept manuscripts from the best agents. And how could they possibly review a blog? Is that a lot?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

NOVEMBER 6, 2008

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. Three concepts I found particularly helpful: Process = discipline.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

JULY 5, 2010

Instead of that naive approach, I wish Id had a book like this one, to help me figure out how to get started with customer development step-by-step. While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

FEBRUARY 16, 2009

Lets start with a distinction between shipping new software to the customer, and changing the customers experience. The idea is that often you can change the customers experience without shipping them new software at all. But I think its more productive to think of this as a spectrum.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

DECEMBER 14, 2009

They aren’t really engaged in customer development, they aren’t getting inside their customers’ heads, and they aren’t crafting a robust ecosystem. For a consumer internet company in particular, this is often due to a lack of design thinking. They get focused solely on growth. They get focused solely on growth.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

SEPTEMBER 18, 2008

All I see is a name, an icon, a price, the developers name, and a review star-rating. The reviews are all over the map. But even clicking through to see a screenshot and some reviews is incredibly time consuming, given the hundreds of apps in most categories. I cant really tell.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74