I agree with you John and Mark, I always ask from what viewpoint is the author writing and what experience. One could every possible degree and still not understand what 'many of us do'. I run into this on a regular basis. I have seen the 'shooting down of ideas' at meetings before. Once has to be realistic about the environment and whats possible and or doable.
Regards, Scott On Mon, Mar 23, 2015 at 10:39 AM, John McKown <[email protected]> wrote: > On Mon, Mar 23, 2015 at 9:12 AM, Mark Regan > <[email protected]> wrote: > > I saw this URL posted to one of our internal blogs: > > > https://kateheddleston.com/blog/how-our-engineering-environments-are-killing-diversity-introduction > Thanks, > > > > > > Mark Regan > > USNR-Ret. [1969-1991, CTO1] > > K8MTR > > > > <>< > > some good points. I do have a few points that I would discuss with the > author. Such as lumping "meritocracy" in with "aggressiveness" and > "long work hours". Or the implied, if not directly stated, objection > to "shooting down" a "stupid idea" in a meeting. Perhaps she meant > that the person should be talked to privately. But if something is > "stupid" (not that I use "stupid" in a meeting), then it needs to be > "shot down". E.g. TSO is a resource hog, so let's write all our > programs on Windows, then submit the jobs to z/OS using ftp, then get > the output back via ftp and look at it on Windows. No, I've never > heard of anybody doing this. But I do know of a shop, long ago, which > ran MVS, kept all the source in Panvalet, and the programmers > submitted jobs _on cards_ via a RJE card reader. Getting output back > on the RJE printer. Why? Just for the reason I gave: TSO was > considered too resource intensive. I don't know why not Roscoe or > Wylbur. > > -- > If you sent twitter messages while exploring, are you on a textpedition? > > He's about as useful as a wax frying pan. > > 10 to the 12th power microphones = 1 Megaphone > > Maranatha! <>< > John McKown > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
