The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Calculus; actually, all forms of mathematics above trigonometry, except for matrix algebra which I've used. All of the engineering applications of that math - linear systems and the like.
As far as software subjects go, there've been quite a few things I've learned which I haven't used in a long time. Out of that list, however, I can't think of a single thing which I learned and then never used. The closest candidate would probably be assembly language for PIC microcontrollers, which I learned well enough for a two month-long project a few years ago.
When I started in the industry, there were only six recognised programming languages (ALGOL, Assembler, Basic, Fortran, COBOL and RPG). I learned all six, but RPG was the only language I never used. Nowadays, I can program in 2934 computer languages. (If you know the basic six, you know the rest.)
What did you learn and never get around to using or, in fact, ever need to use?
Nothing, I used everything I learned and the "good" jobs always required a little more to make the job challenging instead of boring.
However, there are skills I haven't had to use in some time, but I'm sure they'd come back quickly.
In fact, there have been some that my arcane knowledge has been a boon. For instance, one company I worked at required a specialized printer to be able to print barcodes using ESC sequences. To everyone else, ESC sequences were total FM (Field Magic is the polite decode of that). So being of the vintage that I used to need to use ESC sequences to print Bold and Italic on my Epson MX-100 14" wide carriage dot-matrix printer, the task was a snap. For years they kept coming back to me to modify the program because no one else at the company had a clue.
Other skills languishing are Assembly coding, spooler writing, communications packages, real time controls, the list is extensive.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
Talking at the dinner table or at the pub. Nowadays you can see a load of people sitting in a circle messing with their phones. They just sit together but nobody talks anymore. I've seen a family of 4 go out for a meal. They are messing with their phones before the meal, during the meal and after the meal. They've actually forgotten the skill of verbal communication.
A bit de-mob happy, it sounds like one of our customers is see some odd behaviour. Which would be my thing to sort out but it looks like I'm not going to get to fix it! (Yayy! it generally involves the scary temperature box)
Depends on the chip. Some read -5V as 0 and +5V as 1. Some are tri-state using -5V, 0, and +5V. It's actually voltage and not current that it is using. At least the chips I worked with years ago were that way.
[Edit] And yes, some chips used 0V as 0 and +5 as 1. [/Edit]
There are only 10 types of people in the world, those who understand binary and those who don't.
in many case three state of currency doesn't mean three state of logic.
The -5 / 0 / +5 differentiation is used just for electrical reason.
If use 0 / +5 you can have a sort of eco in the signal wich transform it self into noise.
With negative voltage there is a resorption of this eco but the chipset will not see the zero.
Practically is -5 for false and +5 for true
Yeah, it's technically possible, but indeterminate boolean values make my skin crawl. They aren't even boolean, really.
Keith Barrow wrote:
You've probably already used this without realising, nullable bit fields in SQL work along ternary logic lines.
And this is exactly why I hate them. You can have nullable bit fields, but you can also hit the server with a hammer, that doesn't make it a good idea. I'm sure there are some cases out there where this is useful, but I've only found it to be problematic. Every time I find nullable bit fields in a database, it's an issue that needs fixing rather than some clever use of three-state logic. If you need more than two values, why even use a bit field for that? Integers will do fine, and you won't have to deal with nulls.
Keith Barrow wrote:
In formal logic there is also ternary logic, in one scheme:
0: Unknown/ Indeterminate
Yeah, but in general classical logics don't allow indeterminate values. True, false, or GTFO.