Remove Product Development Remove Software Review Remove Technical Review
article thumbnail

Eric Ries and Kent Beck Discuss Product Development

Startup Lessons Learned

On November 14 (that’s this Thursday) at 1p PT, Eric Ries will speak with Kent Beck, a creator of Agile software development, about facilitating the work of engineers and product teams. At a conference I overheard a couple of programmers make a snarky comment about Test-Driven Development. Crazy, huh?

article thumbnail

How to Handle Competition as a Startup

The Startup Magazine

Source Leverage Advanced Technologies Harnessing advanced technologies can transform how startups operate and compete. For instance, a tech startup might emphasize effortless user interfaces or exclusive technology, while a clothing company might highlight sustainable practices or custom designs.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Embrace technical debt

Startup Lessons Learned

Lessons Learned by Eric Ries Wednesday, July 29, 2009 Embrace technical debt Financial debt plays an important and positive role in our economy under normal conditions. Technical debt works the same way, and has the same perils. I won’t pretend that there aren’t teams that take on technical debt for bad reasons.

article thumbnail

Tech Support *is* sales

A Smart Bear: Startups and Marketing for Geeks

You probably think of "tech support" as the bottom of the food chain. After all: Tech support deals with insane customers. Tech support answers the phone; a job even salesmen don't want. Tech support keeps angry customers at bay while having no power to effect change. Tech support is sales. Yep, that sounds lowly.

article thumbnail

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

What does your Chief Technology Officer do all day? Often times, it seems like people are thinking its synonymous with "that guy who gets paid to sit in the corner and think technical deep thoughts" or "that guy who gets to swoop in a rearrange my project at the last minute on a whim." But along the way, something strange happened.

CTO 168
article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

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.

article thumbnail

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

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.