The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: steve jenkin <sjenkin@canb.auug.org.au>
To: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Has this been discussed on-list? How Unix changed Software.
Date: Wed, 7 Sep 2022 14:00:22 +1000	[thread overview]
Message-ID: <E0DE5E28-2F17-47FE-83CE-ED8D9407D8A0@canb.auug.org.au> (raw)
In-Reply-To: <CALQ0xCBjxQWUfcdKy_tU9Ee=O0TXd0NOyNivYqbeq1rQKg_Ehg@mail.gmail.com>

Marc,

the first I.T. Recession in Australia occurred in 1991.
It was the first economic recession where corporates couldn’t easily save money by “automating” - all the low-hanging fruit - like Inventory, Payroll & Accounting - had been computerised, at least by companies that’d survive.

Thanks for mentioning the IBM OCO - I’d left mainframe by then.

Your insight about the ’social contract’ ring true - never heard that before.
Since that first recession, the regard managers have for I.T. / Computing staff - embodied in wages & conditions - has declined markedly outside business where software & systems are their business.
The hype and over-expenditure on Y2K, then the Dot Crash, resulted in a 5 year I.T. recession in Australia - and a very jaded attitude towards I.T. and their budgets within the Corporates I know.

The deskilling and mediocre work of programmers and support staff alike doesn’t seem to improve whole-of-enterprise productivity.

Your summation of the Professional response to the dissolution of the ’social contract’ is very insightful. Explains the rapid rise and proliferation of OSS in the 1990’s.

stevej

> On 7 Sep 2022, at 02:09, Marc Donner <marc.donner@gmail.com> wrote:
> 
> By the mid-1980s the Microsoft folks established the notion that software was economically valuable.  People stopped giving away source code (IBM's change in strategy was called OCO - "Object Code Only") and it totally shocked the software developer community by destroying the jobs for programmers at user sites.  Combine that with the mid-1980s recession and the first layoffs that programmers had ever seen and we saw the first horrified realization that the social contract between programmers and employers did not actually exist.
> 
> We, the programmer community, woke up and committed ourselves as much as ever we could to non-proprietary languages and tools, putting our shoulders to the OSS movement and hence to UNIX and the layer of tools built on top of it.
> 

--
Steve Jenkin, IT Systems and Design 
0412 786 915 (+61 412 786 915)
PO Box 38, Kippax ACT 2615, AUSTRALIA

mailto:sjenkin@canb.auug.org.au http://members.tip.net.au/~sjenkin


  reply	other threads:[~2022-09-07  4:01 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 23:48 [TUHS] " steve jenkin
2022-09-06 16:09 ` [TUHS] " Marc Donner
2022-09-07  4:00   ` steve jenkin [this message]
2022-09-07 14:58     ` John Cowan
2022-09-07 17:13     ` Paul Winalski
2022-09-08 14:12       ` Paul Winalski
2022-09-07  5:15   ` steve jenkin
2022-09-07 13:20     ` Dan Cross
2022-09-07 13:52       ` Steve Nickolas
2022-09-07 12:53 ` [TUHS] STDIN/OUT vs APIs [was: How Unix changed Software] Brian Zick
2022-09-07 13:19   ` [TUHS] " John Cowan
2022-09-07 15:39     ` Joe
2022-09-07 15:43       ` John Cowan
2022-09-07 16:01         ` Charles H Sauer (he/him)
2022-09-06 15:07 [TUHS] Re: Has this been discussed on-list? How Unix changed Software Douglas McIlroy
2022-09-06 17:13 ` Larry McVoy
2022-09-07  1:40 ` steve jenkin
2022-09-07  2:33   ` segaloco via TUHS
2022-09-07  4:08     ` Steve Jenkin
2022-09-07 13:08   ` Steffen Nurpmeso
2022-09-07 14:56   ` Larry McVoy
2022-09-07 21:27     ` Steve Jenkin
2022-09-07 22:36       ` Larry McVoy
2022-09-08 14:42       ` Paul Winalski
2022-09-08 15:02         ` Larry McVoy
2022-09-08 15:04         ` ron minnich
2022-09-08 15:52           ` Warner Losh
2022-09-08 16:47             ` Paul Winalski
2022-09-08 16:50             ` segaloco via TUHS
2022-09-08 17:58               ` ron minnich
2022-09-06 19:04 Douglas McIlroy

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=E0DE5E28-2F17-47FE-83CE-ED8D9407D8A0@canb.auug.org.au \
    --to=sjenkin@canb.auug.org.au \
    --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).