The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Phil Budne <phil@ultimate.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: regex early discussions
Date: Mon, 04 Mar 2024 13:38:54 -0500	[thread overview]
Message-ID: <202403041838.424IcsR8078692@ultimate.com> (raw)
In-Reply-To: <CAC20D2MFY4g+j+e3OUOLgZtcgnYKu93ENjkG80cH59fr5n44bQ@mail.gmail.com>

On the subject of learning how to use reg-exs:

For the better part of a decade I worked on a VoIP system (whose first
product plan was to replace the POTs network: the CTO had a
candlestick phone (sans dial) in his cube attached to a VoIP ATA
(everyone worked from a cube) to hilight that the telephone UI had
gone from switchboard to dial to number pad, and was past due for
replacement.

The admin UI was a poor stepchild (the UX developer was explicitly
excluded from work on it).  To implement "dial plans" and call
routing, the product had a screen with sed style match and
replacements.

My involvement with the product started in the second product plan: a
multi-tenant conferencing system in a 1U box, first at a startup,
after the startup was acquired by Alcatel, Alcatel became
Alcatel-Lucent, and finally when ANOTHER startup purchased rights to
maintain the code as critical to their operations.

In that final setting, I ended up in a room with about 30 customer
service representatives, none of whom I could easily imagine had ever
C.S. course.  I expressed my amazement at their ability to deal with
the reg-ex interface, and apologized the fact that they had to deal with an
interface with such sharp edges!

      reply	other threads:[~2024-03-04 18:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04  1:30 [TUHS] " Will Senn
2024-03-04  2:03 ` [TUHS] " Marc Rochkind
2024-03-04  3:38   ` Larry McVoy
2024-03-04  4:18     ` Rich Salz
2024-03-04  7:51     ` Alec Muffett
2024-03-04  8:17     ` Rob Pike
2024-03-04  8:43       ` Alec Muffett
2024-03-04 14:25         ` Jan Schaumann via TUHS
2024-03-04 10:21       ` Bakul Shah via TUHS
2024-03-04 14:34     ` Larry McVoy
2024-03-04  7:10   ` Otto Moerbeek via TUHS
2024-03-04  7:19     ` Dave Long
2024-03-04  7:25       ` arnold
2024-03-04 12:05         ` Ralph Corderoy
2024-03-04 13:01           ` arnold
2024-03-04  7:25     ` Otto Moerbeek via TUHS
2024-03-04 12:00   ` Peter Weinberger (温博格) via TUHS
2024-03-04 17:05   ` Will Senn
2024-03-04 18:43     ` Rich Salz
2024-03-04 20:57       ` Bakul Shah via TUHS
2024-03-04 21:05       ` Steffen Nurpmeso
2024-03-04 13:17 ` Alan D. Salewski
2024-03-04 16:57 ` Clem Cole
2024-03-04 18:38   ` Phil Budne [this message]

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=202403041838.424IcsR8078692@ultimate.com \
    --to=phil@ultimate.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).