5 ms·
Julia's articles are an excellent reminder of all the great stuff I take for granted. I learned much of this stuff on the job and I only wish that I had easy-t
by wyldfire 9y ago
Julia's articles are an excellent reminder of all the great stuff I take for granted. I learned much of this stuff on the job and I only wish that I had easy-to-digest articles like these to read early on in my career. Especially if you are writing high-level application software, this is great info to help you understand what's happening below.
> “level-triggered” vs “edge-triggered” ... I’d never heard this terminology before (I think it comes from electrical engineering maybe?).
This is IMO easiest to understand when using a logic analyzer or an o-scope. Often you want to see what condition the system was in right when something interesting happens and you can either detect a pulse (like from a momentary button, e.g. elevator call button) or a level change (like from a pole/knife switch like a room's light switch). Also, if you've programmed interrupts before you'll need to understand this distinction.
- vram22 9y ago> > “level-triggered” vs “edge-triggered” ... I’d never heard this terminology before (I think it comes from electrical engineering maybe?). Yes, me neither, but my guess is comes from the level or edge of a square wave, respectively. https://en.wikipedia.org/wiki/Square_wave https://en.wikipedia.org/wiki/Square_wave