From: edgar@openmail.cc
To: help-gnu-emacs@gnu.org
Subject: Re: General advice beyond Org
Date: Sun, 20 May 2018 19:29:30 +0000 [thread overview]
Message-ID: <3670f5d10c3f80646994f515711f0a30@openmail.cc> (raw)
In-Reply-To: <mailman.15.1526832003.3852.help-gnu-emacs@gnu.org>
> Message: 2
> Date: Sat, 19 May 2018 18:31:55 -0400
> From: "James K. Lowden" <jklowden@speakeasy.net>
> To: help-gnu-emacs@gnu.org
> Subject: Re: General advice beyond Org
> Message-ID: <20180519183155.caea7e3c88b046e85a82e888@speakeasy.net>
> Content-Type: text/plain; charset=US-ASCII
>
> On Fri, 18 May 2018 00:28:22 +0000
> edgar@openmail.cc wrote:
>
>> _I_ need help. I am in graduate school, and I keep having issues with
>> my advisor for my strong inclination to use free software. I am
>> obviously not in position to refuse, but she dislikes to have
>> discussions about it. She pays a stipend to me every month, and my
>> tuition is waved.
>
> Question #1: How important is your strong inclination, measured in
> dollars? Because we all have to go along to get along, to some extent.
American, Canadian, Australian... dollars? :D . I don't like to measure
myself in currency. It is as if turning into a product. I guess that you
mean how much I am willing to give up for my inclination, which is a
good question.
> Every place I've ever worked used at least some proprietary software.
> Every place had the need to exchange modifiable files. The desire to
> move from Windows to, say, Qt was nil.
This reminds me of the comment from Gene:
> Date: Fri, 18 May 2018 16:27:12 -0700 (PDT)
>> Do you have any idea how many in positions of authority to constrain
>> your freedom of choise OWN Monopoly$oft stock and have no qualms about
>> misusing their positions of authority to specify proprietary products
>> which benifit them as stock holders?!
>>
>> Don't EVEN go there!
But it is good to know that I will face this.
> The need to share information trumps concerns about software licensing
> every time. The need to keep using what you know trumps touted
> features of what you'd have to learn. If you don't believe me, ask
> someone whose department switched to Git from Subversion.
Golly! I still remember all the time that I had to devote to partially
use Emacs correctly, having used many others in the past! I would not go
back!
> Your advisor is only the tip of the iceberg. Really, she's a messenger
> from the real world, a place where you'll have to learn to use software
> you don't like, and deal with many other contraints and impositions on
> your freedom to get the job done. All organizations have rules, after
> all, by definition.
> If you're trying to defend your ideals, it might help to remember you
> can't, because everything is connected to everything else.
The first part of this statement is very daunting, depressing and grim.
> During the Vietnam war, it wasn't uncommon for someone to declare their
> opposition to the war meant they refused to work for a defense
> contractor. OK. Banking, then? But banks finance defense
> contractors. McDonalds? They feed defense contractor employees.
> Academia? You're training new defense contractors. No matter how you
> earn your bread, your employer and your earnings eventually feed the
> same maw.
Oh! war! thou creator of all!
> If you're just trying to pamper your fingers, it might help to remember
> you can. To the extent others are unaffected, you'll usually be free
> to choose what software to use. That will be more true in technical
> and scientific areas, and less true in business and administrative
> ones.
I don't know what "pamper your fingers" mean, but I think that the
message is the comparison between technical and scientific v.s. business
and administrative.
> How much independence you have depends on how expert you are. If you
> need guidance in how to accomplish a task, any task, you can't expect
> the person helping you to *also* learn your software. Usually help
> comes in the form of "using X do Y", and if you don't have X, you have
> to figure out what X(Y) is. If you know the problem domain and your
> software very well, the route to X(Y) is shorter than if you don't.
May be that is why it is easier in academia? where answers are not
completely clear?
> One last point that's often underappreciated: if you use whatever
> software you're asked/expected to use, then if you have problems or
> delays -- as you certainly will -- you'll have a sympathetic ear. If
> you insist on doing it your own way, others will blame every problem or
> delay, fairly or not, on your choice of software. Before you buck the
> system, it pays to get buy-in or to be very, very sure you'll come out
> ahead.
>
Thanks for the heads up!
> --jkl
-------------------------------------------------
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
next parent reply other threads:[~2018-05-20 19:29 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.15.1526832003.3852.help-gnu-emacs@gnu.org>
2018-05-20 19:29 ` edgar [this message]
2018-05-21 3:39 ` General advice beyond Org Marcin Borkowski
[not found] ` <mailman.148.1526874026.1292.help-gnu-emacs@gnu.org>
2018-05-21 16:26 ` James K. Lowden
2018-05-21 18:07 ` Bob Newell
2018-05-21 19:23 ` Marcin Borkowski
2018-05-20 19:34 ` Exporting ODT to Org [was Re: General advice beyond Org] edgar
2018-05-21 8:07 ` tomas
[not found] <mailman.893.1527022341.1290.help-gnu-emacs@gnu.org>
2018-05-23 4:23 ` General advice beyond Org edgar
2018-05-23 4:27 ` edgar
2018-05-23 4:30 ` edgar
[not found] <mailman.626.1526915916.1290.help-gnu-emacs@gnu.org>
2018-05-23 4:04 ` edgar
2018-05-26 4:01 ` Marcin Borkowski
2018-05-26 7:08 ` edgar
[not found] <mailman.19.1527004804.3124.help-gnu-emacs@gnu.org>
2018-05-23 3:44 ` edgar
2018-05-23 19:19 ` Stefan Monnier
2018-05-26 4:14 ` Marcin Borkowski
2018-05-26 19:34 ` Stefan Monnier
2018-05-27 6:54 ` Thien-Thi Nguyen
2018-05-27 17:19 ` Stefan Monnier
2018-05-27 18:19 ` Thien-Thi Nguyen
2018-05-28 19:21 ` Stefan Monnier
2018-05-31 9:50 ` Thien-Thi Nguyen
[not found] ` <mailman.1113.1528121846.1292.help-gnu-emacs@gnu.org>
2018-06-04 14:46 ` Emanuel Berg
2018-06-04 14:47 ` Emanuel Berg
2018-05-27 18:32 ` edgar
2018-05-23 3:50 ` edgar
[not found] <mailman.5.1526603344.1292.help-gnu-emacs@gnu.org>
2018-05-18 23:27 ` Gene
2018-05-19 7:06 ` tomas
[not found] ` <mailman.67.1526713619.1292.help-gnu-emacs@gnu.org>
2018-05-27 1:02 ` Gene
2018-05-27 7:27 ` tomas
2018-05-19 22:31 ` James K. Lowden
[not found] <mailman.127.1526629283.1290.help-gnu-emacs@gnu.org>
2018-05-18 8:41 ` edgar
2018-05-21 20:10 ` Eric Abrahamsen
2018-05-22 7:10 ` tomas
2018-05-22 16:58 ` Bob Newell
2018-05-22 18:05 ` Eric Abrahamsen
2018-05-22 19:15 ` tomas
2018-05-18 0:28 edgar
2018-05-18 1:52 ` Peter Neilson
2018-05-18 7:12 ` S. Champailler
2018-05-18 8:10 ` edgar
2018-05-18 8:20 ` tomas
2018-05-18 22:31 ` Stefan Monnier
2018-05-18 8:15 ` tomas
2018-05-18 10:54 ` Yuri Khan
2018-05-18 11:10 ` S. Champailler
2018-05-18 13:50 ` Kevin Buchs
2018-05-18 15:31 ` tomas
2018-05-18 16:19 ` Alan E. Davis
2018-05-18 16:22 ` Alan E. Davis
2018-05-18 16:32 ` Jason Yamada-Hanff
2018-05-18 19:09 ` Devin Prater
2018-05-18 13:50 ` hymie!
2018-05-20 1:24 ` Samuel Wales
2018-05-20 8:08 ` tomas
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=3670f5d10c3f80646994f515711f0a30@openmail.cc \
--to=edgar@openmail.cc \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).