From: arnold@skeeve.com
To: wkt@tuhs.org, scj@yaccman.com
Cc: tuhs@tuhs.org
Subject: [TUHS] Technical decisions based on political considerations [was Re: AT&T Research]
Date: Thu, 23 Jul 2020 00:02:04 -0600 [thread overview]
Message-ID: <202007230602.06N6243i013099@freefriends.org> (raw)
In-Reply-To: <03a8a0a84960ca40be4ea04b5cd1d780@yaccman.com>
scj@yaccman.com wrote:
> The technical people I met all seemed
> competent -- it must be the management that was the difference...
<rant>
I saw this *a lot* when I worked at Intel; being forced to use
the wrong tools for software development because of political
considerations instead of technical ones. One of the reasons I
was super glad to leave there and why I think that Intel as a
whole will never make it as a software company. (There are pockets
there that understand software, but the majority of the company
does not.)
</rant>
Sorry,
Arnold
next prev parent reply other threads:[~2020-07-23 6:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 1:08 [TUHS] AT&T Research John P. Linderman
2020-07-11 1:32 ` Larry McVoy
2020-07-11 1:51 ` John P. Linderman
2020-07-11 15:36 ` Clem Cole
2020-07-11 20:30 ` Warren Toomey
2020-07-11 20:36 ` Jon Steinhart
2020-07-11 21:58 ` Rob Pike
2020-07-11 22:29 ` Larry McVoy
2020-07-12 7:55 ` Ed Bradford
2020-07-12 2:22 ` [TUHS] BTL pranks [was AT&T Research] Doug McIlroy
2020-07-12 11:58 ` [TUHS] Monitoring by loudspeaker (was: BTL pranks) Michael Kjörling
2020-07-12 13:25 ` Dan Cross
2020-07-12 14:58 ` Robert Clausecker
2020-07-12 16:09 ` [TUHS] Monitoring by loudspeaker Al Kossow
2020-07-12 20:10 ` [TUHS] Fwd: " Rich Morin
2020-08-23 8:58 ` [TUHS] " Tom Ivar Helbekkmo via TUHS
2020-07-23 4:13 ` [TUHS] AT&T Research scj
2020-07-23 6:02 ` arnold [this message]
2020-07-23 14:42 ` [TUHS] Technical decisions based on political considerations [was Re: AT&T Research] Larry McVoy
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=202007230602.06N6243i013099@freefriends.org \
--to=arnold@skeeve.com \
--cc=scj@yaccman.com \
--cc=tuhs@tuhs.org \
--cc=wkt@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).