Poka-Yoke
21–30 of 48 posts
Re: Poka-Yoke
#22I like collecting little ideas like this. Slightly meta-ironically I'd describe the genre as "just abstract enough to be useful nuggets of knowledge" and I have an org file full of them. The hard part is I don't know any better name for such "concepts" so I can't search for other people's lists. Does anyone else keep a similar collect or have advice for finding more? (For example Gurwinder sometimes posts lists like…
"Epistemological atom" is bulky. Some are principles, some are laws, some are aphorisms, some are patterns. Sometimes you see "nuggets" or "pearls of wisdom". The publishing industry tries to froth these ideas into $25 nonfiction hardbacks, 15 minute TED talks, and hour long podcast appearances, but they are without obvious exception small ideas.
"meme" as analogous to gene might have taken root in some alternate timeline. I think one of the characteristics that makes certain ideas compelling in this way is that they seem to be applicable in ways far beyond their origin (cf. design patterns). That's why they feel collectable.
I liked the term "knol" for a "unit of knowledge" from when Google tried to do a wikipedia like thing. There is definitely a shape and scope relatable to a wiki page. The idea should feel unique and complete enough to have its own wiki page but dense enough to fit in the summary.
Re: Poka-Yoke
#23In my industry, we mostly use the term to refer to mechanical features, typically keyways, that prevent connectors from being mated incorrectly. Suppose you have a module with 50 pins worth of connectors, but because some of the signals are in different harnesses which get installed at different times, you can't just use a 50-pin connector. For this example let's say it's sensible to break it up as 20+20+10. You woul…
Re: Poka-Yoke
#24In my industry, we mostly use the term to refer to mechanical features, typically keyways, that prevent connectors from being mated incorrectly. Suppose you have a module with 50 pins worth of connectors, but because some of the signals are in different harnesses which get installed at different times, you can't just use a 50-pin connector. For this example let's say it's sensible to break it up as 20+20+10. You woul…
Re: Poka-Yoke
#25Re: Poka-Yoke
#26"Yoke" is pronounced like "yo K", not like the control wheel of an aircraft. (Then again, seeing how nobody pronounces Pokémon as Pokémon, I guess striving for accurate pronunciation is a lost cause)
"Yoh kay" as in "show slay" Or "yoh keh" as in "moth fret" ? I pronounce pokémon as "Poh Key Mon". Which is a third variation to "ké"
Japanese vowels can vary quite a lot, because there aren't nearly as many other vowels to confuse them with as there are in English.
The Japanese "o" vowel is usually close to [ɔ], the General American English CLOTH vowel (from Wikipedia: "cough, broth, cross, long, Boston", or "moth") or THOUGHT in either GA or British Received Pronunciation ("taught, sauce, hawk, jaw, broad") than to GOAT in either dialect ("soap, joke, home, know, so, roll", or "show").
The Japanese "e" vowel is usually close to [ɛ], which is the General American English DRESS vowel (from Wikipedia: "step, neck, edge, shelf, friend, ready", to which we might add "fret") than to [e] or [ej] or [eɪ] or [ei], which is more like the General American English FACE vowel ("tape, cake, raid, veil, steak, day", to which we might add "slay"). RP doesn't have [ɛ] at all; the closest it has is that it realizes SQUARE ("care, fair, pear, where, scarce, vary") as [ɛə].
Other English dialects (AAVE, Irish, Scottish, Cajun, Southern American, Jamaican, Standard Indian, Bangladeshi, Nigerian, Australian) realize these vowels in their own different ways which may or may not correspond well to the Japanese phonemes you're asking about.
Re: Poka-Yoke
#27Also known as "eliminating the fail state" or "rendering invalid states unrepresentable". Unfortunately, also very attractive to being used corruptly in the political arena (see nudge theory, newspeak). Can also be downright rejected, bypassed, or ignored. See most workers/employers views on OSHA.
At my job, I add automations to try to avoid problematic and common errors. But I also engineer them so that a human can override them in the event of an emergency or some other need
Re: Poka-Yoke
#28In my industry, we mostly use the term to refer to mechanical features, typically keyways, that prevent connectors from being mated incorrectly. Suppose you have a module with 50 pins worth of connectors, but because some of the signals are in different harnesses which get installed at different times, you can't just use a 50-pin connector. For this example let's say it's sensible to break it up as 20+20+10. You woul…
When I was designing boards, we had 1-2 standard types of connector we were allowed use, that had an even number of pins. So we would use a different number of pins for each connector on the board, even if some of the pins were not used. It looked kind of silly to see 4 wires in a 12 pin connector but it was better then getting them mixed up.
I'll try to plan uses for all the pins in advance, like a deluxe version, and then cut down what's needed for the thing I'm doing now. Often I can actually add something useful (like an extra copy of a signal to reduce the need to splice in the harness) at no cost, just by thinking ahead a little.
Another thing I'm proud of recently, is having an uncommitted relay on a board, whose function could then be defined by how the harness was wired. Rather than try to anticipate how it would be used, I just figured it'd be handy. Provided an extra ground too, so you could just put a hairpin wire in the connector to ground one side of the relay since that's a pretty common usage model. And for builds where we knew we wouldn't use it, just DNP at assembly time.