 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> And here I was thinking that all the components are microscopic...
>
> Err no, each component is roughly the same size as the display itself.
> eg for a typical 2.0" phone display each component is going to be the
> same order of magnitude. Of course the electronic circuits that are
> actually on the glass panel itself are too small to see, for the
> electronics guys (yes we only get male applicants) we just show them
> some simplified circuit diagrams of important stuff, showing them the
> transistors under a microscope wouldn't be too helpful.
Yeah, but, I thought it contains stuff like a half-wave plate (which is
nanometers thick) and stuff.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
scott wrote:
>> ...OK, how many other people here felt an irresistablel urge to try to
>> answer all of those?
>
> I could answer the first one :-D
A better question might be "why do they call it a relational database?"
So many people get that one wrong...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
scott wrote:
>> Real coders define a continuation monad who's operators are all ASCII
>> art, and generate spaghetti code using an epimorphism over
>> endofunctors. Deobfuscate THAT! O_O
>
> We had a function called Viagra in our code. It was called every second
> to check if the lifting arm on our robot was still in the fully raised
> position, and if not activate the motor until it hit the limit switch.
GEEK HUMOUR FTFW!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Yeah, but, I thought it contains stuff like a half-wave plate (which is
> nanometers thick) and stuff.
Actually the half-wave plate (or quarter-wave plate) is part of the
polariser sheet (which contains lots of other layers), these are typically
0.2-0.4mm thick and can easily be seen attached to both sides of the glass.
We expect most candidates to at least have a very basic idea how an LCD
works (we tell them this before the interview).
Other optical sheets in the backlight, like the diffuser and prism array
sheets are thinner, but still easily visible and handle-able as they are all
the same size as the display itself. In fact you can run your finger nail
along the sheet to see if has any prism structure on it, you could probably
work out the spacing of the prisms from the pitch of the sound somehow
without the need for any microscope. Also there is another sheet in there
that just looks like a mirror, but obviously it doesn't reflect all the
light or the display wouldn't work. THat's another good one to ask them
about.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> Real coders define a continuation monad who's operators are all ASCII
>> art, and generate spaghetti code using an epimorphism over
>> endofunctors. Deobfuscate THAT! O_O
>
> I'd first need to deobfuscate your sentence :-P
Trust me, if I had the time and energy, I could probably come up with
something horribly contorted in Haskell.
1. It lets you define functions with names like **_<#_^_#>_**
2. It lets you write lines of code and automatically inserts hidden
function calls between them.
3. It allows functions to construct other functions.
Need I continue? Suffice it to say, you could do some seriously messed
up stuff with this puppy...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible schrieb:
> TLB - convert from virtual memory addresses to physical memory
> addresses. It's basically a cache of the page mappings. (Let's face it,
> accessing RAM for every memory access to figure out where in physical
> memory the requested virtual address is would be *really* slow...)
Ah yes - those animals. I knew I had read about TLBs somewhere somewhen.
> I only know this because I read the Intel reference manuals. For no
> reason other than curiosity.
Did that, too - but that's probably about a decade ago, and apparently I
never really needed that stuff :-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
scott schrieb:
> We had a function called Viagra in our code. It was called every second
> to check if the lifting arm on our robot was still in the fully raised
> position, and if not activate the motor until it hit the limit switch.
LOL! Talk about self-explanatory identifiers :-P
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> I only know this because I read the Intel reference manuals. For no
>> reason other than curiosity.
>
> Did that, too - but that's probably about a decade ago, and apparently I
> never really needed that stuff :-)
I was trying to build a new OS, remember? :-}
(Warp's assessment was correct - I never got past a boot loader that
didn't actually load anything.)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymous org> wrote:
> Invisible schrieb:
> > TLB - convert from virtual memory addresses to physical memory
> > addresses. It's basically a cache of the page mappings. (Let's face it,
> > accessing RAM for every memory access to figure out where in physical
> > memory the requested virtual address is would be *really* slow...)
> Ah yes - those animals. I knew I had read about TLBs somewhere somewhen.
Same here: I knew the concept existed, but the I was not so familiar
with its *name* that I could make the connection.
Which makes the question maybe a bit unfair: Even if the person does know
what it is about, if he can't remember it from its name, it will look like
he doesn't know about that subject at all.
Besides, in which job would it be necessary to know this?
Unicode encodings? Certainly useful to know. Basic SQL knowledge? Can
become handy sometimes even in jobs not directly related to databses.
Knowing what a TLB is and how it works? Exactly where do you need to know
that? It's not like knowing that would change the way you develop programs.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>>> TLB - convert from virtual memory addresses to physical memory
>>> addresses. It's basically a cache of the page mappings.
>
>> Ah yes - those animals. I knew I had read about TLBs somewhere somewhen.
>
> Same here: I knew the concept existed, but the I was not so familiar
> with its *name* that I could make the connection.
>
> Which makes the question maybe a bit unfair: Even if the person does know
> what it is about, if he can't remember it from its name, it will look like
> he doesn't know about that subject at all.
>
> Besides, in which job would it be necessary to know this?
>
> Unicode encodings? Certainly useful to know. Basic SQL knowledge? Can
> become handy sometimes even in jobs not directly related to databses.
> Knowing what a TLB is and how it works? Exactly where do you need to know
> that? It's not like knowing that would change the way you develop programs.
Well, I guess the idea is that by asking *lots* of [admittedly fairly
arbitrary] questions, you get some idea of whether the person in
question knows anything.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
