From: Marcin Borkowski <mbork@mbork.pl>
To: tomas@tuxteam.de
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs in a Corporate Environment
Date: Sat, 15 Apr 2023 11:12:53 +0200 [thread overview]
Message-ID: <87fs915x0q.fsf@mbork.pl> (raw)
In-Reply-To: <ZDpS1N5IznvAf+uk@tuxteam.de>
On 2023-04-15, at 09:31, tomas@tuxteam.de wrote:
> On Sat, Apr 15, 2023 at 08:12:55AM +0200, Marcin Borkowski wrote:
>>
>> On 2023-04-14, at 18:11, tomas@tuxteam.de wrote:
>
> [...]
>
>> > Anyway: my employers so far have decided that they can trust
>> > my judgement wrt data security, thanks $DEITY.
>>
>> That's of course a pleasant experience, but I still think this
>> discussion is worthwhile.
>
> For sure, and I am glad for that. Still, it's a bit jarring to me
> what people are willing to accept without complaints because it
> comes from $EMPLOYER. Did it come from the state, they'd all be
> yelling dictatorship (with a reason). Why does an employer get a
> free pass on that?
Good point. I often think that slaves in antiquity, peasants in the
Middle Ages (which were much more civilized times than most people think
- in fact, it may be the case that the so-called "Middle Ages" were the
golden age of our civilization, and we have only declined since then, at
least in moral and political terms) and employees today are in a very
much similar position. And quite possibly it was even better to be
a peasant 600 years ago than a corporate employee today.
> I mean: sometimes you have no choice if you want to go buy bread,
> but rationalising that behaviour goes too far for my taste.
You might be right, but I would be very cautious with judgements in
individual cases. (But you know that already, of course.)
>> Also, I've seen e.g. reckless developers enamored by ChatGPT and
>> similar, LLM-based tools, happily providing company information to
>> them...
>
> Yes: trust in your employees is an investment: as an employer you
> have to put resources into education and into building a trust
> relationship. But it pays off handsomely.
Agreed.
> If, as an employer, you insist into treating your employees as a
> disposable resource, you'll get every data leak you deserve.
Agreed, too.
Best,
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2023-04-15 9:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 19:48 Emacs in a Corporate Environment Yuan Cao
2023-04-12 20:10 ` Corwin Brust
2023-04-12 20:48 ` John Yates
2023-04-12 21:33 ` Yuan Cao
2023-04-13 0:08 ` Corwin Brust
2023-04-13 14:35 ` Marcin Borkowski
2023-04-14 14:36 ` Michael Albinus
2023-04-14 14:52 ` Eli Zaretskii
2023-04-14 15:08 ` Óscar Fuentes
2023-04-14 15:47 ` Eli Zaretskii
2023-04-14 16:11 ` tomas
2023-04-15 6:12 ` Marcin Borkowski
2023-04-15 7:31 ` tomas
2023-04-15 9:12 ` Marcin Borkowski [this message]
2023-04-15 6:11 ` Marcin Borkowski
2023-04-15 7:17 ` Eli Zaretskii
2023-04-15 7:34 ` tomas
2023-04-15 7:59 ` Eli Zaretskii
2023-04-15 8:21 ` tomas
2023-04-15 9:41 ` Eli Zaretskii
2023-04-15 11:16 ` Po Lu
2023-04-15 12:04 ` Marcin Borkowski
2023-04-15 12:18 ` Ruijie Yu via Users list for the GNU Emacs text editor
2023-04-15 13:22 ` tomas
2023-04-15 18:45 ` Michael Albinus
2023-04-15 6:10 ` Marcin Borkowski
2023-04-15 21:14 ` Björn Bidar
2023-04-16 7:51 ` Michael Albinus
2023-04-13 14:23 ` Marcin Borkowski
2023-04-13 17:23 ` Yuan Cao
2023-04-12 20:52 ` Jean Louis
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fs915x0q.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=help-gnu-emacs@gnu.org \
--cc=tomas@tuxteam.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).