4 ms·
> IBM uses special and completely unintuitive names for basic concepts…. because OF COURSE THEY DO. As I recall, it's called "Bluespeak", and that sort of thin
by AnIdiotOnTheNet 8y ago
> IBM uses special and completely unintuitive names for basic concepts…. because OF COURSE THEY DO.
As I recall, it's called "Bluespeak", and that sort of thing is pretty common actually. I was educated in networking at a Cisco netacad, so I use Cisco terminology that is apparently not universal.
Programming languages do this too for some reason: Sum type, tagged union, discriminated union, variant...
- jacoblambda 8y agoI would argue with programming languages that it's less bluespeak-esque and rather that they have a more or less one-to-one relation with the mathematical principles they are based on. Often programming features end up with a math name (matching the element they are based on) and a developer friendly name which in some ways makes life easier (by separating high/low level discussions) and more confusing (everything now has different names which get used based on author/speaker preference).
- JdeBP 8y agoThe point that M. Bellotti came close to, but missed, is that "of course they do" is because every field has jargon. The error here is in thinking that one set of jargon is intuitive and normal whilst another set of jargon is "special and completely unintuitive". The simple truth is that there are many people to whom jargon such as "WIMP", "ISOs", "flat UI", "IIFE", "DOM", "pull request", and "UX" is equally as opaque and foreign as "DASD", "APAR", "SRC", "PMR", and "PTF" (http://jdebp.info./FGA/fix-terminology.html http://jdebp.info./FGA/fix-terminology.html). All are in fact niche terminology.
- exolymph 8y agoI recently started learning more about git in order to use GitHub for work. I can confirm that "pull request" makes no sense whatsoever before you have a working mental model of git (even now, I don't think I could adequately explain it to someone else).
- southern_cross 8y agoIIRC, as the story goes the folks who designed IBM's SNA (Systems Network Architecture) went out of their way in order to come up with a whole new set of technical jargon for that. I don't remember why, though. BTW, I've been around long enough to have had conversations like the following: Them: "I want to run Lotus 1-2-3." (This was the near-universal spreadsheet standard before Microsoft Excel came along.) Me: "OK, then first we're going to have to get you a PC." Them: "What's a PC?" Then I would have to explain that this was a "Personal Computer". And not just any personal computer, either, but rather an "IBM" PC, in order to distinguish it from an Apple or Commodore or TRS-80 or TI-99/4A or Atari or whatever. And they might respond that they didn't even know that IBM made personal computers. (Which they don't any longer, of course.)
- teh_klev 8y ago> IBM uses special and completely unintuitive names for basic concepts Once upon a time I worked as a (young) field engineer looking after mostly Intel based kit, peripherals and Novell/Windows/Unix OS support. Our company was subcontracted to look after a bunch of Perle controllers for another maintenance company that didn't have engineering staff locally (these were on two and four hour onsite must-fix contracts). Perle manufactured a range of clones of IBM's 5294/5394/5494 Twinax remote access controllers that you plugged stuff like 5250 series terminals and printers into. Anyway, I had to go on a training to course to learn about the gear, usual faults etc. But I also had to learn the IBM lingo such as asking the remote ops folks to "VARY ON" and "VARY OFF" (i.e. enable/disable) controllers when working on them. There were other, now long forgotten, incantations you needed to utter over the phone to IBM ops folks when on site, but the VARY ON/OFF one stuck with me. As an aside, I also ended up looking after and field repairing a bunch of System/36's[0], in particular replacing hard disks which looked like: http://www.corestore.org/5360-13.jpg http://www.corestore.org/5360-13.jpg Amazingly a sole engineer could carry out this task in about 30-40 minutes with no need for extra hands. These were well thought out and designed workhorses. [0]: http://www.corestore.org/36.htm http://www.corestore.org/36.htm
- southern_cross 8y agoDon't feel too bad. As a decades-long user of IBM gear, on and off, the VARY terminology has always struck me as quite odd, too.
- krylon 8y agoI like that the kernel is called "nucleus". It's like parallel evolution, many concepts are the same, but they developed independently, so the naming is different. I did not mind the names, at the time I had plenty of old mainframe hands around, who were actually happy I showed such an interest in their work, so they gladly took their time to answer any and all questions I had. Fun times... :-)
- JdeBP 8y agoThe names "kernel" and "nucleus" are not in fact different, let alone different concepts. "Control Program" is by far the more different name in this regard. * https://superuser.com/a/329479/38062 https://superuser.com/a/329479/38062
- 394549 8y ago>> IBM uses special and completely unintuitive names for basic concepts…. because OF COURSE THEY DO. > As I recall, it's called "Bluespeak", and that sort of thing is pretty common actually. How much of that is because they invented terms for these concepts before our current terms were coined or became ubiquitous? It might be easy to forget, but IBM was once at the cutting edge of computing. They coined terms, others coined rival terms, and it wasn't at all clear whose terms would be ubiquitous in 2018. IBM changing to adopt another computing culture's terms would be akin to metrification: expensive, short term pain to abandon a good-enough system to achieve distant long-term benefits.