From: Bob Newell <bobnewell@bobnewell.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: [O] General advice beyond Org
Date: Thu, 17 May 2018 16:44:39 -1000 [thread overview]
Message-ID: <CADoYgq9YgBf=qZqVa3554686T=3UuWeGXWQmZ3U6ccBcnmVQ9A@mail.gmail.com> (raw)
In-Reply-To: <op.zi6str12rns8nc@odin>
Aloha,
Sometimes you need to pick your battles.
In a place I once worked at, there were two environments. One was
extremely restrictive and you were only allowed to use specific
products ... so I had to use abominations like Word and Outlook. (In
the other environment, I could do as I wished.) It was otherwise a
good job, and I liked it, so I put up with the rules. It was neither a
battle I could win nor a battle worth fighting.
Was it harder to work without Emacs and the many tools that made me
more productive? Yes. But again, that came with the territory, and I
didn't think it was worth quitting over.
In your case, in grad school, I of course don't know your environment,
or what proprietary tools you're being told to use vs. what FOSS tools
might be available. Certainly things like Scilab, Sage Math, R, etc.
will do a lot, but your needs may be much greater.
If your evaluation (and you need to do a careful evaluation of the
merits and demerits of both your approach and her approach) is that
it's better to go with what your adviser asks, then you should do so.
No, I wouldn't like it either. But I don't think (unlike RMS, perhaps)
that there are show-stopping moral or ethical issues here.
If your evaluation truly tells you that your way is best, then you
need to come up with a plan of action, with alternatives. I'd suggest
that a good enough evaluation could possibly sway your adviser.
Best of luck to you.
next prev parent reply other threads:[~2018-05-18 2:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 0:28 General advice beyond Org edgar
2018-05-18 1:52 ` Peter Neilson
2018-05-18 2:44 ` Bob Newell [this message]
2018-05-18 7:32 ` [O] " tomas
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-19 7:18 ` [O] " Marcin Borkowski
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='CADoYgq9YgBf=qZqVa3554686T=3UuWeGXWQmZ3U6ccBcnmVQ9A@mail.gmail.com' \
--to=bobnewell@bobnewell.net \
--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).