General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: davecb@spamcop.net
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] building a better toaster
Date: Mon, 2 Jul 2018 03:17:08 +0300	[thread overview]
Message-ID: <D9D99623-63B0-4420-BA3B-31655877389B@gmail.com> (raw)
In-Reply-To: <776b2a30-071c-bb36-42a4-dee3e6596c79@rogers.com>

> On 2 Jul, 2018, at 2:34 am, David Collier-Brown <davec-b@rogers.com> wrote:
> 
> If you put your cost accountants in one silo and your engineers in another, you get to be an ex-company (;-))

Maybe so, but if you let the former have absolute authority over the latter, you'll end up with the same shoddy far-eastern-made crap as everyone else, because buying the standard mass-produced components and plugging them together is all the budget will allow for.  Likewise, if you let Marketing dictate the schedule, you *will* end up releasing something unfinished and buggy as hell, because it took 80% of the time to reach feature-complete and the remaining 20% is distribution lead-time, not available for debugging or even basic usability testing.

The fact that both of the above happen far too often is a source of intense frustration.  The fact that many retailers won't even bother stocking a higher-quality product that happens to exist is downright *insulting*.

I could give you all sorts of railway analogies to go with this.  The British railway industry alone is a rich vein of examples of abject stupidity contrasted with brilliance.

There is a middle ground.  Have cost be one of the factors for the engineers to optimise for, but don't make it the overriding factor.  Tell them the commercial benefits of shipping in time for the holiday season, or back-to-school, or whatever - but let *them* decide if it's worth rushing the product out to meet that schedule.  Consequently, you'll get a better product that might just surprise the market.

 - Jonathan Morton


  reply	other threads:[~2018-07-02  0:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30 15:28 Dave Taht
2018-06-30 17:36 ` Jonathan Morton
2018-07-01 23:34   ` David Collier-Brown
2018-07-02  0:17     ` Jonathan Morton [this message]
2018-07-02  1:36       ` David Collier-Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D9D99623-63B0-4420-BA3B-31655877389B@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=davecb@spamcop.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox