General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: David Lang <david@lang.hm>, Michael Richardson <mcr@sandelman.ca>,
	 Jonathan Morton <chromatix99@gmail.com>,
	 bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] FW: [Dewayne-Net] Ajit Pai caves to SpaceX but is still skeptical of Musk's latency claims
Date: Sat, 13 Jun 2020 17:03:13 -0700 (PDT)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2006131652220.16262@qynat-yncgbc> (raw)
In-Reply-To: <1592073681.126716238@apps.rackspace.com>

On Sat, 13 Jun 2020, David P. Reed wrote:

> On Saturday, June 13, 2020 1:43am, "David Lang" <david@lang.hm> said:
> 
>
>> Remember, Musk already sacked the starlink leadership once for being to stuck in
>> 'the way satellites are always built' so if it doesn't work well under load and
>> they can't fix it, he will find people who can.
> 
> He just might. Depends on who he asks. The fact that ATT literally couldn't 
> fix its network for at least a year, and spent most of that year blaming Apple 
> and the design of the iPhone, asking the right people isn't what arrogant 
> organizations are good at.

Musk has shown that he is not stuck on "this is the way we've always done 
things" and conventional wisdom. He's also shown a willingness to scrap existing 
plans and infrastructure when it is shown not to work.

> And firing people appeals to those who think Trump 
> is brilliant as a manager - he appeals because he says "you're fired". I think 
> sacking whole teams is an indication of someone who has risen to his level of 
> incompetence, but that's just my opinion.

he sacked the management team, not everyone, and when you are doing new stuff 
and you have people playing the "we'll just ignore the bosses instructions 
because we know the industry better" they deserve to get sacked.

take a look at the first pair of starlink test satellites (before the change) 
and what they are launching now. What they are doing now breaks a TON of 
'industry best practices' in satellite design, but the result is much cheaper, 
and much cheaper to lunch that allows scalability that wasn't possible with the 
old model.

traditionally, satellites are very expensive, because the cost to lauch them was 
so high that it made sense to put lots of money into each satellite. As launch 
costs plummet, you can afford a slightly higher failure rate potential to a 
drastic cost reduction.

Musk is overly optomisitic, but that's a good thing because without that 
optimisim he wouldn't even try the things he's doing. He has a solid track 
record of failing to meet his initial goal/deadline, but continuing to work and 
eventually exceeding his initial goals (even if it's a bit later than he 
planned)

I see no reason that starlink would be any different.

David Lang



  reply	other threads:[~2020-06-14  0:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 16:03 David P. Reed
2020-06-11 16:14 ` Jonathan Morton
2020-06-11 18:46   ` David P. Reed
2020-06-11 18:56     ` David Lang
2020-06-11 19:16       ` David P. Reed
2020-06-11 19:28         ` David Lang
2020-06-12 15:39           ` Michael Richardson
2020-06-13  5:43             ` David Lang
2020-06-13 18:41               ` David P. Reed
2020-06-14  0:03                 ` David Lang [this message]
2020-06-14  0:36               ` Michael Richardson
2020-06-14  1:17                 ` David Lang
2020-06-14 15:40                   ` David P. Reed
2020-06-14 15:57                     ` Michael Richardson
2020-06-14 21:04                       ` David P. Reed
2020-06-14 23:13                         ` Michael Richardson
2020-06-12 15:30     ` Michael Richardson
2020-06-12 19:50       ` David P. Reed
2020-06-13 21:15         ` Michael Richardson
2020-06-13 23:02           ` Jonathan Morton
2020-06-14  0:06           ` David Lang
2020-06-14 11:23   ` Roland Bless

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=nycvar.QRO.7.76.6.2006131652220.16262@qynat-yncgbc \
    --to=david@lang.hm \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=dpreed@deepplum.com \
    --cc=mcr@sandelman.ca \
    /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