Live data from Hacker News

Poll: Do you actually use the product you are working on?

news.ycombinator.com

181–190 of 226 posts

Re: Poll: Do you actually use the product you are working on?

#181

Dog fooding is certainly one way to develop software, and I respect enormously the companies that do it, but "software for software developers" is a rather small subset of e.g. B2B software. I don't use Appointment Reminder like my customers do. I can't, because I don't own an HVAC company with 200 appointments this week. I suppose I could force myself to use it for e.g. reminding myself of my own appointments, but t…

Dogfooding doesn't have be limited to "software for software developers." A lot of it is "software for software businesses" or "software for problems which occur in software businesses, but which are not unique to software businesses."

Any of the above is probably "dogfooding" for small companies where people wear many hats while having lowish internal firewalling and power disparity. It's often much less useful at a BigCo where the product team may never see the internal users without scheduling a meeting in advance, and where fixed development schedules and internal politics are creating design lock-in.

Also keep in mind that, for every story about dogfooding improving product quality, there are others about dogfooding creating a runaway blind spot because the company confused the needs of internal users with the needs of customers. Internal use can be a useful resource, but it can't replace customer research.

Re: Poll: Do you actually use the product you are working on?

#184
We just added a new page in our admin panel labelled 'dog food' and will be using that as a testing lab. The product we sell is a technology for sales teams and now that we are out selling ourselves we have a greater need for our own product.

Although the conventional wisdom is to build things you had a need for yourself, I believe this is one of the riskiest ways to create breakthrough innovations. Far easier to go find people who have a problem and who are not developers and get them to pay for something.

Re: Poll: Do you actually use the product you are working on?

#185

Dog fooding is certainly one way to develop software, and I respect enormously the companies that do it, but "software for software developers" is a rather small subset of e.g. B2B software. I don't use Appointment Reminder like my customers do. I can't, because I don't own an HVAC company with 200 appointments this week. I suppose I could force myself to use it for e.g. reminding myself of my own appointments, but t…

Dogfooding doesn't have be limited to "software for software developers." A lot of it is "software for software businesses" or "software for problems which occur in software businesses, but which are not unique to software businesses." Any of the above is probably "dogfooding" for small companies where people wear many hats while having lowish internal firewalling and power disparity. It's often much less useful at a…

Mobile OS/app development also has excellent dog food potential among geeks.

Re: Poll: Do you actually use the product you are working on?

#186
At my previous employer, a small browser vendor that decided to abandon its own rendering engine and browser stack, I stopped using our product because Linux wasn't a priority. Numerous reasons were given, such as low market share, “only geeks use it”, all journalists use Macs, &c.

This was to the point of ridiculing the platform and the people working on it, frequently citing “Linux jokes” such as “you'll probably have to recompile your kernel first” whenever the question was seriously raised about when we'd start at least getting the core libraries working.

And when I say it wasn't a priority, I mean that we didn't even have something that was in a compilable state. A few people had started fixing up the broken code to get something that would compile on Linux in their own free time. After a few weeks of hacking, they were told by management to stop what they were doing and instead focus their volunteer efforts on the project goals, being to ship a Windows and Mac version.

So the company began the process of forcefully moving developers who'd worked on Linux for over 15 years to platforms they felt uncomfortable and unproductive working on.

This is a much longer tale, but it tells the story of a company alienating not only their loyal user base, but also a significant proportion of their own developers. The result? Lack of motivation and resignations.

Well done.

Re: Poll: Do you actually use the product you are working on?

#189
Mailrox: https://www.mailrox.com/

Stemmed from something painful I had to do every day (build HTML emails) that a web app didn’t exist for. Then I slowly went from using it to every day to running it every day. If you’d have asked the question a year a go I’d have said every day.

Re: Poll: Do you actually use the product you are working on?

#190
post #53

Yes but not as much as I like to. The guys who build a project management tool may benefit the most I think. We are building a site to engage people to write daily (in English), www.dailythem.es, and while I know using the site more is very useful, I have to keep thinking about the business direction and figure out user demographic before I spend all days using my own product.

In this case I probably should consider myself happy: I'm on the developer team of Collabtive, a free open source Basecamp alternative, i.e. a project management software.

In fact it is very easy to use our own product not only for project management in the strict sense of the term, but also for bug tracking, file storage and distribution and community management.

Besides it being useful for us, we have already been able to put a lot of our own requirements into the published version.

Post reply on HN