• interviewing

    From RichD@21:1/5 to All on Wed Apr 13 13:02:45 2022
    When you interview job candidates, you pose standard
    problems, of circuits, PSpice, maybe Mathcad, etc.
    Textbook stuff, you expect he knows, reviewing his resume.

    Microsoft and Google are famous for posing brain twisters,
    stuff "outside the book" (if any exists, nowadays with the net).
    Do you do this? The obvious idea is to test for originality.
    How much weight do you place on the responses?

    --
    Rich

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Grant Taylor@21:1/5 to Don Y on Wed Apr 13 16:15:45 2022
    On 4/13/22 3:32 PM, Don Y wrote:
    "Originality" doesn't necessarily equate with competency.

    I completely agree. I'm not looking for anything original by any
    stretch of the imagination.

    I am looking for something that causes the candidate to think for a few
    minutes so that they can demonstrate their understanding of the problem,
    how to possibly solve the problem, and what solution they come up with.

    I don't even /require/ that the candidate have a fully fleshed out
    solution. Especially if they don't because of an artificial time
    constraint. If the candidate can demonstrate that they understand the
    problem, can come up with a solution, and produce work towards the
    solution, then they will get at least /some/ credit for the question.



    --
    Grant. . . .
    unix || die

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to RichD on Wed Apr 13 14:32:02 2022
    On 4/13/2022 1:02 PM, RichD wrote:
    When you interview job candidates, you pose standard
    problems, of circuits, PSpice, maybe Mathcad, etc.
    Textbook stuff, you expect he knows, reviewing his resume.

    Microsoft and Google are famous for posing brain twisters,
    stuff "outside the book" (if any exists, nowadays with the net).
    Do you do this? The obvious idea is to test for originality.
    How much weight do you place on the responses?

    We "test" to see how well the candidate can explore the problem
    space. Folks who rush to a solution often miss on identifying
    important (or "valuable") criteria/flexibility in their solutions.

    "Originality" doesn't necessarily equate with competency.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dave Platt@21:1/5 to blockedofcourse@foo.invalid on Wed Apr 13 16:04:55 2022
    In article <t37fgn$f62$1@dont-email.me>,
    Don Y <blockedofcourse@foo.invalid> wrote:
    On 4/13/2022 1:02 PM, RichD wrote:
    When you interview job candidates, you pose standard
    problems, of circuits, PSpice, maybe Mathcad, etc.
    Textbook stuff, you expect he knows, reviewing his resume.

    Microsoft and Google are famous for posing brain twisters,
    stuff "outside the book" (if any exists, nowadays with the net).
    Do you do this? The obvious idea is to test for originality.
    How much weight do you place on the responses?

    We "test" to see how well the candidate can explore the problem
    space. Folks who rush to a solution often miss on identifying
    important (or "valuable") criteria/flexibility in their solutions.

    +1

    When I do these sorts of interviews, I'm not (usually) looking for domain-specific knowledge. Rather, I'm looking for overall problem-
    solving skills - and a big part of that is "problem _defining_
    skills".

    A very important first step (for the interviewee) is to make certain
    that they understand the problem. What's being asked for? What are
    the requirements? What is must-have vs. nice-to-have? What are the
    must-not?

    Somebody who can "read back" the problem as-stated (in their own words
    and interpretation) and show that they understand what was asked for,
    gets points... "active listening" skills like this are a real asset.
    [I credit my wife for teaching me how important this is, and how it's
    done - she's a graduate psychotherapist and this sort of skill is
    critically important in her work.]

    Someone who can pick up on ambiguities in the requirements and asks
    for clarification gets points. Someone who states what they're
    assuming (and says "correct me if I'm wrong here") gets points.
    Someone who lets me know where their personal expertise and skills can
    cover, and where these end ("I'm on new ground and thin ice here")
    gets points.

    Somebody who jumps in immediately to a proposed solution, without
    doing the above... not so much. That's fairly common and foregivable
    in rather-junior people (who want to show what they know) but I
    don't care to see it in someone at the senior-designer level. It's
    too easy (and expensive) for a project to get off-track due to
    incorrect assumptions... the more senior the eager-beaver, the more
    of the project that can be misdirected.

    I don't go in for "brain teasers" or trick questions... those don't
    necessarily correlate well to real engineering problem-solving.
    Rather, I try to probe with real engineering problems which are
    outside of the candidate's specific work experience and direct skill
    set, but where there's a similar level of general technical expertise
    and problem-solving ability required. I don't expect people to come
    to a working solution in cases like these (although it's nice to see
    it happen), but I want to see how they build their logical framework
    to support a design.

    Google _was_ notorious for brain-teaser problems, years ago, but I
    understand that this approach is deprecated there nowadays.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dennis@21:1/5 to All on Wed Apr 13 18:27:11 2022
    I completely agree.  I'm not looking for anything original by any
    stretch of the imagination.

    I am looking for something that causes the candidate to think for a few minutes so that they can demonstrate their understanding of the problem,
    how to possibly solve the problem, and what solution they come up with.

    I don't even /require/ that the candidate have a fully fleshed out solution.  Especially if they don't because of an artificial time constraint.  If the candidate can demonstrate that they understand the problem, can come up with a solution, and produce work towards the
    solution, then they will get at least /some/ credit for the question.


    I had a friend that years ago had a job interview with one of the
    minicomputer manufactures. At that time they still sent source code with
    the systems and he would go over it - particularly when there seemed to
    be problems. At the end of the interview with the operating system
    manager he was asked if he had any questions. He said yes - he couldn't understand a particular part of the OS and thought it was a problem.
    They talked a bit more. The manager had one of the programmers bring in
    the source code. The manager and programmer looked at the code a bit and
    then told my friend that there was a problem and they would have to fix
    it. He accepted the job offer.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Dennis on Wed Apr 13 17:35:31 2022
    On 4/13/2022 4:27 PM, Dennis wrote:
    I had a friend that years ago had a job interview with one of the minicomputer
    manufactures. At that time they still sent source code with the systems and he
    would go over it - particularly when there seemed to be problems. At the end of
    the interview with the operating system manager he was asked if he had any questions. He said yes - he couldn't understand a particular part of the OS and
    thought it was a problem. They talked a bit more. The manager had one of the programmers bring in the source code. The manager and programmer looked at the
    code a bit and then told my friend that there was a problem and they would have
    to fix it. He accepted the job offer.

    I was looking at a consulting gig many years ago -- for an "electronic door lock system" (think hotels, etc.).

    I was given a brief tour of the facility which ended at their prototype
    of the system (a sample door, with lock, and the "front desk" equipment
    that manages the "keys").

    I was given a brief/cursory demo and asked if I could "play" with it.
    I stepped up to the console and selected "Grand Master" (each key exists
    on several levels -- so the maintenance guy can have access to all of
    the rooms in building A, the maid have access to the rooms on the first
    floor, the guest have access to THIS room, etc.).

    I was very deliberate in making sure my host could see what I was doing.
    (He was very encouraging, thinking I had never seen the system before now.)

    I then reached over and unplugged a cable -- which got a bit of a reaction
    from my host. Then, proceeded to make 3 "Grand Master" keys. Then, reconnected the cable and hit "Cancel Operation". Then, let my host
    notice that the system had no record of the three FUNCTIONAL keys -- that
    I handed to him!

    Ooops!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Dave Platt on Wed Apr 13 17:38:29 2022
    On 4/13/2022 4:04 PM, Dave Platt wrote:
    In article <t37fgn$f62$1@dont-email.me>,
    Don Y <blockedofcourse@foo.invalid> wrote:

    We "test" to see how well the candidate can explore the problem
    space. Folks who rush to a solution often miss on identifying
    important (or "valuable") criteria/flexibility in their solutions.

    +1

    When I do these sorts of interviews, I'm not (usually) looking for domain-specific knowledge.

    Exactly. Most of the projects/industries with which I've been
    involved were "atypical" and most of the added value came NOT
    from how well you could design a circuit, build a mechanism
    or code an algorithm but, rather, from how well you could "grok"
    the actual application domain.

    Rather, I'm looking for overall problem-
    solving skills - and a big part of that is "problem _defining_
    skills".

    Yes.

    A very important first step (for the interviewee) is to make certain
    that they understand the problem. What's being asked for? What are
    the requirements? What is must-have vs. nice-to-have? What are the must-not?

    More importantly, what *assumptions* is the "problem presenter"
    not voicing (and, possibly not AWARE of!) as well as what assumptions
    will the "problem solver" *bake* into his solution -- that might not
    be merited or might LIMIT the solutions he can envision.

    Somebody who can "read back" the problem as-stated (in their own words
    and interpretation) and show that they understand what was asked for,
    gets points... "active listening" skills like this are a real asset.
    [I credit my wife for teaching me how important this is, and how it's
    done - she's a graduate psychotherapist and this sort of skill is
    critically important in her work.]

    Someone who can pick up on ambiguities in the requirements and asks
    for clarification gets points. Someone who states what they're
    assuming (and says "correct me if I'm wrong here") gets points.

    But, there are issues that go beyond simple assumptions.

    "What are your SIZE constraints?" etc.

    "Does the solution have to be ELECTRONIC?"

    "Who is gong to be using this?"

    "What is the expected lifespan of the <whatever>?"

    Someone who lets me know where their personal expertise and skills can
    cover, and where these end ("I'm on new ground and thin ice here")
    gets points.

    AFAICT, the only "past experience" that has ever been useful is their *process*. You've likely never designed (nor imagined!) one of <these>...

    A group with which I am affiliated has a ~50K sq ft warehouse. The
    "inventory" changes, RADICALLY, from week to week. One week it may
    have thousands of computers... the next, hundreds of hospital beds
    (occupying the space that the computers had occupied previously).

    Keeping track of this inventory is tedious because it is so varied.
    And, because they rely heavily on volunteer labor. There's nothing
    you can use to ensure folks "do the right thing" when you're not
    paying them, etc.

    A guy "solved" this problem with a fancy database and web-based portal.
    Must have been hundreds of hours gathering up the hardware, writing the
    code, etc.

    And, no one used it.

    Because the data entry chore was HUGE. And, getting someone to
    VOLUNTEER their time to type in all that crap -- and have someone
    with that "responsibility" available 6 days a week -- just wasn't
    gonna happen. He failed to COMPLETELY understand the problem
    and came up with a solution that *he* could implement and "use"
    (though I notice he didn't volunteer to do all the data entry!)

    Some years later, I came along and said "Why don't we have..."
    "We already *had* a system. No one used it." Yada yada yada.

    I designed a solution where every "thing" ("of interest") was tagged
    with a unique barcode label. I printed sheets of these (self-adhesive)
    in numerical sequence. If 1 -- or 397 -- got lost... <shrug> They
    are just UNIQUE IDENTIFIERS so any one is just as "good" as any other!

    When you "used" a label, you gave it meaning. "37 is the identifier
    for Don Y". "38 is the identifier for this hospital gurney". "39
    is the identifier for room 101". "40 is the shipping manifest for
    the May 2022 Guatemala shipment." etc.

    So, scan the barcode on my "badge" and the system knows "this particular
    wifi barcode scanner is being used by Don Y." (because the definition
    of "item 37" is that of "staff") Scan the barcode on the gurney and the
    system knows Don Y is about to do something with that gurney. Scan the
    barcode on the door to room 101 and the system knows Don Y has stored
    *that* gurney in room 101 (at 12:47PM on April 12th) -- even if the other gurneys are stored in 12 different places!

    If Jerry (identifier 105) moves the gurney to some other room, he
    will undertake similar actions and the system will know the new
    location for *that* gurney (along with who moved it, when, etc.).

    When Don Y wants to gather up all the gurneys to ship to Guatemala,
    the system can tell him where each of them are located (no need for
    them all to be in a common location!). He can type a description *or*
    find a similar item and search for "more of these". He can then "move"
    them to the "shipping manifest" to signify that they will be on a
    truck/boat soon (so, trying to locate them in the warehouse is a
    wasted effort).

    [If he runs out of space in the shipping container, he can scan the
    barcode on the gurney as he removes it and scan the new location to
    "return" it to inventory]

    You can verify your inventory at any time -- just by walking through the facility and scanning an item's barcode, then the location in which it
    is encountered. It's not even an "inventory update MODE"; it's just
    "normal mode of operation"!

    Note that you can *train* someone to use this "user interface" in
    a matter of minutes. So, you don't have to "invest" much training
    in your volunteer staff.

    And, you can get folks who are developmentally disabled to contribute, meaningfully, because they don't have to deal with a keyboard, computer,
    etc. Just "point".

    This isn't significantly different (development effort) than the previous "classical" approach to managing data. You just have to think a bit
    about the UI devices and the *users* who will be employing them! The
    previous solution wasted effort on technology instead of understanding
    the problem space.

    And, the "powers that be" were equally at fault because their assumptions
    (as to WHO would be using this) were so ingrained that they never thought
    to give voice to them! "Hey, make sure Tommy will be able to use whatever
    you put together..."

    [Some years later, I was in a furniture warehouse and saw that they used
    a similar approach to keeping track of where items were located. No need
    to arrange to have all of the "sofas" in aisle 27, "lamps" in aisle 28,
    etc. If you want something, let the machine tell you where to find it;
    relying on some bogus system that makes you feel good that you can commit
    thins to memory is hopelessly outdated!]

    Somebody who jumps in immediately to a proposed solution, without
    doing the above... not so much. That's fairly common and foregivable
    in rather-junior people (who want to show what they know) but I
    don't care to see it in someone at the senior-designer level. It's
    too easy (and expensive) for a project to get off-track due to
    incorrect assumptions... the more senior the eager-beaver, the more
    of the project that can be misdirected.

    Exactly. And, the more "ego" at stake.

    I once asked a colleague who had a considerable role in hiring what
    he thought of the "youngsters". He shrugged -- a *visible* "meh".
    His only comment: "They're FAST!"

    Sure! They don't yet know all the things that they don't yet know! :>
    (i.e., WHY that solution isn't going to work -- even though it seems
    like it *should*. They have to stumble onto the questions that they
    should have asked up front...)

    I don't go in for "brain teasers" or trick questions... those don't necessarily correlate well to real engineering problem-solving.
    Rather, I try to probe with real engineering problems which are
    outside of the candidate's specific work experience and direct skill
    set, but where there's a similar level of general technical expertise
    and problem-solving ability required. I don't expect people to come
    to a working solution in cases like these (although it's nice to see
    it happen), but I want to see how they build their logical framework
    to support a design.

    An interview is a lousy environment to assess a person's skillset.
    The power dynamic is horribly skewed. The interviewer likely has
    preconceived notions of what he wants. The applicant focused on
    getting the offer -- and not whether or not he actually WANTS the
    offer. etc.

    I want to see an applicant that is *interested* in the problem space
    and approaches it in a way that suggests he might have "good discipline"
    in approaching *future* problems (which I can't yet imagine)

    Some firms look for "personality issues" -- especially those that require
    large "team" efforts (lone wolves contraindicated, there). Likewise,
    some require "self starters" -- folks who are resourceful and know how to
    get the resources/supplies that they *might* need.

    Google _was_ notorious for brain-teaser problems, years ago, but I
    understand that this approach is deprecated there nowadays.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rich S@21:1/5 to All on Wed Apr 13 18:44:26 2022
    I havent interviewed in a long while, but my
    simple point is, do they show any passion
    or enthusiasm for the job. That, alone,
    seemed rare. If they asked a lot of on-point
    questions - no matter how naive - that was
    usually a very good indicator,,
    regards, Rich S.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jlarkin@highlandsniptechnology.com@21:1/5 to r_delaney2001@yahoo.com on Wed Apr 13 19:12:56 2022
    On Wed, 13 Apr 2022 13:02:45 -0700 (PDT), RichD
    <r_delaney2001@yahoo.com> wrote:

    When you interview job candidates, you pose standard
    problems, of circuits, PSpice, maybe Mathcad, etc.
    Textbook stuff, you expect he knows, reviewing his resume.

    Microsoft and Google are famous for posing brain twisters,
    stuff "outside the book" (if any exists, nowadays with the net).
    Do you do this? The obvious idea is to test for originality.
    How much weight do you place on the responses?

    We did two Zoom interviews today. We talked about what we do, what
    we're looking for, and asked the guys what they like to do. One was an
    obvious non-fit to all of us; he said it first, so we parted happy.

    The other looks promising, so we'll fly him out and get more serious, whiteboard some circuits and architectures maybe. My interview
    technique is "let's design something together."



    --

    I yam what I yam - Popeye

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Hobbs@21:1/5 to RichD on Wed Apr 13 21:59:43 2022
    RichD wrote:
    When you interview job candidates, you pose standard
    problems, of circuits, PSpice, maybe Mathcad, etc.
    Textbook stuff, you expect he knows, reviewing his resume.

    Microsoft and Google are famous for posing brain twisters,
    stuff "outside the book" (if any exists, nowadays with the net).
    Do you do this? The obvious idea is to test for originality.
    How much weight do you place on the responses?

    --
    Rich


    I interviewed a few folks when I was at IBM, but never did any quiz
    questions.

    BITD I got asked a couple of relatively memorable ones. Interviewing at
    HP Labs in Palo Alto, they asked me to derive the Fresnel formulae for reflection of a plane wave at a dielectric interface.

    I said, "You don't want to sit and watch me go through a bunch of
    algebra, but I'll tell you how the calculation goes", and then explained
    about how phase matching at the boundary gives you the reflected and transmitted k vectors, and the patching conditions for tangential E and perpendicular D (*) give you a 2x2 matrix equation for the transmitted
    and reflected field amplitudes. They were happy.

    The other one was at Tektronix in Beaverton OR. (This was in 1987, when
    at least some of their legendary vertical amp guys were still active.)
    One of them (I think it was Thor Hallen) drew a circuit with a couple of
    PNPs and asked me to figure out what it did.

    The biasing was impossible--there was no way it would do anything
    useful. I said something like, "Well, at AC it would do X, but at DC it
    makes no sense because the biasing is all wrong."

    Turned out it was a ramp generator based on ancient germanium PNPs that
    were so leaky that their base currents went the wrong direction. IIRC
    it was supposed to be able to start up regardless of how leaky they were.

    They weren't expecting anybody to get that in 1987--they just wanted to
    see how folks approached the problem.

    When I interviewed folks at IBM, mostly I asked them to tell me about
    something they'd built, and then we'd discuss it. The ones who were
    excited about showing off their mudpies and could answer fairly probing
    design questions got the Good Housekeeping seal.

    Cheers

    Phil Hobbs


    (*) or equivalently tangential B and perpendicular H.

    --
    Dr Philip C D Hobbs
    Principal Consultant
    ElectroOptical Innovations LLC / Hobbs ElectroOptics
    Optics, Electro-optics, Photonics, Analog Electronics
    Briarcliff Manor NY 10510

    http://electrooptical.net
    http://hobbs-eo.com

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Rich S on Wed Apr 13 20:01:36 2022
    On 4/13/2022 6:44 PM, Rich S wrote:
    I havent interviewed in a long while, but my
    simple point is, do they show any passion
    or enthusiasm for the job. That, alone,
    seemed rare. If they asked a lot of on-point
    questions - no matter how naive - that was
    usually a very good indicator,,

    Agreed.

    "Synthetic" problems are likely not a good indicator
    of how they will approach the *real* "work".

    Like hypotheticals about wombats crossing roadways...
    (unless you're particularly fond of wombats, how much
    are you going to invest in exploring that problem space?)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From boB@21:1/5 to richsulinengineer@gmail.com on Wed Apr 13 20:52:58 2022
    On Wed, 13 Apr 2022 18:44:26 -0700 (PDT), Rich S
    <richsulinengineer@gmail.com> wrote:

    I havent interviewed in a long while, but my
    simple point is, do they show any passion
    or enthusiasm for the job. That, alone,
    seemed rare. If they asked a lot of on-point
    questions - no matter how naive - that was
    usually a very good indicator,,
    regards, Rich S.

    Yes ! Attitude and passion counts a LOT !

    boB

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to RichD on Thu Apr 14 08:51:50 2022
    On 13/04/2022 21:02, RichD wrote:
    When you interview job candidates, you pose standard
    problems, of circuits, PSpice, maybe Mathcad, etc.
    Textbook stuff, you expect he knows, reviewing his resume.

    Microsoft and Google are famous for posing brain twisters,
    stuff "outside the book" (if any exists, nowadays with the net).
    Do you do this? The obvious idea is to test for originality.

    Most regular interviewers have their own favourite pet questions.

    Discussing the right answers online would defeat the object so they
    don't stay useable for long in this age of everything on social media.

    How many zeroes does 100! have in its decimal representation is one such
    that has been popular in recent years.

    How much weight do you place on the responses?

    Watching how they approach an unfamiliar problem can be a sufficient
    guide to do they have what it takes. Engineering can get away with an
    answer that whilst not exactly right is "good enough" for practical
    purposes.

    A pure mathematics course would expect the right answer (and quickly).

    You have to know what characteristics you are recruiting for to pick the
    right test question(s) for the position if you are playing this game.

    Whether the individual will fit in with the team is often much more
    important than technical prowess (provided that is adequate).

    Unless that is you enjoy herding cats (something software engineering management has been compared with - more than our fair share of divas).

    --
    Regards,
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Clive Arthur@21:1/5 to RichD on Thu Apr 14 11:05:51 2022
    On 13/04/2022 21:02, RichD wrote:
    When you interview job candidates, you pose standard
    problems, of circuits, PSpice, maybe Mathcad, etc.
    Textbook stuff, you expect he knows, reviewing his resume.

    Microsoft and Google are famous for posing brain twisters,
    stuff "outside the book" (if any exists, nowadays with the net).
    Do you do this? The obvious idea is to test for originality.
    How much weight do you place on the responses?

    --
    Rich

    For a fairly junior post, probably out of university...

    Non-inverting op-amp circuit with feedback from 10k and 1k divider on
    output with the 1k to ground. What's the gain? Many will say 10.

    Inverting op-amp, 1k input, 10k feedback. What's the gain. Many will
    say 10 instead of -10.

    Make a two input Xor from 2 input Nand gates. Most can do it with 5,
    some with 4.

    Write a bit of generic code to calculate a square root.

    What temperature does solder melt at? This one's interesting, most
    don't know of course, but some can't even make a guess, and even if the
    guess is wildly wrong the reasoning can be good.

    And if they can, bring something along they've done before.

    [I remember the first proper interview I had when I was eighteen. It
    was for a technical job at the BBC and there was an interview panel of
    IIRC four people. They showed me a small PCB and asked me what it was.
    From the 741 op-amp and the fairly large value capacitors I deduced
    that it was probably a low power audio amplifier. Their notes just said "circuit board". They then handed me a resistor which I told them was a
    4k7 5% 1/4 watt resistor (I'd been doing PCB assembly jobs and didn't
    really need to think). Their notes just said "resistor".

    Yes, completely non-technical people interviewing for a technical job.]


    --
    Cheers
    Clive

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jlarkin@highlandsniptechnology.com@21:1/5 to '''newspam'''@nonad.co.uk on Thu Apr 14 07:35:25 2022
    On Thu, 14 Apr 2022 08:51:50 +0100, Martin Brown
    <'''newspam'''@nonad.co.uk> wrote:

    On 13/04/2022 21:02, RichD wrote:
    When you interview job candidates, you pose standard
    problems, of circuits, PSpice, maybe Mathcad, etc.
    Textbook stuff, you expect he knows, reviewing his resume.

    Microsoft and Google are famous for posing brain twisters,
    stuff "outside the book" (if any exists, nowadays with the net).
    Do you do this? The obvious idea is to test for originality.

    Most regular interviewers have their own favourite pet questions.

    Discussing the right answers online would defeat the object so they
    don't stay useable for long in this age of everything on social media.

    How many zeroes does 100! have in its decimal representation is one such
    that has been popular in recent years.

    How much weight do you place on the responses?

    Watching how they approach an unfamiliar problem can be a sufficient
    guide to do they have what it takes. Engineering can get away with an
    answer that whilst not exactly right is "good enough" for practical
    purposes.

    A pure mathematics course would expect the right answer (and quickly).

    You have to know what characteristics you are recruiting for to pick the >right test question(s) for the position if you are playing this game.

    Whether the individual will fit in with the team is often much more
    important than technical prowess (provided that is adequate).

    Unless that is you enjoy herding cats (something software engineering >management has been compared with - more than our fair share of divas).


    Puzzles, especially math puzzles, tell a small part about a person's
    prospect as a design engineer. Puzzles are an easy thing for HR folks
    to use.

    To find out how someone will work with your design team, just do it.



    --

    I yam what I yam - Popeye

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Clive Arthur on Thu Apr 14 09:24:48 2022
    On 4/14/2022 3:05 AM, Clive Arthur wrote:
    And if they can, bring something along they've done before.

    But, this turns the interview around and lets them control the narrative instead of letting you drive it. Unless you have some experience with that product or application domain, you're largely at their mercy (BS factor).

    I've also seen it backfire spectacularly on the applicant! In one
    case, an engineer brought some schematics and source code that "he'd"
    created. As I happened to be very familiar with the product involved,
    he was beyond chagrin when I asked him what part of the project
    "Bob Jackadizzledoo" (bogus name designed to represent the oddness of
    the REAL author's name) had done (Ans: every item that the applicant
    was submitting as "his own").

    Unfortunately, it doubly backfired on the *employer* as I told them of
    this -- as well as placing some "personal calls" to "Bob J" for an off-the-record appraisal of the applicant's past work (something
    that HR can't legally do to the degree that *I* can) -- and they hired
    the guy, anyway.

    [He turned out to be an 18 month disaster! Only quitting when he had
    to "produce" (literally, the day his design was due to be completed)]

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Clive Arthur@21:1/5 to Don Y on Thu Apr 14 23:28:25 2022
    On 14/04/2022 17:24, Don Y wrote:
    On 4/14/2022 3:05 AM, Clive Arthur wrote:
    And if they can, bring something along they've done before.

    But, this turns the interview around and lets them control the narrative instead of letting you drive it.  Unless you have some experience with that product or application domain, you're largely at their mercy (BS factor).

    I've also seen it backfire spectacularly on the applicant!  In one
    case, an engineer brought some schematics and source code that "he'd" created.  As I happened to be very familiar with the product involved,
    he was beyond chagrin when I asked him what part of the project
    "Bob Jackadizzledoo" (bogus name designed to represent the oddness of
    the REAL author's name) had done (Ans:  every item that the applicant
    was submitting as "his own").

    Unfortunately, it doubly backfired on the *employer* as I told them of
    this -- as well as placing some "personal calls" to "Bob J" for an off-the-record appraisal of the applicant's past work (something
    that HR can't legally do to the degree that *I* can) -- and they hired
    the guy, anyway.

    [He turned out to be an 18 month disaster!  Only quitting when he had
    to "produce" (literally, the day his design was due to be completed)]

    I interviewed a guy for a technician/wireman job. He was shy, you might
    say socially inept, but the things he brought along were just lovely.
    Nothing that was going to change the world - for example a variable
    power supply from a magazine design - but just so well put together.

    He got the job. After a few weeks he came out of his shell and was very
    well liked by all. He took pride in his work.

    Sadly, after a few years, Parkinson's got him. RIP Trevor.

    --
    Cheers
    Clive

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Clive Arthur on Thu Apr 14 17:27:25 2022
    On 4/14/2022 3:28 PM, Clive Arthur wrote:
    On 14/04/2022 17:24, Don Y wrote:

    [He turned out to be an 18 month disaster! Only quitting when he had
    to "produce" (literally, the day his design was due to be completed)]

    I interviewed a guy for a technician/wireman job. He was shy, you might say socially inept, but the things he brought along were just lovely. Nothing that
    was going to change the world - for example a variable power supply from a magazine design - but just so well put together.

    I've never seen an applicant bring anything (other than "paper") to an interview. Many show up empty handed. Others with schematics or some
    source code listings, etc.

    Most of the projects/products that I've designed are either too large
    or too expensive to bring along for show-and-tell. Photographs, design documents, etc. have to suffice.

    When I first started on my own, I used to bring "presentations" (talking papers) describing my past projects/products. I quickly learned that was unnecessary -- if someone wanted to talk to me, they'd largely made up
    their mind to hire me (based on a referral).

    So, meeting was more an opportunity to evaluate personalities, etc. (I've
    NOT met many of the clients I've had, over the yeaars!) And, for me, an opportunity to explore their problem to decide if it was something I'd be interested in taking on (I'm always in search of a "new" learning experience; no desire to rehash something I've already done -- that's just "a job"! :> )

    He got the job. After a few weeks he came out of his shell and was very well liked by all. He took pride in his work.

    I've met all kinds. AFAICT, "ability" had very little correlation with other personality factors. But, *process* was a big predicter of success.

    Sadly, after a few years, Parkinson's got him. RIP Trevor.

    Nasty disease. A friend currently battling it. Sadly, largely in denial (e.g., thinking if she changes her diet things will magically get better, etc.)

    ALS is considerably worse. Really hard to watch and know there's damn near nothing you can *do* to help/make it better.

    Both suck in that they are slow marches downhill... tomorrow will be WORSE
    than today... <frown>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rich S@21:1/5 to All on Thu Apr 14 17:51:07 2022

    BITD I got asked a couple of relatively memorable ones. Interviewing at
    HP Labs in Palo Alto, they asked me to derive the Fresnel formulae for reflection of a plane wave at a dielectric interface.


    As to being the interviewee, mine cannot compare to that! ;-)

    The one "extreme" experience; I was handed a multipage
    exam, was like taking my college ACTs all over again.
    It took two hours to complete, involved all kinds of math, physics,
    , written challenges. And picking specs out of their databooks.
    They called it the "Howard Hughes Test"
    I never did figure out why, Did HH grill his candidates that way?

    I must of done OK.. they hired me.
    -=RS

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From RichD@21:1/5 to Clive Arthur on Thu Apr 14 19:10:26 2022
    On April 14, Clive Arthur wrote:
    When you interview job candidates, you pose standard
    problems, of circuits, PSpice, maybe Mathcad, etc.
    Textbook stuff, you expect he knows,
    Microsoft and Google are famous for posing brain twisters,
    stuff "outside the book" (if any exists, nowadays with the net).
    Do you do this? The obvious idea is to test for originality.
    How much weight do you place on the responses?

    Write a bit of generic code to calculate a square root.

    That's what I have in mind.

    Probably the applicant has never done this, now he's on his own,
    he has to think his way through a problem. That's what you
    watch - not the answer, but his thinking.

    What temperature does solder melt at? This one's interesting, most
    don't know of course, but some can't even make a guess, and even if the
    guess is wildly wrong the reasoning can be good.

    OK, I'll bite - how does one 'reason' one's way to a melting point?
    Mentally solve Schrodinger's equation, given the molecular structure of solder?

    They showed me a small PCB and asked me what it was.
    From the 741 op-amp and the fairly large value capacitors I deduced
    that it was probably a low power audio amplifier. Their notes just said "circuit board".
    They then handed me a resistor which I told them was a
    4k7 5% 1/4 watt resistor. Their notes just said "resistor".

    hmmm... did any candidate fail this exam?

    --
    Rich

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Miles, KE5FX@21:1/5 to Clive Arthur on Thu Apr 14 19:40:39 2022
    On Thursday, April 14, 2022 at 3:05:59 AM UTC-7, Clive Arthur wrote:
    Write a bit of generic code to calculate a square root.

    int i=1,root=0; while (input > 0) { input -= i; i += 2; root++; }

    Well, you didn't say it had to be FAST...

    -- john, KE5FX

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to RichD on Thu Apr 14 21:11:42 2022
    On 4/14/2022 7:10 PM, RichD wrote:

    Write a bit of generic code to calculate a square root.

    That's what I have in mind.

    Probably the applicant has never done this, now he's on his own,
    he has to think his way through a problem. That's what you
    watch - not the answer, but his thinking.

    The typical sort of "test" for "programmers" would be a sort.
    As this is a well-baked issue, the test is geared at noting
    if the applicant knows the different types of sort algorithms
    and the tradeoffs/execution times of each.

    The "red flag" being the applicant who doesn't look for more
    clarification on the number of items being sorted, their
    characteristics, the nature of the list *before* the sort,
    how it will be used *after* the sort, etc.

    Because it is a relatively *simple* problem, you don't have to
    worry about "test averse" applicants "choking" in the process.

    Of course, if you are looking for "niche" applications, one
    might ask the applicant to describe scenarios where deadlock
    can occur, livelock, priority inversion, etc. Or, issues
    regarding specific protocol stacks, etc.

    And, if the programmer will have to interface to hardware,
    there are a variety of simple challenges that will tell you
    if he knows the issues that are pertinent, there (and how
    reality can defy his code's assumptions -- in delightfully
    clever ways!)

    But, "process" is always paramount. Is he a defensive coder, etc.?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Larkin@21:1/5 to r_delaney2001@yahoo.com on Fri Apr 15 10:06:24 2022
    On Thu, 14 Apr 2022 19:10:26 -0700 (PDT), RichD
    <r_delaney2001@yahoo.com> wrote:

    On April 14, Clive Arthur wrote:
    When you interview job candidates, you pose standard
    problems, of circuits, PSpice, maybe Mathcad, etc.
    Textbook stuff, you expect he knows,
    Microsoft and Google are famous for posing brain twisters,
    stuff "outside the book" (if any exists, nowadays with the net).
    Do you do this? The obvious idea is to test for originality.
    How much weight do you place on the responses?

    Write a bit of generic code to calculate a square root.

    For an integer, just binary search the bits, like an SAR ADC.

    --

    If a man will begin with certainties, he shall end with doubts,
    but if he will be content to begin with doubts he shall end in certainties. Francis Bacon

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Wim Ton@21:1/5 to All on Fri Apr 15 13:03:15 2022
    I was interviewed for the job of well logging engineer. Besides answering common engineering questions, I was asked to solve the problems written on a whiteboard behind my back. The usual stuff, like "what is the next number in this sequence".
    Anyway, I got the job.

    Wim Ton

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joe Gwinn@21:1/5 to r_delaney2001@yahoo.com on Fri Apr 15 15:27:32 2022
    On Thu, 14 Apr 2022 19:10:26 -0700 (PDT), RichD
    <r_delaney2001@yahoo.com> wrote:

    On April 14, Clive Arthur wrote:
    When you interview job candidates, you pose standard
    problems, of circuits, PSpice, maybe Mathcad, etc.
    Textbook stuff, you expect he knows,
    Microsoft and Google are famous for posing brain twisters,
    stuff "outside the book" (if any exists, nowadays with the net).
    Do you do this? The obvious idea is to test for originality.
    How much weight do you place on the responses?

    Write a bit of generic code to calculate a square root.

    That's what I have in mind.

    Probably the applicant has never done this, now he's on his own,
    he has to think his way through a problem. That's what you
    watch - not the answer, but his thinking.

    What temperature does solder melt at? This one's interesting, most
    don't know of course, but some can't even make a guess, and even if the
    guess is wildly wrong the reasoning can be good.

    OK, I'll bite - how does one 'reason' one's way to a melting point?
    Mentally solve Schrodinger's equation, given the molecular structure of solder?

    They showed me a small PCB and asked me what it was.
    From the 741 op-amp and the fairly large value capacitors I deduced
    that it was probably a low power audio amplifier. Their notes just said
    "circuit board".
    They then handed me a resistor which I told them was a
    4k7 5% 1/4 watt resistor. Their notes just said "resistor".

    hmmm... did any candidate fail this exam?

    What I usually do is to give the candidate a sheet of paper and ask
    him to draw a block diagram and describe their favorite project in
    great detail. This generally flushes the poseurs out - the know none
    of the expected details.

    There was one time when I was screening June grads in EE, and asked
    this kind of question, and got nowhere. Long story short, I
    eventually asked him to state and explain Ohm's Law. Total blank.

    It developed that he was on the Varsity Football Team. Hmm. Probably
    never attended a single class. I do not know whose idea it was to
    grant an EE degree, because there is no way he could ever fake it in
    an EE job.

    Joe Gwinn

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Clifford Heath@21:1/5 to John Larkin on Sat Apr 16 08:03:21 2022
    On 16/4/22 3:06 am, John Larkin wrote:
    On Thu, 14 Apr 2022 19:10:26 -0700 (PDT), RichD
    <r_delaney2001@yahoo.com> wrote:

    On April 14, Clive Arthur wrote:
    When you interview job candidates, you pose standard
    problems, of circuits, PSpice, maybe Mathcad, etc.
    Textbook stuff, you expect he knows,
    Microsoft and Google are famous for posing brain twisters,
    stuff "outside the book" (if any exists, nowadays with the net).
    Do you do this? The obvious idea is to test for originality.
    How much weight do you place on the responses?

    Write a bit of generic code to calculate a square root.

    For an integer, just binary search the bits, like an SAR ADC.

    Quicker to start by finding the highest 1 (number of significant bits).
    This is a single opcode in many architectures. The square root will have
    half as many significant bits, or one fewer than that. Instantly narrows
    the search space by a *lot*.

    CH

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to jlarkin@highlandsniptechnology.com on Sat Apr 16 11:37:50 2022
    On 14/04/2022 15:35, jlarkin@highlandsniptechnology.com wrote:
    On Thu, 14 Apr 2022 08:51:50 +0100, Martin Brown
    <'''newspam'''@nonad.co.uk> wrote:

    On 13/04/2022 21:02, RichD wrote:
    When you interview job candidates, you pose standard
    problems, of circuits, PSpice, maybe Mathcad, etc.
    Textbook stuff, you expect he knows, reviewing his resume.

    Microsoft and Google are famous for posing brain twisters,
    stuff "outside the book" (if any exists, nowadays with the net).
    Do you do this? The obvious idea is to test for originality.

    Most regular interviewers have their own favourite pet questions.

    Discussing the right answers online would defeat the object so they
    don't stay useable for long in this age of everything on social media.

    How many zeroes does 100! have in its decimal representation is one such
    that has been popular in recent years.

    How much weight do you place on the responses?

    Watching how they approach an unfamiliar problem can be a sufficient
    guide to do they have what it takes. Engineering can get away with an
    answer that whilst not exactly right is "good enough" for practical
    purposes.

    A pure mathematics course would expect the right answer (and quickly).

    You have to know what characteristics you are recruiting for to pick the
    right test question(s) for the position if you are playing this game.

    Whether the individual will fit in with the team is often much more
    important than technical prowess (provided that is adequate).

    Unless that is you enjoy herding cats (something software engineering
    management has been compared with - more than our fair share of divas).


    Puzzles, especially math puzzles, tell a small part about a person's
    prospect as a design engineer. Puzzles are an easy thing for HR folks
    to use.

    The open ended puzzle tests are not particularly useful when used by HR.
    Anyway they prefer multiple choice off the shelf standardised
    personality tests - so much easier to mark.

    To find out how someone will work with your design team, just do it.

    Although I draw the line at the nasty modern practice of tasking some
    bunch of poor unfortunate would be recruits with solving one of your
    tricky real world problems for nothing in an attempt to win the job.

    You can generally tell pretty quickly whether or not someone really
    knows their stuff as claimed on the CV or has mugged it up from "Ace the technical interview for Dummies" or even done no prep at all.

    "What would you like to ask me about the job?" can be informative too.

    We had a couple of short test pieces of code ~20 lines for each language
    and the test was to explain what the code does. Much like you would with
    a circuit diagram in hardware. Quite a few had no real understanding of
    the language(s) that they claimed to know fluently. Saved a lot of time.

    One of the key requirements is to have a balanced team.

    You need the odd completer finisher to ensure that the last remaining uninteresting bits do get done when the people who break new ground are
    off doing the next interesting big project. Resource is always finite.

    --
    Regards,
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jlarkin@highlandsniptechnology.com@21:1/5 to '''newspam'''@nonad.co.uk on Sat Apr 16 08:12:50 2022
    On Sat, 16 Apr 2022 11:37:50 +0100, Martin Brown
    <'''newspam'''@nonad.co.uk> wrote:

    On 14/04/2022 15:35, jlarkin@highlandsniptechnology.com wrote:
    On Thu, 14 Apr 2022 08:51:50 +0100, Martin Brown
    <'''newspam'''@nonad.co.uk> wrote:

    On 13/04/2022 21:02, RichD wrote:
    When you interview job candidates, you pose standard
    problems, of circuits, PSpice, maybe Mathcad, etc.
    Textbook stuff, you expect he knows, reviewing his resume.

    Microsoft and Google are famous for posing brain twisters,
    stuff "outside the book" (if any exists, nowadays with the net).
    Do you do this? The obvious idea is to test for originality.

    Most regular interviewers have their own favourite pet questions.

    Discussing the right answers online would defeat the object so they
    don't stay useable for long in this age of everything on social media.

    How many zeroes does 100! have in its decimal representation is one such >>> that has been popular in recent years.

    How much weight do you place on the responses?

    Watching how they approach an unfamiliar problem can be a sufficient
    guide to do they have what it takes. Engineering can get away with an
    answer that whilst not exactly right is "good enough" for practical
    purposes.

    A pure mathematics course would expect the right answer (and quickly).

    You have to know what characteristics you are recruiting for to pick the >>> right test question(s) for the position if you are playing this game.

    Whether the individual will fit in with the team is often much more
    important than technical prowess (provided that is adequate).

    Unless that is you enjoy herding cats (something software engineering
    management has been compared with - more than our fair share of divas).


    Puzzles, especially math puzzles, tell a small part about a person's
    prospect as a design engineer. Puzzles are an easy thing for HR folks
    to use.

    The open ended puzzle tests are not particularly useful when used by HR. >Anyway they prefer multiple choice off the shelf standardised
    personality tests - so much easier to mark.

    To find out how someone will work with your design team, just do it.

    Although I draw the line at the nasty modern practice of tasking some
    bunch of poor unfortunate would be recruits with solving one of your
    tricky real world problems for nothing in an attempt to win the job.

    You can generally tell pretty quickly whether or not someone really
    knows their stuff as claimed on the CV or has mugged it up from "Ace the >technical interview for Dummies" or even done no prep at all.

    "What would you like to ask me about the job?" can be informative too.

    We had a couple of short test pieces of code ~20 lines for each language
    and the test was to explain what the code does. Much like you would with
    a circuit diagram in hardware. Quite a few had no real understanding of
    the language(s) that they claimed to know fluently. Saved a lot of time.

    One of the key requirements is to have a balanced team.

    You need the odd completer finisher to ensure that the last remaining >uninteresting bits do get done when the people who break new ground are
    off doing the next interesting big project. Resource is always finite.

    We did a job interview yesterday. The guy arrived at 11 AM and left
    just after 6 PM. I walked him over the I80 footbridge back to his car.

    We brainstormed the architecture and details of a planned product
    line, including things that we haven't yet resolved. Free consulting.

    I taught him a few things about pcb traces and grounding in picosecond circuits. He hadn't done any fast wideband stuff and had some
    conventionally silly ideas about return currents, but he is sound on
    grounding. Looks good at thermals and packaging too.

    It was interesting to see not just his intelligence and technical
    range, but how he generated ideas and reacted to other peoples' ideas.
    Perhaps a tad dogmatic, but I guess people are stressed in interviews.

    He also cooks, and bakes bread, so we took him for Thai lunch outdoors
    and then walked to Tartine and bought him a gigantic sourdough country
    loaf. All that sort of stuff suggests how people might work together.

    He admits to being autistic, which is if anything an asset in our
    business. Another guy that we zoom interviewed this week is autistic
    too. Visibly so.

    We agreed that if we hire him, it will be as a virtual intern, in
    other words we'd try it for few months to see how it works and part
    friends if not. That was his suggestion, and I like it.



    --

    I yam what I yam - Popeye

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From RichD@21:1/5 to wim...@gmail.com on Sat Apr 16 12:05:31 2022
    On April 15, wim...@gmail.com wrote:
    I was interviewed for the job of well logging engineer. Besides answering common engineering questions, I was asked to solve the problems written
    on a whiteboard behind my back. The usual stuff, like "what is the next number in this sequence".

    77, 49, 36, 18, ... ?


    --
    Rich

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Hobbs@21:1/5 to RichD on Sat Apr 16 16:42:38 2022
    RichD wrote:
    On April 15, wim...@gmail.com wrote:
    I was interviewed for the job of well logging engineer. Besides answering
    common engineering questions, I was asked to solve the problems written
    on a whiteboard behind my back. The usual stuff, like "what is the next
    number in this sequence".

    77, 49, 36, 18, ... ?


    --
    Rich

    8, 0, 0, 0, 0,....

    Cheers

    Phil Hobbs

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From whit3rd@21:1/5 to All on Sat Apr 16 14:33:36 2022
    On Thursday, April 14, 2022 at 7:40:42 PM UTC-7, John Miles, KE5FX wrote:
    On Thursday, April 14, 2022 at 3:05:59 AM UTC-7, Clive Arthur wrote:
    Write a bit of generic code to calculate a square root.
    int i=1,root=0; while (input > 0) { input -= i; i += 2; root++; }

    Well, you didn't say it had to be FAST...

    Isn't FORTRAN generic? Statement function would do it

    squareroot(x) = exp(alog(0.5 * x) )

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Allison@21:1/5 to jla...@highlandsniptechnology.com on Sat Apr 16 14:16:01 2022
    jla...@highlandsniptechnology.com wrote:

    ==================================

    It was interesting to see not just his intelligence and technical
    range, but how he generated ideas and reacted to other peoples' ideas. Perhaps a tad dogmatic,

    ** So in reality a whole lot and exactly like JL - another autistic.

    but I guess people are stressed in interviews.

    ** Nope - that is how most autistics permanently ARE.


    He also cooks, and bakes bread, so we took him for Thai lunch outdoors
    and then walked to Tartine and bought him a gigantic sourdough country
    loaf. All that sort of stuff suggests how people might work together.

    ** No it does not.

    He admits to being autistic, which is if anything an asset in our business.

    ** My god, what a shitty business you are in.

    But I guess being socially awkward and obsessed with tiny details is some sort advantage when doing PCBs.

    Another guy that we zoom interviewed this week is autistic too.

    ** So PCB design is one step below code scribbling ?

    Visibly so.

    ** Wonder what that means.

    Hesitant speech, makes no eye contact and looks plain odd?
    Met more than a few of them.
    Otherwise know as " useful idiots ".


    We agreed that if we hire him, it will be as a virtual intern,

    ** So he is gonna be employing AI?



    ...... Phil

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From RichD@21:1/5 to Phil Hobbs on Sat Apr 16 14:39:44 2022
    On April 16, Phil Hobbs wrote:
    Besides answering common engineering questions, I was asked to solve the >>> problems written on a whiteboard behind my back. The usual stuff, like "what
    is the next number in this sequence".

    77, 49, 36, 18, ... ?

    8, 0, 0, 0 ....

    https://www.youtube.com/watch?v=yscaDkzHqek

    Given a Tom Collins glass, 4" high, 6" circumference.
    A spider sits on the outside, 1" from the bottom.
    A fly lands on the inside, 1" from the top, on the opposite side.
    The spider, who aced the calculus of variations, takes the shortest
    route and pounces.
    What route, what distance?

    --
    Rich

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From whit3rd@21:1/5 to Phil Hobbs on Sat Apr 16 14:56:18 2022
    On Saturday, April 16, 2022 at 1:42:48 PM UTC-7, Phil Hobbs wrote:
    RichD wrote:
    On April 15, wim...@gmail.com wrote:
    ...I was asked to solve the problems written
    on a whiteboard behind my back. The usual stuff, like "what is the next
    number in this sequence".

    77, 49, 36, 18, ... ?

    8, 0, 0, 0, 0,....

    OEIS.org lists the 8, 8, 8, 8 variant only; you might want to submit yours for inclusion

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jlarkin@highlandsniptechnology.com@21:1/5 to pallison49@gmail.com on Sat Apr 16 15:19:51 2022
    On Sat, 16 Apr 2022 14:16:01 -0700 (PDT), Phil Allison
    <pallison49@gmail.com> wrote:

    jla...@highlandsniptechnology.com wrote:

    ==================================

    It was interesting to see not just his intelligence and technical
    range, but how he generated ideas and reacted to other peoples' ideas.
    Perhaps a tad dogmatic,

    ** So in reality a whole lot and exactly like JL - another autistic.

    No, quite different. It's called a "spectrum" for good reason.


    but I guess people are stressed in interviews.

    ** Nope - that is how most autistics permanently ARE.


    No, quite the opposite. All sorts of things that other people worry
    about, I absolutely ignore.




    He also cooks, and bakes bread, so we took him for Thai lunch outdoors
    and then walked to Tartine and bought him a gigantic sourdough country
    loaf. All that sort of stuff suggests how people might work together.

    ** No it does not.

    He admits to being autistic, which is if anything an asset in our business.

    ** My god, what a shitty business you are in.

    Thinking objectively, inventing things that work. It's fun and pays
    well.


    But I guess being socially awkward and obsessed with tiny details is some sort advantage when doing PCBs.

    The tiny details matter. There are thousands of possible mistakes on a
    complex board, and it takes some obsession to get every one right. As
    it takes some dedication to be really good at most anything.


    Another guy that we zoom interviewed this week is autistic too.

    ** So PCB design is one step below code scribbling ?

    Visibly so.

    ** Wonder what that means.

    Rocking back and forth into the camera, especially visible with the
    close-up cam of a laptop. I let him know so maybe he can try to not do
    it in the future.

    Mo works with autistics. She suggests he do something out of sight,
    like squeeze a rubber ball maybe.


    Hesitant speech, makes no eye contact and looks plain odd?

    No that guy was great otherwise. Really smart, but wants to do
    wireless stuff, which we don't do.





    --

    I yam what I yam - Popeye

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Allison@21:1/5 to jla...@highlandsniptechnology.com on Sat Apr 16 15:48:50 2022
    jla...@highlandsniptechnology.com wrote:

    ==================================

    It was interesting to see not just his intelligence and technical
    range, but how he generated ideas and reacted to other peoples' ideas.
    Perhaps a tad dogmatic,

    ** So in reality a whole lot and exactly like JL - another autistic.
    <
    No, quite different. It's called a "spectrum" for good reason.


    ** JL misreads, all the time.

    His words "... a tad dogmatic" - are clearly an understatement.
    So in reality the applicant was a whole lot dogmatic
    Like JL is, 100% of the time, including now.


    but I guess people are stressed in interviews.

    ** Nope - that is how most autistics permanently ARE.

    No, quite the opposite.

    ** Fraid that is a totally undeniable fact.


    He admits to being autistic, which is if anything an asset in our business.

    ** My god, what a shitty business you are in.

    Thinking objectively,

    ** Not something JL has ever done.
    ASD people cannot be genuinely objective.
    Lacking empathy just makes them mean and nasty.


    But I guess being socially awkward and obsessed with tiny details is some sort advantage when doing PCBs.

    The tiny details matter.

    ** But there is NO need to be autistic and obsessed to deal with details when needed.

    Another guy that we zoom interviewed this week is autistic too.

    ** So PCB design is one step below code scribbling ?

    Visibly so.

    ** Wonder what that means.

    Rocking back and forth into the camera, especially visible with the
    close-up cam of a laptop. I let him know so maybe he can try to not do
    it in the future.

    ** LOL - better he not LOOK like a nut case - eh ?


    Mo works with autistics.

    ** She is one, you fool.


    Hesitant speech, makes no eye contact and looks plain odd?

    No that guy was great otherwise.

    ** Blatant lie.

    One autistic has no way to evaluate another.
    Be like a blind person trying to evaluate someone's vision.




    ..... Phil

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Clifford Heath@21:1/5 to RichD on Sun Apr 17 09:56:30 2022
    On 17/4/22 7:39 am, RichD wrote:
    On April 16, Phil Hobbs wrote:
    Besides answering common engineering questions, I was asked to solve the >>>> problems written on a whiteboard behind my back. The usual stuff, like "what
    is the next number in this sequence".

    77, 49, 36, 18, ... ?

    8, 0, 0, 0 ....

    https://www.youtube.com/watch?v=yscaDkzHqek

    Given a Tom Collins glass, 4" high, 6" circumference.
    A spider sits on the outside, 1" from the bottom.
    A fly lands on the inside, 1" from the top, on the opposite side.
    The spider, who aced the calculus of variations, takes the shortest
    route and pounces.
    What route, what distance?

    Can it jump across from the opposite lip?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jlarkin@highlandsniptechnology.com@21:1/5 to pallison49@gmail.com on Sat Apr 16 18:47:19 2022
    On Sat, 16 Apr 2022 15:48:50 -0700 (PDT), Phil Allison
    <pallison49@gmail.com> wrote:

    jla...@highlandsniptechnology.com wrote:

    ==================================

    It was interesting to see not just his intelligence and technical
    range, but how he generated ideas and reacted to other peoples' ideas.
    Perhaps a tad dogmatic,

    ** So in reality a whole lot and exactly like JL - another autistic.
    <
    No, quite different. It's called a "spectrum" for good reason.


    ** JL misreads, all the time.

    His words "... a tad dogmatic" - are clearly an understatement.
    So in reality the applicant was a whole lot dogmatic
    Like JL is, 100% of the time, including now.


    but I guess people are stressed in interviews.

    ** Nope - that is how most autistics permanently ARE.

    No, quite the opposite.

    ** Fraid that is a totally undeniable fact.


    He admits to being autistic, which is if anything an asset in our business.

    ** My god, what a shitty business you are in.

    Thinking objectively,

    ** Not something JL has ever done.
    ASD people cannot be genuinely objective.
    Lacking empathy just makes them mean and nasty.


    But I guess being socially awkward and obsessed with tiny details is some sort advantage when doing PCBs.

    The tiny details matter.

    ** But there is NO need to be autistic and obsessed to deal with details when needed.

    Another guy that we zoom interviewed this week is autistic too.

    ** So PCB design is one step below code scribbling ?

    Visibly so.

    ** Wonder what that means.

    Rocking back and forth into the camera, especially visible with the
    close-up cam of a laptop. I let him know so maybe he can try to not do
    it in the future.

    ** LOL - better he not LOOK like a nut case - eh ?


    Mo works with autistics.

    ** She is one, you fool.


    Hesitant speech, makes no eye contact and looks plain odd?

    No that guy was great otherwise.

    ** Blatant lie.

    One autistic has no way to evaluate another.
    Be like a blind person trying to evaluate someone's vision.

    The issue isn't personality stuff, it's electronics: not in your skill
    set.



    --

    I yam what I yam - Popeye

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Allison@21:1/5 to jla...@highlandsniptechnology.com on Sat Apr 16 19:08:55 2022
    jla...@highlandsniptechnology.com wrote:

    ==================================

    It was interesting to see not just his intelligence and technical
    range, but how he generated ideas and reacted to other peoples' ideas. >> >> Perhaps a tad dogmatic,

    ** So in reality a whole lot and exactly like JL - another autistic.
    <
    No, quite different. It's called a "spectrum" for good reason.


    ** JL misreads, all the time.

    His words "... a tad dogmatic" - are clearly an understatement.
    So in reality the applicant was a whole lot dogmatic
    Like JL is, 100% of the time, including now.


    but I guess people are stressed in interviews.

    ** Nope - that is how most autistics permanently ARE.

    No, quite the opposite.

    ** Fraid that is a totally undeniable fact.


    He admits to being autistic, which is if anything an asset in our business.

    ** My god, what a shitty business you are in.

    Thinking objectively,

    ** Not something JL has ever done.
    ASD people cannot be genuinely objective.
    Lacking empathy just makes them mean and nasty.


    But I guess being socially awkward and obsessed with tiny details is some sort advantage when doing PCBs.

    The tiny details matter.

    ** But there is NO need to be autistic and obsessed to deal with details when needed.

    Another guy that we zoom interviewed this week is autistic too.

    ** So PCB design is one step below code scribbling ?

    Visibly so.

    ** Wonder what that means.

    Rocking back and forth into the camera, especially visible with the
    close-up cam of a laptop. I let him know so maybe he can try to not do
    it in the future.

    ** LOL - better he not LOOK like a nut case - eh ?


    Mo works with autistics.

    ** She is one, you fool.


    Hesitant speech, makes no eye contact and looks plain odd?

    No that guy was great otherwise.

    ** Blatant lie.

    One autistic has no way to evaluate another.
    Be like a blind person trying to evaluate someone's vision.

    The issue isn't personality stuff,

    ** It is and YOU raised it, in direst relation to " interviewing".
    FFS READ your own words !!!.

    it's electronics:

    ** Anyone can see " electronics" was never even mentioned.

    What an absurd lie and pathetic obfuscation.
    How typically autistic of JL....



    ....... Phil

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to jla...@highlandsniptechnology.com on Sat Apr 16 20:07:47 2022
    On Sunday, April 17, 2022 at 11:47:29 AM UTC+10, jla...@highlandsniptechnology.com wrote:
    On Sat, 16 Apr 2022 15:48:50 -0700 (PDT), Phil Allison
    <palli...@gmail.com> wrote:
    jla...@highlandsniptechnology.com wrote:

    <snip>

    ASD people cannot be genuinely objective.
    Lacking empathy just makes them mean and nasty.

    They lack the capacity to pick up social signals. That doesn't make them means and nasty - once they work out that they have been unintentionally offensive, they can be just as apologetic as anybody else.
    Phil seems to lack the capacity to be apologetic.

    But I guess being socially awkward and obsessed with tiny details is some sort advantage when doing PCBs.

    The tiny details matter.

    ** But there is NO need to be autistic and obsessed to deal with details when needed.

    Dedication is all that it takes. But there aren't all that many dedicated people around. If you've got lots of printed circuit boards to get laid out, you may have to settle for obsessive.

    <snip>

    Hesitant speech, makes no eye contact and looks plain odd?

    No that guy was great otherwise.

    ** Blatant lie.

    By which Phil means that he doesn't want to believe it.

    One autistic has no way to evaluate another.
    Be like a blind person trying to evaluate someone's vision.

    Autism involves some deficits in social interaction. The small visual and acoustic cues that most of us pick up automatically do help in evaluating other people, but there is plenty of other information available, not that Phil seems to know how to
    process it.

    The issue isn't personality stuff, it's electronics: not in your skill set.

    Phil is actually very good at audio electronics. John Larkin has an inflated idea of his own electronic expertise. He's good but not as good as he likes to think, and he seems to have failed to notice when Phil's expertise was displayed here, as it has
    been from time to time.

    John is also prone to insulting people by claiming that they "don't design electronics", which is a trifle ironic since John Larkin's approach to circuit design looks more like evolving a better circuit by trying out lots of tiny incremental changes.
    Most people's design process involves evaluating a lot of different ideas before turning one or two into prototypes and evaluating them, and they can talk about the blind alleys that they looked at. Maybe John Larkin is too vain to admit spending time
    exploring blind alleys.

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to palli...@gmail.com on Sat Apr 16 19:20:55 2022
    On Sunday, April 17, 2022 at 7:16:06 AM UTC+10, palli...@gmail.com wrote:
    jla...@highlandsniptechnology.com wrote:

    <snip>

    He admits to being autistic, which is if anything an asset in our business.

    ** My god, what a shitty business you are in.

    Wrong. Electronics is about getting everything right, and some autistic people are good at concentrating on their task, rather than getting distracted by the social interactions they aren't all that good at.

    But I guess being socially awkward and obsessed with tiny details is some sort advantage when doing PCBs.

    Another guy that we zoom interviewed this week is autistic too.

    ** So PCB design is one step below code scribbling ?

    It requires spatial skills, which coding doesn't. It used to be easier to get printed circuit layout drafts-people than programmers, but there's no reason to suppose that this still true.

    Visibly so.

    ** Wonder what that means.

    Hesitant speech, makes no eye contact and looks plain odd?
    Met more than a few of them.

    Or thinks he has. Somebody talking to Phil would chose his words carefully - you wouldn't want to provoke a tantrum.

    Otherwise know as " useful idiots ".

    They aren't. Being autistic doesn't make you any kind of idiot. Lenin used the term "useful idiot" to describe people who believed in democratic socialism and thought that that meant that they ought to support the Communist Party, which claims to be
    socialist, but isn't democratic.

    We agreed that if we hire him, it will be as a virtual intern,

    ** So he is gonna be employing AI?

    Sounds more like working remotely. There's not a lot of artificial intelligence in that.

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to jla...@highlandsniptechnology.com on Sat Apr 16 19:41:48 2022
    On Sunday, April 17, 2022 at 8:20:02 AM UTC+10, jla...@highlandsniptechnology.com wrote:
    On Sat, 16 Apr 2022 14:16:01 -0700 (PDT), Phil Allison
    <palli...@gmail.com> wrote:

    jla...@highlandsniptechnology.com wrote: =

    It was interesting to see not just his intelligence and technical
    range, but how he generated ideas and reacted to other peoples' ideas.
    Perhaps a tad dogmatic,

    Didn't agree with John Larkin quite as fast as John would have liked.

    ** So in reality a whole lot and exactly like JL - another autistic.

    No, quite different. It's called a "spectrum" for good reason.

    but I guess people are stressed in interviews.

    ** Nope - that is how most autistics permanently ARE.

    What Phil knows about being autistic seems to come from calling other people autistic. and probably from being told that he is austistic (though that's merely a plausible hypothesis).

    He certainly seems to see many more autistic people than you'd expect from the Australian population statistics, so his diagnostic criteria don't seem to be well calibrated.

    No, quite the opposite. All sorts of things that other people worry about, I absolutely ignore.

    That's excessive self-confidence and egomania - also exhibited by Donald Trump. Nothing to do with autism - though if you can't pick up the socials signals telling you that you are boasting to excess, you may be more likely to make a habit of it.

    He also cooks, and bakes bread, so we took him for Thai lunch outdoors
    and then walked to Tartine and bought him a gigantic sourdough country
    loaf. All that sort of stuff suggests how people might work together.

    ** No it does not.

    Not Phil, who isn't the most collaborative of engineers.

    He admits to being autistic, which is if anything an asset in our business.

    ** My god, what a shitty business you are in.

    Thinking objectively, inventing things that work. It's fun and pays well.

    But I guess being socially awkward and obsessed with tiny details is some sort advantage when doing PCBs.

    The tiny details matter. There are thousands of possible mistakes on a complex board, and it takes some obsession to get every one right.

    Not exactly obsession. Persistence works just as well, and it's handy if you can break off and worry about something else that turns out to be more urgent before getting back to finish the job.
    Obsession is less flexible.

    As it takes some dedication to be really good at most anything.

    Dedication isn't obsession.

    Another guy that we zoom interviewed this week is autistic too.

    ** So PCB design is one step below code scribbling ?

    Visibly so.

    ** Wonder what that means.

    Rocking back and forth into the camera, especially visible with the close-up cam of a laptop. I let him know so maybe he can try to not do it in the future.

    Mo works with autistics. She suggests he do something out of sight, like squeeze a rubber ball maybe.

    Hesitant speech, makes no eye contact and looks plain odd?

    No that guy was great otherwise. Really smart, but wants to do wireless stuff, which we don't do.

    Phil capacity for diagnosing autism is remarkable, but not all that reliable - he does see much more of it than people who are trained in how to look for it.

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From whit3rd@21:1/5 to All on Sat Apr 16 19:46:00 2022
    On Saturday, April 16, 2022 at 2:33:40 PM UTC-7, whit3rd wrote:
    On Thursday, April 14, 2022 at 7:40:42 PM UTC-7, John Miles, KE5FX wrote:
    On Thursday, April 14, 2022 at 3:05:59 AM UTC-7, Clive Arthur wrote:
    Write a bit of generic code to calculate a square root.

    Isn't FORTRAN generic? Statement function would do it

    squareroot(x) = exp(alog(0.5 * x) )

    Drat, those parentheses moved
    squareroot(x) = exp( 0.5 * alog(x))

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Piotr Wyderski@21:1/5 to Phil Hobbs on Sun Apr 17 09:03:16 2022
    Phil Hobbs wrote:

    8, 0, 0, 0, 0,....

    The sequence is unnecessarily long. The next number in any sequence is
    always zero and it invariably is my answer to this type of questions.
    Easy peasy to prove this claim with Newton interpolation polynomial.

    Best regards, Piotr

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jan Panteltje@21:1/5 to pcdhSpamMeSenseless@electrooptical. on Sun Apr 17 07:04:15 2022
    On a sunny day (Sat, 16 Apr 2022 16:42:38 -0400) it happened Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote in <t3f9o0$1jj7$1@gioia.aioe.org>:

    RichD wrote:
    On April 15, wim...@gmail.com wrote:
    I was interviewed for the job of well logging engineer. Besides answering >>> common engineering questions, I was asked to solve the problems written
    on a whiteboard behind my back. The usual stuff, like "what is the next
    number in this sequence".

    77, 49, 36, 18, ... ?


    --
    Rich

    8, 0, 0, 0, 0,....

    Cheers

    Phil Hobbs

    1,2,3,4,5,6,7,8,9,11

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jlarkin@highlandsniptechnology.com@21:1/5 to pallison49@gmail.com on Sun Apr 17 07:33:10 2022
    On Sat, 16 Apr 2022 19:08:55 -0700 (PDT), Phil Allison
    <pallison49@gmail.com> wrote:

    jla...@highlandsniptechnology.com wrote:

    ==================================

    It was interesting to see not just his intelligence and technical
    range, but how he generated ideas and reacted to other peoples' ideas. >> >> >> Perhaps a tad dogmatic,

    ** So in reality a whole lot and exactly like JL - another autistic.
    <
    No, quite different. It's called a "spectrum" for good reason.


    ** JL misreads, all the time.

    His words "... a tad dogmatic" - are clearly an understatement.
    So in reality the applicant was a whole lot dogmatic
    Like JL is, 100% of the time, including now.


    but I guess people are stressed in interviews.

    ** Nope - that is how most autistics permanently ARE.

    No, quite the opposite.

    ** Fraid that is a totally undeniable fact.


    He admits to being autistic, which is if anything an asset in our business.

    ** My god, what a shitty business you are in.

    Thinking objectively,

    ** Not something JL has ever done.
    ASD people cannot be genuinely objective.
    Lacking empathy just makes them mean and nasty.


    But I guess being socially awkward and obsessed with tiny details is some sort advantage when doing PCBs.

    The tiny details matter.

    ** But there is NO need to be autistic and obsessed to deal with details when needed.

    Another guy that we zoom interviewed this week is autistic too.

    ** So PCB design is one step below code scribbling ?

    Visibly so.

    ** Wonder what that means.

    Rocking back and forth into the camera, especially visible with the
    close-up cam of a laptop. I let him know so maybe he can try to not do
    it in the future.

    ** LOL - better he not LOOK like a nut case - eh ?


    Mo works with autistics.

    ** She is one, you fool.


    Hesitant speech, makes no eye contact and looks plain odd?

    No that guy was great otherwise.

    ** Blatant lie.

    One autistic has no way to evaluate another.
    Be like a blind person trying to evaluate someone's vision.

    The issue isn't personality stuff,

    ** It is and YOU raised it, in direst relation to " interviewing".
    FFS READ your own words !!!.

    it's electronics:

    ** Anyone can see " electronics" was never even mentioned.

    When we interview EEs, of course we talk about electronics. We did
    that for 5 hours on Friday.

    I prefer in-person interviews, where we can whiteboard architectures
    and circuits and things. Work together.

    Personalities matter too of course, and that is best evaluated by
    working together for a while.


    What an absurd lie and pathetic obfuscation.
    How typically autistic of JL....

    There is no typical autism. It's not an OGOD (one gene, one disease)
    like Huntington's, but it's the sum of hundreds of genetic effects.
    Some trends are called "autism" by some people, but that's an
    arbitrary prejudice.

    You hate engineers because you can't understand the magic that we do.
    Lots of techs have that syndrome.



    --

    I yam what I yam - Popeye

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to jla...@highlandsniptechnology.com on Sun Apr 17 08:19:23 2022
    On Monday, April 18, 2022 at 12:33:20 AM UTC+10, jla...@highlandsniptechnology.com wrote:
    On Sat, 16 Apr 2022 19:08:55 -0700 (PDT), Phil Allison
    <palli...@gmail.com> wrote:
    jla...@highlandsniptechnology.com wrote:

    <snip>

    How typically autistic of JL....

    There is no typical autism. It's not an OGOD (one gene, one disease)
    like Huntington's, but it's the sum of hundreds of genetic effects.
    Some trends are called "autism" by some people, but that's an
    arbitrary prejudice.

    https://www.cdc.gov/ncbddd/autism/facts.html

    There is a a single diagnostic category labelled autistic spectrum disorders. There's not a single cause of all the various similar disorders, but they do have enough in common that they tend to be treated by a single class of medical practitioners. This
    single category may be a bit arbitrary - there are always going to be borderline cases - but clinical practice is shaped by patient behavior, not the other way around.

    You hate engineers because you can't understand the magic that we do. Lots of techs have that syndrome.

    Phil isn't any kind of technician. He knows his way around audio electronics pretty well and does understand what he is doing. You don't seem to - or you may just not be interested in what other people do, if they don't know enough about what you are
    doing to give the the kind of well-informed flattery that you crave, and don't seem to deserve.

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Allison@21:1/5 to ljla...@highlandsniptechnology.com on Sun Apr 17 15:05:09 2022
    ljla...@highlandsniptechnology.com wrote:
    ==================================


    It was interesting to see not just his intelligence and technical
    range, but how he generated ideas and reacted to other peoples' ideas.
    Perhaps a tad dogmatic,

    ** So in reality a whole lot and exactly like JL - another autistic. >> ><
    No, quite different. It's called a "spectrum" for good reason.


    ** JL misreads, all the time.

    His words "... a tad dogmatic" - are clearly an understatement.
    So in reality the applicant was a whole lot dogmatic
    Like JL is, 100% of the time, including now.


    but I guess people are stressed in interviews.

    ** Nope - that is how most autistics permanently ARE.

    No, quite the opposite.

    ** Fraid that is a totally undeniable fact.


    He admits to being autistic, which is if anything an asset in our business.

    ** My god, what a shitty business you are in.

    Thinking objectively,

    ** Not something JL has ever done.
    ASD people cannot be genuinely objective.
    Lacking empathy just makes them mean and nasty.


    But I guess being socially awkward and obsessed with tiny details is some sort advantage when doing PCBs.

    The tiny details matter.

    ** But there is NO need to be autistic and obsessed to deal with details when needed.

    Another guy that we zoom interviewed this week is autistic too.

    ** So PCB design is one step below code scribbling ?

    Visibly so.

    ** Wonder what that means.

    Rocking back and forth into the camera, especially visible with the
    close-up cam of a laptop. I let him know so maybe he can try to not do >> >> it in the future.

    ** LOL - better he not LOOK like a nut case - eh ?


    Mo works with autistics.

    ** She is one, you fool.


    Hesitant speech, makes no eye contact and looks plain odd?

    No that guy was great otherwise.

    ** Blatant lie.

    One autistic has no way to evaluate another.
    Be like a blind person trying to evaluate someone's vision.

    The issue isn't personality stuff,

    ** It is and YOU raised it, in direst relation to " interviewing".
    FFS READ your own words !!!.

    it's electronics:

    ** Anyone can see " electronics" was never even mentioned.


    When we interview EEs, of course we talk about electronics.

    ** Yaawwwnnn - more obfuscation.

    Plus JL resorts to the Royal Plural.

    Personalities matter too of course,

    ** Never mentioned either - what desperate liar.

    ( Autism is NOT a personality trait )


    What an absurd lie and pathetic obfuscation.
    How typically autistic of JL....

    There is no typical autism.

    ** Yet another dumb obfuscation - plus 100% false.

    like Huntington's, but it's the sum of hundreds of genetic effects.

    ** But just ONE overriding one.

    You hate engineers ....

    ** FFS, I am an engineer !!!

    What I hate are smug, narcissistic, bullshitting liars like YOU.
    Everybody hates them.



    .... Phil

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to palli...@gmail.com on Sun Apr 17 20:08:39 2022
    On Monday, April 18, 2022 at 8:05:13 AM UTC+10, palli...@gmail.com wrote:
    ljla...@highlandsniptechnology.com wrote:

    <snip>

    There is no typical autism.
    ** Yet another dumb obfuscation - plus 100% false.
    like Huntington's, but it's the sum of hundreds of genetic effects.

    ** But just ONE overriding one.

    Completely wrong.

    https://www.frontiersin.org/articles/10.3389/fncel.2019.00385/full

    <snip>

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Allison@21:1/5 to bill....@ieee.org on Sun Apr 17 20:28:08 2022
    Total IDIOT & Raving Ratbag bill....@ieee.org wrote: =========================================

    There is no typical autism.

    ** Yet another dumb obfuscation - plus 100% false.

    like Huntington's, but it's the sum of hundreds of genetic effects.

    ** But just ONE overriding one.

    Completely wrong.

    https://www.frontiersin.org/articles/10.3389/fncel.2019.00385/full


    ** Only CONGENITAL LIARS post links like that.
    And clueless Google Monkeys like Da Slowman demented idiot.

    It's really just the same as saying:

    " .. proof of my (very likely wrong assertion is in their somewhere - so go find it Rover. "

    Well, NO it fucking ain't:

    WOOF WOOF !!!



    ...... Phil

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to palli...@gmail.com on Sun Apr 17 20:47:09 2022
    On Monday, April 18, 2022 at 1:28:13 PM UTC+10, palli...@gmail.com wrote:
    bill....@ieee.org wrote:

    <snip>

    like Huntington's, but it's the sum of hundreds of genetic effects.

    ** But just ONE overriding one.

    Completely wrong.

    https://www.frontiersin.org/articles/10.3389/fncel.2019.00385/full

    ** Only CONGENITAL LIARS post links like that.

    Phil can't understand a word of it., and feels hurt.

    And clueless Google Monkeys like Bill Sloman.

    I'm fairly sure that Robert Plomin's "Blueprint" says much the same thing, but that's a book and I can't post a link to it's content

    https://www.penguin.com.au/books/blueprint-9780141984261

    It's really just the same as saying:

    " .. proof of my (very likely wrong assertion is in their somewhere - so go find it Rover. "

    "As is often the case with complex diseases, individuals with similar pathogenic variants may have drastically varying phenotypes".

    That sentence is in the introduction - not a lot of reading is required to get to it.

    Well, NO it fucking ain't: WOOF WOOF !!!

    Phil does seem to enjoy barking up the wrong tree.

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Allison@21:1/5 to All on Sun Apr 17 20:56:39 2022
    IEEE Bill rides ( his fat hobby horse) again: bill....@ieee.org wrote:

    ======================================================

    ** Re autism, JL postulated:

    but it's the sum of hundreds of genetic effects.

    ** But just ONE overriding one.

    ** The IEEE horseman got on his high one:.


    Completely wrong.

    https://www.frontiersin.org/articles/10.3389/fncel.2019.00385/full

    ** Only CONGENITAL LIARS post links like that.

    And clueless Google Monkeys like Bill Sloman.

    " .. proof of my (very likely wrong assertion is in their somewhere - so go find it Rover. "

    "As is often the case with complex diseases, individuals with similar pathogenic variants may have drastically varying phenotypes".


    ** Purest ** gobbledegook ** having ZERO to do with my simple and very true claim.

    That autistics have one characteristic thing in common.



    ...... Phil

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to palli...@gmail.com on Sun Apr 17 22:52:35 2022
    On Monday, April 18, 2022 at 1:56:42 PM UTC+10, palli...@gmail.com wrote:
    bill....@ieee.org wrote:

    ** Re autism, JL postulated:
    but it's the sum of hundreds of genetic effects.

    ** But just ONE overriding one.

    ** Bill got on his high horse:.

    As I do when people post utter nonsense.

    Completely wrong.

    https://www.frontiersin.org/articles/10.3389/fncel.2019.00385/full

    ** Only CONGENITAL LIARS post links like that.
    And clueless Google Monkeys like Bill Sloman.

    m fairly sure that Robert Plomin's "Blueprint" says much the same thing, but that's a book and I can't post a link to it's content.

    <Putting back the line Phil snipped.>

    " .. proof of my (very likely wrong assertion is in their somewhere - so go find it Rover. "

    "As is often the case with complex diseases, individuals with similar pathogenic variants may have drastically varying phenotypes".
    That sentence is in the introduction - not a lot of reading is required to get to it.

    ** Purest ** gobbledegook ** having ZERO to do with my simple and very true claim.

    Phil can't understand that it directly contradicts his simple - but totally false - claim. The phenotype is just what is produced when the genotype - the genetic blueprint provided in the original fertilised egg - has developed into an adult. If every
    sufferer from autism suffered from the same crucial genetic defect, they'd have a pretty similar phenotypes. They don't.

    That autistics have one characteristic thing in common.

    That isn't true either. If it were Phil could name it.

    His diagnosis of autism does seem to depend on one common characteristic - the sufferer has to have the temerity to disagree with Phil. Phil gets a lot of stuff wrong, so he does see a lot more "autism" than people who are trained to diagnose the actual
    disorder.

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to jlarkin@highlandsniptechnology.com on Mon Apr 18 11:14:58 2022
    On 16/04/2022 16:12, jlarkin@highlandsniptechnology.com wrote:
    On Sat, 16 Apr 2022 11:37:50 +0100, Martin Brown
    <'''newspam'''@nonad.co.uk> wrote:

    On 14/04/2022 15:35, jlarkin@highlandsniptechnology.com wrote:

    To find out how someone will work with your design team, just do it.

    Although I draw the line at the nasty modern practice of tasking some
    bunch of poor unfortunate would be recruits with solving one of your
    tricky real world problems for nothing in an attempt to win the job.

    You can generally tell pretty quickly whether or not someone really
    knows their stuff as claimed on the CV or has mugged it up from "Ace the
    technical interview for Dummies" or even done no prep at all.

    "What would you like to ask me about the job?" can be informative too.

    We had a couple of short test pieces of code ~20 lines for each language
    and the test was to explain what the code does. Much like you would with
    a circuit diagram in hardware. Quite a few had no real understanding of
    the language(s) that they claimed to know fluently. Saved a lot of time.

    One of the key requirements is to have a balanced team.

    You need the odd completer finisher to ensure that the last remaining
    uninteresting bits do get done when the people who break new ground are
    off doing the next interesting big project. Resource is always finite.

    We did a job interview yesterday. The guy arrived at 11 AM and left
    just after 6 PM. I walked him over the I80 footbridge back to his car.

    We brainstormed the architecture and details of a planned product
    line, including things that we haven't yet resolved. Free consulting.

    If you are going to offer a job to one of the candidates at the end of
    the interview process then fair enough. What I don't like are vapourware
    jobs just intended to obtain free consulting from would be candidates.

    Right now it isn't a problem in the UK almost everywhere is short
    staffed coming out of lockdown and it is very much a sellers market.
    He admits to being autistic, which is if anything an asset in our
    business. Another guy that we zoom interviewed this week is autistic
    too. Visibly so.

    High functioning autistic engineers can be very good if suitably
    motivated and pointed at the right problems (as various security
    breaches of various US military computers will attest).

    We agreed that if we hire him, it will be as a virtual intern, in
    other words we'd try it for few months to see how it works and part
    friends if not. That was his suggestion, and I like it.

    They can be a bit of a handful. Hope it works out for both sides.

    --
    Regards,
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jlarkin@highlandsniptechnology.com@21:1/5 to '''newspam'''@nonad.co.uk on Mon Apr 18 07:04:33 2022
    On Mon, 18 Apr 2022 11:14:58 +0100, Martin Brown
    <'''newspam'''@nonad.co.uk> wrote:

    On 16/04/2022 16:12, jlarkin@highlandsniptechnology.com wrote:
    On Sat, 16 Apr 2022 11:37:50 +0100, Martin Brown
    <'''newspam'''@nonad.co.uk> wrote:

    On 14/04/2022 15:35, jlarkin@highlandsniptechnology.com wrote:

    To find out how someone will work with your design team, just do it.

    Although I draw the line at the nasty modern practice of tasking some
    bunch of poor unfortunate would be recruits with solving one of your
    tricky real world problems for nothing in an attempt to win the job.

    You can generally tell pretty quickly whether or not someone really
    knows their stuff as claimed on the CV or has mugged it up from "Ace the >>> technical interview for Dummies" or even done no prep at all.

    "What would you like to ask me about the job?" can be informative too.

    We had a couple of short test pieces of code ~20 lines for each language >>> and the test was to explain what the code does. Much like you would with >>> a circuit diagram in hardware. Quite a few had no real understanding of
    the language(s) that they claimed to know fluently. Saved a lot of time. >>>
    One of the key requirements is to have a balanced team.

    You need the odd completer finisher to ensure that the last remaining
    uninteresting bits do get done when the people who break new ground are
    off doing the next interesting big project. Resource is always finite.

    We did a job interview yesterday. The guy arrived at 11 AM and left
    just after 6 PM. I walked him over the I80 footbridge back to his car.

    We brainstormed the architecture and details of a planned product
    line, including things that we haven't yet resolved. Free consulting.

    If you are going to offer a job to one of the candidates at the end of
    the interview process then fair enough. What I don't like are vapourware
    jobs just intended to obtain free consulting from would be candidates.


    Don't be silly. It would make no sense to spend time and money
    interviewing job seekers (which includes flying them to California for
    a few days and paying all the expenses) to get a few hours of
    questonable consulting. If we need consulting, we'd get someone good
    and pay them their rate.



    Right now it isn't a problem in the UK almost everywhere is short
    staffed coming out of lockdown and it is very much a sellers market.
    He admits to being autistic, which is if anything an asset in our
    business. Another guy that we zoom interviewed this week is autistic
    too. Visibly so.

    High functioning autistic engineers can be very good if suitably
    motivated and pointed at the right problems (as various security
    breaches of various US military computers will attest).

    We agreed that if we hire him, it will be as a virtual intern, in
    other words we'd try it for few months to see how it works and part
    friends if not. That was his suggestion, and I like it.

    They can be a bit of a handful. Hope it works out for both sides.

    Hiring is always scary. I hate to fire people, or have people walk
    out, but sometimes things don't work.





    --

    I yam what I yam - Popeye

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jlarkin@highlandsniptechnology.com@21:1/5 to pallison49@gmail.com on Mon Apr 18 06:57:57 2022
    On Sun, 17 Apr 2022 15:05:09 -0700 (PDT), Phil Allison
    <pallison49@gmail.com> wrote:

    ljla...@highlandsniptechnology.com wrote:
    ==================================


    It was interesting to see not just his intelligence and technical >> >> >> >> range, but how he generated ideas and reacted to other peoples' ideas.
    Perhaps a tad dogmatic,

    ** So in reality a whole lot and exactly like JL - another autistic. >> >> ><
    No, quite different. It's called a "spectrum" for good reason.


    ** JL misreads, all the time.

    His words "... a tad dogmatic" - are clearly an understatement.
    So in reality the applicant was a whole lot dogmatic
    Like JL is, 100% of the time, including now.


    but I guess people are stressed in interviews.

    ** Nope - that is how most autistics permanently ARE.

    No, quite the opposite.

    ** Fraid that is a totally undeniable fact.


    He admits to being autistic, which is if anything an asset in our business.

    ** My god, what a shitty business you are in.

    Thinking objectively,

    ** Not something JL has ever done.
    ASD people cannot be genuinely objective.
    Lacking empathy just makes them mean and nasty.


    But I guess being socially awkward and obsessed with tiny details is some sort advantage when doing PCBs.

    The tiny details matter.

    ** But there is NO need to be autistic and obsessed to deal with details when needed.

    Another guy that we zoom interviewed this week is autistic too.

    ** So PCB design is one step below code scribbling ?

    Visibly so.

    ** Wonder what that means.

    Rocking back and forth into the camera, especially visible with the
    close-up cam of a laptop. I let him know so maybe he can try to not do >> >> >> it in the future.

    ** LOL - better he not LOOK like a nut case - eh ?


    Mo works with autistics.

    ** She is one, you fool.


    Hesitant speech, makes no eye contact and looks plain odd?

    No that guy was great otherwise.

    ** Blatant lie.

    One autistic has no way to evaluate another.
    Be like a blind person trying to evaluate someone's vision.

    The issue isn't personality stuff,

    ** It is and YOU raised it, in direst relation to " interviewing".
    FFS READ your own words !!!.

    it's electronics:

    ** Anyone can see " electronics" was never even mentioned.


    When we interview EEs, of course we talk about electronics.

    ** Yaawwwnnn - more obfuscation.

    Plus JL resorts to the Royal Plural.

    The interview was one applicant and 5 of us. Also known as "we".

    I do need people to share the blame.



    --

    I yam what I yam - Popeye

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Allison@21:1/5 to jla...@highlandsniptechnology.com on Mon Apr 18 15:08:03 2022
    jla...@highlandsniptechnology.com wrote:

    ===================================

    ** Anyone can see " electronics" was never even mentioned.


    When we interview EEs, of course we talk about electronics.

    ** Yaawwwnnn - more obfuscation.

    Plus JL resorts to the Royal Plural.

    The interview was one applicant and 5 of us. Also known as "we".


    ** Jesus fucking Christ Almighty !!!!!!

    So now JL tells us he lines up a panel of * 5 smug autistics * like himself to interrogate and intimidate individual victims.
    What a living nightmare, Kafka would be impressed.

    Worst possible method of finding actually competent staff.
    Might as well flip a coin.



    ..... Phil

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tabby@21:1/5 to palli...@gmail.com on Thu Apr 21 01:27:50 2022
    On Monday, 18 April 2022 at 23:08:07 UTC+1, palli...@gmail.com wrote:
    jla...@highlandsniptechnology.com wrote:

    The interview was one applicant and 5 of us. Also known as "we".

    ** Jesus fucking Christ Almighty !!!!!!

    So now JL tells us he lines up a panel of * 5 smug autistics * like himself to interrogate and intimidate individual victims.
    What a living nightmare, Kafka would be impressed.

    Worst possible method of finding actually competent staff.
    Might as well flip a coin.



    ..... Phil

    1 2 1 interviewers miss a lot. You learn that from having multiple people interviewing.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tabby@21:1/5 to palli...@gmail.com on Thu Apr 21 01:22:07 2022
    On Saturday, 16 April 2022 at 23:48:54 UTC+1, palli...@gmail.com wrote:
    jla...@highlandsniptechnology.com wrote:

    ==================================

    It was interesting to see not just his intelligence and technical
    range, but how he generated ideas and reacted to other peoples' ideas. >> Perhaps a tad dogmatic,

    ** So in reality a whole lot and exactly like JL - another autistic.
    <
    No, quite different. It's called a "spectrum" for good reason.
    ** JL misreads, all the time.

    His words "... a tad dogmatic" - are clearly an understatement.
    So in reality the applicant was a whole lot dogmatic
    Like JL is, 100% of the time, including now.
    but I guess people are stressed in interviews.

    ** Nope - that is how most autistics permanently ARE.

    No, quite the opposite.
    ** Fraid that is a totally undeniable fact.
    He admits to being autistic, which is if anything an asset in our business.

    ** My god, what a shitty business you are in.

    Thinking objectively,
    ** Not something JL has ever done.
    ASD people cannot be genuinely objective.
    Lacking empathy just makes them mean and nasty.

    But I guess being socially awkward and obsessed with tiny details is some sort advantage when doing PCBs.

    The tiny details matter.
    ** But there is NO need to be autistic and obsessed to deal with details when needed.
    Another guy that we zoom interviewed this week is autistic too.

    ** So PCB design is one step below code scribbling ?

    Visibly so.

    ** Wonder what that means.

    Rocking back and forth into the camera, especially visible with the close-up cam of a laptop. I let him know so maybe he can try to not do
    it in the future.
    ** LOL - better he not LOOK like a nut case - eh ?


    Mo works with autistics.

    ** She is one, you fool.
    Hesitant speech, makes no eye contact and looks plain odd?

    No that guy was great otherwise.
    ** Blatant lie.

    One autistic has no way to evaluate another.
    Be like a blind person trying to evaluate someone's vision.




    ..... Phil

    Phil doesn't understand the autistic spectrum

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Allison@21:1/5 to All on Thu Apr 21 04:03:42 2022
    Tabby puked another hair ball:
    ========================

    So now JL tells us he lines up a panel of * 5 smug autistics * like himself to interrogate and intimidate individual victims.
    What a living nightmare, Kafka would be impressed.

    Worst possible method of finding actually competent staff.
    Might as well flip a coin.


    1 2 1 interviewers miss a lot.

    ** Not if they are reasonably smart people and NOT austistic fuckwits like YOU.

    You learn that from having multiple people interviewing.

    ** No you don't.

    FOAD Tabby



    ...... Phil

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Allison@21:1/5 to All on Thu Apr 21 04:01:01 2022
    Tabby puked up a hair ball:

    =======================

    One autistic has no way to evaluate another.
    Be like a blind person trying to evaluate someone's vision.

    Phil doesn't understand the autistic spectrum

    ** Tabby makes completely ASD fucked morons look smart.

    FOAD Tabby.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jlarkin@highlandsniptechnology.com@21:1/5 to All on Thu Apr 21 07:07:04 2022
    On Thu, 21 Apr 2022 01:22:07 -0700 (PDT), Tabby <tabbypurr@gmail.com>
    wrote:

    On Saturday, 16 April 2022 at 23:48:54 UTC+1, palli...@gmail.com wrote:
    jla...@highlandsniptechnology.com wrote:

    ==================================

    It was interesting to see not just his intelligence and technical
    range, but how he generated ideas and reacted to other peoples' ideas. >> > >> Perhaps a tad dogmatic,

    ** So in reality a whole lot and exactly like JL - another autistic.
    <
    No, quite different. It's called a "spectrum" for good reason.
    ** JL misreads, all the time.

    His words "... a tad dogmatic" - are clearly an understatement.
    So in reality the applicant was a whole lot dogmatic
    Like JL is, 100% of the time, including now.
    but I guess people are stressed in interviews.

    ** Nope - that is how most autistics permanently ARE.

    No, quite the opposite.
    ** Fraid that is a totally undeniable fact.
    He admits to being autistic, which is if anything an asset in our business.

    ** My god, what a shitty business you are in.

    Thinking objectively,
    ** Not something JL has ever done.
    ASD people cannot be genuinely objective.
    Lacking empathy just makes them mean and nasty.

    But I guess being socially awkward and obsessed with tiny details is some sort advantage when doing PCBs.

    The tiny details matter.
    ** But there is NO need to be autistic and obsessed to deal with details when needed.
    Another guy that we zoom interviewed this week is autistic too.

    ** So PCB design is one step below code scribbling ?

    Visibly so.

    ** Wonder what that means.

    Rocking back and forth into the camera, especially visible with the
    close-up cam of a laptop. I let him know so maybe he can try to not do
    it in the future.
    ** LOL - better he not LOOK like a nut case - eh ?


    Mo works with autistics.

    ** She is one, you fool.
    Hesitant speech, makes no eye contact and looks plain odd?

    No that guy was great otherwise.
    ** Blatant lie.

    One autistic has no way to evaluate another.
    Be like a blind person trying to evaluate someone's vision.




    ..... Phil

    Phil doesn't understand the autistic spectrum

    And he is himself in a constant state of rage.

    https://www.webmd.com/mental-health/what-is-intermittent-explosive-disorder



    --

    I yam what I yam - Popeye

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tabby@21:1/5 to palli...@gmail.com on Sun Apr 24 16:06:28 2022
    On Thursday, 21 April 2022 at 12:03:46 UTC+1, palli...@gmail.com wrote:
    Tabby puked another hair ball:
    ========================

    So now JL tells us he lines up a panel of * 5 smug autistics * like himself to interrogate and intimidate individual victims.
    What a living nightmare, Kafka would be impressed.

    Worst possible method of finding actually competent staff.
    Might as well flip a coin.


    1 2 1 interviewers miss a lot.
    ** Not if they are reasonably smart people and NOT austistic fuckwits like YOU.

    I've consistently seen that >1 people pick up on points than 1 alone miss. Reasonably smart does not mean nothing gets missed. (It's why we have teams.)


    You learn that from having multiple people interviewing.
    ** No you don't.

    FOAD Tabby

    Phil considers himself reasonable :)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tabby@21:1/5 to jla...@highlandsniptechnology.com on Sun Apr 24 16:08:51 2022
    On Thursday, 21 April 2022 at 15:07:14 UTC+1, jla...@highlandsniptechnology.com wrote:
    On Thu, 21 Apr 2022 01:22:07 -0700 (PDT), Tabby <tabb...@gmail.com>

    Phil doesn't understand the autistic spectrum
    And he is himself in a constant state of rage.

    https://www.webmd.com/mental-health/what-is-intermittent-explosive-disorder

    Yup. Not the only one on here.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to Tabby on Sun Apr 24 23:46:39 2022
    On Monday, April 25, 2022 at 9:06:32 AM UTC+10, Tabby wrote:
    On Thursday, 21 April 2022 at 12:03:46 UTC+1, palli...@gmail.com wrote:
    Tabby puked another hair ball:
    ========================

    So now JL tells us he lines up a panel of * 5 smug autistics * like himself to interrogate and intimidate individual victims.
    What a living nightmare, Kafka would be impressed.

    Worst possible method of finding actually competent staff.
    Might as well flip a coin.


    1 2 1 interviewers miss a lot.
    ** Not if they are reasonably smart people and NOT austistic fuckwits like YOU.
    I've consistently seen that >1 people pick up on points than 1 alone miss. Reasonably smart does not mean nothing gets missed. (It's why we have teams.)
    You learn that from having multiple people interviewing.
    ** No you don't.

    FOAD Tabby

    Phil considers himself reasonable :)

    I've had enough exchanges with Tabby to consider Phil's response to be perfectly reasonable in this particular instance. Sadly, Tabby seems to be unwilling to make himself scarce.

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Larkin@21:1/5 to All on Mon Apr 25 12:26:18 2022
    On Sun, 24 Apr 2022 16:06:28 -0700 (PDT), Tabby <tabbypurr@gmail.com>
    wrote:

    On Thursday, 21 April 2022 at 12:03:46 UTC+1, palli...@gmail.com wrote:
    Tabby puked another hair ball:
    ========================

    So now JL tells us he lines up a panel of * 5 smug autistics * like himself to interrogate and intimidate individual victims.
    What a living nightmare, Kafka would be impressed.

    Worst possible method of finding actually competent staff.
    Might as well flip a coin.


    1 2 1 interviewers miss a lot.
    ** Not if they are reasonably smart people and NOT austistic fuckwits like YOU.

    I've consistently seen that >1 people pick up on points than 1 alone miss. Reasonably smart does not mean nothing gets missed. (It's why we have teams.)

    We like to spend some time brainstorming with the applicant and the
    people he will be working with. A lot can get discovered, technically
    and otherwise. Why not?

    I wonder what it would be like to work for Phil.

    --

    If a man will begin with certainties, he shall end with doubts,
    but if he will be content to begin with doubts he shall end in certainties. Francis Bacon

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Larkin@21:1/5 to All on Mon Apr 25 12:28:23 2022
    On Sun, 24 Apr 2022 16:08:51 -0700 (PDT), Tabby <tabbypurr@gmail.com>
    wrote:

    On Thursday, 21 April 2022 at 15:07:14 UTC+1, jla...@highlandsniptechnology.com wrote:
    On Thu, 21 Apr 2022 01:22:07 -0700 (PDT), Tabby <tabb...@gmail.com>

    Phil doesn't understand the autistic spectrum
    And he is himself in a constant state of rage.

    https://www.webmd.com/mental-health/what-is-intermittent-explosive-disorder

    Yup. Not the only one on here.

    The world is becoming more tribal, for several reasons. That makes
    some people crazy.

    --

    If a man will begin with certainties, he shall end with doubts,
    but if he will be content to begin with doubts he shall end in certainties. Francis Bacon

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lasse Langwadt Christensen@21:1/5 to All on Mon Apr 25 12:33:59 2022
    mandag den 25. april 2022 kl. 21.28.35 UTC+2 skrev John Larkin:
    On Sun, 24 Apr 2022 16:08:51 -0700 (PDT), Tabby <tabb...@gmail.com>
    wrote:
    On Thursday, 21 April 2022 at 15:07:14 UTC+1, jla...@highlandsniptechnology.com wrote:
    On Thu, 21 Apr 2022 01:22:07 -0700 (PDT), Tabby <tabb...@gmail.com>

    Phil doesn't understand the autistic spectrum
    And he is himself in a constant state of rage.

    https://www.webmd.com/mental-health/what-is-intermittent-explosive-disorder

    Yup. Not the only one on here.
    The world is becoming more tribal, for several reasons. That makes
    some people crazy.

    https://youtu.be/sY5MmhLQBng

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Hobbs@21:1/5 to John Larkin on Mon Apr 25 19:27:33 2022
    John Larkin wrote:
    On Sun, 24 Apr 2022 16:06:28 -0700 (PDT), Tabby <tabbypurr@gmail.com>
    wrote:

    On Thursday, 21 April 2022 at 12:03:46 UTC+1, palli...@gmail.com wrote:
    Tabby puked another hair ball:
    ========================

    So now JL tells us he lines up a panel of * 5 smug autistics * like himself to interrogate and intimidate individual victims.
    What a living nightmare, Kafka would be impressed.

    Worst possible method of finding actually competent staff.
    Might as well flip a coin.


    1 2 1 interviewers miss a lot.
    ** Not if they are reasonably smart people and NOT austistic fuckwits like YOU.

    I've consistently seen that >1 people pick up on points than 1 alone miss. Reasonably smart does not mean nothing gets missed. (It's why we have teams.)

    We like to spend some time brainstorming with the applicant and the
    people he will be working with. A lot can get discovered, technically
    and otherwise. Why not?

    I wonder what it would be like to work for Phil.


    https://www.youtube.com/watch?v=lc4C7GC6MGE

    Cheers

    Phil Hobbs

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Larkin@21:1/5 to pcdhSpamMeSenseless@electrooptical. on Mon Apr 25 17:12:19 2022
    On Mon, 25 Apr 2022 19:27:33 -0400, Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    John Larkin wrote:
    On Sun, 24 Apr 2022 16:06:28 -0700 (PDT), Tabby <tabbypurr@gmail.com>
    wrote:

    On Thursday, 21 April 2022 at 12:03:46 UTC+1, palli...@gmail.com wrote: >>>> Tabby puked another hair ball:
    ========================

    So now JL tells us he lines up a panel of * 5 smug autistics * like himself to interrogate and intimidate individual victims.
    What a living nightmare, Kafka would be impressed.

    Worst possible method of finding actually competent staff.
    Might as well flip a coin.


    1 2 1 interviewers miss a lot.
    ** Not if they are reasonably smart people and NOT austistic fuckwits like YOU.

    I've consistently seen that >1 people pick up on points than 1 alone miss. Reasonably smart does not mean nothing gets missed. (It's why we have teams.)

    We like to spend some time brainstorming with the applicant and the
    people he will be working with. A lot can get discovered, technically
    and otherwise. Why not?

    I wonder what it would be like to work for Phil.


    https://www.youtube.com/watch?v=lc4C7GC6MGE

    Cheers

    Phil Hobbs

    I meant the other Phil of course.

    --

    If a man will begin with certainties, he shall end with doubts,
    but if he will be content to begin with doubts he shall end in certainties. Francis Bacon

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to John Larkin on Mon Apr 25 18:50:24 2022
    On Tuesday, April 26, 2022 at 5:28:35 AM UTC+10, John Larkin wrote:
    On Sun, 24 Apr 2022 16:08:51 -0700 (PDT), Tabby <tabb...@gmail.com>
    wrote:
    On Thursday, 21 April 2022 at 15:07:14 UTC+1, jla...@highlandsniptechnology.com wrote:
    On Thu, 21 Apr 2022 01:22:07 -0700 (PDT), Tabby <tabb...@gmail.com>

    Phil doesn't understand the autistic spectrum
    And he is himself in a constant state of rage.

    https://www.webmd.com/mental-health/what-is-intermittent-explosive-disorder

    Yup. Not the only one on here.
    The world is becoming more tribal, for several reasons. That makes some people crazy.

    Things like Facebook and Twitter allow people to be "tribal" with more people. The absence of face-to-face interaction takes out a number of constraints.

    The world is actually becoming more connected at levels above mere tribes, and has been since we invented writing, but the internet offers a lot more bandwidth than we ever had before, and a lot of the people who now exploit it haven't got the background
    with lower bandwidth remote communications to realise that they do need to reign in their immediate reactions.

    --
    Bill sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Hobbs@21:1/5 to John Larkin on Mon Apr 25 22:09:22 2022
    John Larkin wrote:
    On Mon, 25 Apr 2022 19:27:33 -0400, Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    John Larkin wrote:
    On Sun, 24 Apr 2022 16:06:28 -0700 (PDT), Tabby <tabbypurr@gmail.com>
    wrote:

    On Thursday, 21 April 2022 at 12:03:46 UTC+1, palli...@gmail.com wrote: >>>>> Tabby puked another hair ball:
    ========================

    So now JL tells us he lines up a panel of * 5 smug autistics * like himself to interrogate and intimidate individual victims.
    What a living nightmare, Kafka would be impressed.

    Worst possible method of finding actually competent staff.
    Might as well flip a coin.


    1 2 1 interviewers miss a lot.
    ** Not if they are reasonably smart people and NOT austistic fuckwits like YOU.

    I've consistently seen that >1 people pick up on points than 1 alone miss. Reasonably smart does not mean nothing gets missed. (It's why we have teams.)

    We like to spend some time brainstorming with the applicant and the
    people he will be working with. A lot can get discovered, technically
    and otherwise. Why not?

    I wonder what it would be like to work for Phil.


    https://www.youtube.com/watch?v=lc4C7GC6MGE


    I meant the other Phil of course.


    I knew that. ;)

    He and I bounce off things in different ways. I expect my approach is a
    bit more comfortable for most folks.

    Cheers

    Phil Hobbs

    --
    Dr Philip C D Hobbs
    Principal Consultant
    ElectroOptical Innovations LLC / Hobbs ElectroOptics
    Optics, Electro-optics, Photonics, Analog Electronics
    Briarcliff Manor NY 10510

    http://electrooptical.net
    http://hobbs-eo.com

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jlarkin@highlandsniptechnology.com@21:1/5 to pcdhSpamMeSenseless@electrooptical. on Mon Apr 25 19:43:27 2022
    On Mon, 25 Apr 2022 22:09:22 -0400, Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    John Larkin wrote:
    On Mon, 25 Apr 2022 19:27:33 -0400, Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    John Larkin wrote:
    On Sun, 24 Apr 2022 16:06:28 -0700 (PDT), Tabby <tabbypurr@gmail.com>
    wrote:

    On Thursday, 21 April 2022 at 12:03:46 UTC+1, palli...@gmail.com wrote: >>>>>> Tabby puked another hair ball:
    ========================

    So now JL tells us he lines up a panel of * 5 smug autistics * like himself to interrogate and intimidate individual victims.
    What a living nightmare, Kafka would be impressed.

    Worst possible method of finding actually competent staff.
    Might as well flip a coin.


    1 2 1 interviewers miss a lot.
    ** Not if they are reasonably smart people and NOT austistic fuckwits like YOU.

    I've consistently seen that >1 people pick up on points than 1 alone miss. Reasonably smart does not mean nothing gets missed. (It's why we have teams.)

    We like to spend some time brainstorming with the applicant and the
    people he will be working with. A lot can get discovered, technically
    and otherwise. Why not?

    I wonder what it would be like to work for Phil.


    https://www.youtube.com/watch?v=lc4C7GC6MGE


    I meant the other Phil of course.


    I knew that. ;)

    He and I bounce off things in different ways. I expect my approach is a
    bit more comfortable for most folks.

    Cheers

    Phil Hobbs

    You're just a big teddy bear.



    --

    I yam what I yam - Popeye

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Hobbs@21:1/5 to jlarkin@highlandsniptechnology.com on Tue Apr 26 10:12:13 2022
    jlarkin@highlandsniptechnology.com wrote:
    On Mon, 25 Apr 2022 22:09:22 -0400, Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    John Larkin wrote:
    On Mon, 25 Apr 2022 19:27:33 -0400, Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    John Larkin wrote:
    On Sun, 24 Apr 2022 16:06:28 -0700 (PDT), Tabby <tabbypurr@gmail.com> >>>>> wrote:

    On Thursday, 21 April 2022 at 12:03:46 UTC+1, palli...@gmail.com wrote: >>>>>>> Tabby puked another hair ball:
    ========================

    So now JL tells us he lines up a panel of * 5 smug autistics * like himself to interrogate and intimidate individual victims.
    What a living nightmare, Kafka would be impressed.

    Worst possible method of finding actually competent staff.
    Might as well flip a coin.


    1 2 1 interviewers miss a lot.
    ** Not if they are reasonably smart people and NOT austistic fuckwits like YOU.

    I've consistently seen that >1 people pick up on points than 1 alone miss. Reasonably smart does not mean nothing gets missed. (It's why we have teams.)

    We like to spend some time brainstorming with the applicant and the
    people he will be working with. A lot can get discovered, technically >>>>> and otherwise. Why not?

    I wonder what it would be like to work for Phil.


    https://www.youtube.com/watch?v=lc4C7GC6MGE


    I meant the other Phil of course.


    I knew that. ;)

    He and I bounce off things in different ways. I expect my approach is a
    bit more comfortable for most folks.

    Cheers

    Phil Hobbs

    You're just a big teddy bear.

    Well, I think of myself more in the "virile, dashing, and handsome"
    vein, but at this late date your characterization is probably closer to
    the mark. ;)

    Cheers

    Phil Hobbs


    --
    Dr Philip C D Hobbs
    Principal Consultant
    ElectroOptical Innovations LLC / Hobbs ElectroOptics
    Optics, Electro-optics, Photonics, Analog Electronics
    Briarcliff Manor NY 10510

    http://electrooptical.net
    http://hobbs-eo.com

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)