From: Tyler Adams <coppero1237@gmail.com>
To: Jon Steinhart <jon@fourwinds.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Favorite unix design principles?
Date: Sat, 30 Jan 2021 22:06:45 +0200 [thread overview]
Message-ID: <CAEuQd1Dpbcs=kd0XynnwUkYoL_UgRfd355ttZcsLiB8Hf4gEXQ@mail.gmail.com> (raw)
In-Reply-To: <202101301950.10UJoWeA456408@darkstar.fourwinds.com>
[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]
Really? Except for one particularly incompetent team, I cannot recall
working with nor reviewing code that sacrificed clarity for performance.
Tyler
On Sat, Jan 30, 2021 at 9:51 PM Jon Steinhart <jon@fourwinds.com> wrote:
> Tyler Adams writes:
> >
> > For sure, I've seen at least two interesting changes:
> > - market forces have pushed fast iteration and fast prototyping into the
> > mainstream in the form of Silicon valley "fail fast" culture and the
> > "agile" culture. This, over the disastrous "waterfall" style, has led to
> a
> > momentous improvement in overall productivity improvements.
> > - As coders get pulled away from the machine and performance is less and
> > less in coders hands, engineers aren't sucked into (premature)
> optimization
> > as much.
>
> It's interesting in more than one way.
>
> The "fail fast" culture seems to result in a lot more failure than I find
> acceptable.
>
> As performance is less in coders hands, performance is getting worse. I
> haven't seen less premature optimization, I've just seen more premature
> optimization that didn't optimize anything.
>
> My take is that the above changes have resulted in less reliable products
> with poor performance being delivered more quickly. I'm just kind of weird
> in that I'd prefer better products delivered more slowly. Especially since
> much of what counts as a product these days is just churn to keep people
> buying, not to provide things that are actually useful.
>
[-- Attachment #2: Type: text/html, Size: 2065 bytes --]
next prev parent reply other threads:[~2021-01-30 20:07 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 11:10 Tyler Adams
2021-01-25 12:32 ` Steve Nickolas
2021-01-26 2:06 ` M Douglas McIlroy
2021-01-26 2:53 ` Steve Nickolas
2021-01-26 10:22 ` Tyler Adams
2021-01-26 12:26 ` John P. Linderman
2021-01-26 15:23 ` Clem Cole
2021-01-26 16:00 ` Niklas Karlsson
2021-01-26 16:13 ` Adam Thornton
[not found] ` <CAKH6PiXKjksEpQOMMMQTbcsMvX2thz3WzqjoRWJAsXnZ4Eq_iQ@mail.gmail.com>
2021-01-30 19:01 ` Tyler Adams
2021-01-30 19:50 ` Jon Steinhart
2021-01-30 20:06 ` Tyler Adams [this message]
2021-01-30 21:28 ` Clem Cole
2021-01-30 21:42 ` Dave Horsfall
2021-01-30 21:45 ` Tyler Adams
2021-01-30 22:31 ` Larry McVoy
2021-01-30 22:28 ` Larry McVoy
2021-01-30 23:11 ` [TUHS] FreeBSD behind the times? (was: Favorite unix design principles?) Greg 'groggy' Lehey
2021-01-30 23:17 ` Larry McVoy
2021-01-30 23:22 ` Warner Losh
2021-01-30 23:31 ` [TUHS] [SPAM] " Larry McVoy
2021-01-30 23:37 ` Jon Steinhart
2021-01-30 23:54 ` Larry McVoy
2021-01-31 12:23 ` [TUHS] [SPAM] Re: FreeBSD behind the times? Dermot Tynan
2021-01-31 0:00 ` [TUHS] [SPAM] Re: FreeBSD behind the times? (was: Favorite unix design principles?) Bakul Shah
2021-02-09 2:15 ` [TUHS] " Will Senn
2021-02-09 2:16 ` Will Senn
2021-02-09 2:30 ` Greg 'groggy' Lehey
2021-01-31 0:39 ` Steve Nickolas
2021-01-31 1:47 ` Will Senn
2021-01-31 2:25 ` Larry McVoy
2021-01-31 2:52 ` Will Senn
2021-01-31 3:00 ` Larry McVoy
2021-01-31 3:06 ` Will Senn
2021-01-31 3:32 ` John Cowan
2021-02-04 5:43 ` Dave Horsfall
2021-02-04 6:10 ` Angus Robinson
2021-02-04 7:46 ` Andy Kosela
2021-02-04 22:25 ` Dave Horsfall
2021-02-04 15:45 ` Will Senn
2021-02-04 16:03 ` Henry Bent
2021-02-04 16:32 ` Dan Cross
2021-02-04 16:49 ` Will Senn
2021-02-04 17:46 ` Larry McVoy
2021-02-04 18:41 ` Bakul Shah
2021-02-04 22:28 ` George Michaelson
2021-02-04 22:41 ` Bakul Shah
2021-02-05 0:33 ` Larry McVoy
2021-02-05 5:17 ` Bakul Shah
2021-02-05 14:18 ` Larry McVoy
2021-02-05 18:16 ` Warner Losh
2021-02-05 18:21 ` ron minnich
2021-02-06 0:03 ` Bakul Shah
2021-02-06 2:06 ` Dan Cross
2021-02-06 3:01 ` Bakul Shah
2021-02-06 1:18 ` John Gilmore
2021-02-06 1:43 ` joe mcguckin
2021-02-06 1:55 ` Bakul Shah
2021-02-05 20:50 ` Dave Horsfall
2021-02-06 0:21 ` Brad Spencer
2021-02-06 2:22 ` Rico Pajarola
2021-02-06 2:55 ` Larry McVoy
2021-02-06 3:07 ` Will Senn
2021-02-27 8:54 ` Stuart Remphrey
2021-02-06 4:55 ` John Cowan
2021-02-04 7:46 ` Chris Torek
2021-02-04 15:47 ` Will Senn
2021-02-11 21:01 ` Angel M Alganza
2021-01-30 23:09 ` [TUHS] Favorite unix design principles? John Cowan
2021-01-30 23:22 ` Jon Steinhart
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEuQd1Dpbcs=kd0XynnwUkYoL_UgRfd355ttZcsLiB8Hf4gEXQ@mail.gmail.com' \
--to=coppero1237@gmail.com \
--cc=jon@fourwinds.com \
--cc=tuhs@tuhs.org \
/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;
as well as URLs for NNTP newsgroup(s).