|
Blogchalk:
Portsmouth, NH, US
|
|
|
| |
|
Friday, September 13, 2002
|
|
Gotcha Again
I had to know for sure, but this seems pretty dumb. So if you write a few items and post but don't publish, they'll show up as unpublished. But as soon as you hit either Post or Publish, whamo! All your unpublished items get published. Really not what I expected. And not all that useful...
6:45:03 PM [ permalink ]
|
|
Gotcha
This is probably documented somewhere, but I just realized it.
I've got three buttons enabled, and I often post an incomplete item when I get interrupted in the middle of writing.
I learned tonight that you can have three unpublished posts and if you hit the "Publish" button while you're editing a post, you'll publish everything. I didn't expect this...
6:40:08 PM [ permalink ]
|
|
I hope I did this right
I said* that I love it. And then I was inspired to hack on a little extension. I've taken Garth's script and modified it to say "unpublished" if the post in question has not yet been published. Follow instructions here to make it work.
I've done very little Radio scripting, so this may crash Radio, melt your computer, or make your wife want to leave you. But if it doesn't work, please tell me so that I can (try to) fix it!
*Note that this link was creating using a backlink from the desktopHomePage. :)
6:16:55 PM [ permalink ]
|
|
Don't even think about trying to get a job without...
I just saw this article about a list of skills to have before even considering trying to get an IT job. Phil Wolff added:
Reminds me of this bit from Robert Heinlein's "The Notebooks of Lazarus Long", 1978, aphorisms from Time Enough for Love.
[ ... ]
I like that weblogs touch on the fullness of life. If only the hiring process did too. [a klog apart]
I am sufficiently inspired to make up a list for those considering working in the embedded space. This is on-the-fly, so feel free to suggest additions...
An embedded software engineer should be able to:
- use an oscilloscope, logic analyzer, and in-circuit-emulator,
- (bonus: use a soldering iron)
- read schematics,
- write a coherent specification,
- think on a whiteboard (in at least two colors),
- speak effectively to a room full of peers,
- avoid creating race conditions,
- analyze a program (not his own, of course!) to find race conditions,
- read two or more dialects of assembler, which implies that he can
- understand two or more CPU architectures,
- grok a data sheet,
- (bonus: understand verilog or VHDL; double bonus: fluency with verilog/VHDL and related tools),
- have intimate familiarity with the internals of at least one RTOS,
- fluency in two or more of: C, C++, Ada, assembler,
- know how to mix C and C++,
- know why mixing C and C++ can be a mistake,
- decipher an assembler dump, linker map, and other cryptic output,
- ...
Hmm. I think Phil is right. A list like this could make great feedback into the hiring process... asking a question like: "What would you add to this list?" could give you great insight into a prospective candidate.
7:38:50 AM [ permalink ]
|
|
|
© Copyright 2002 Brian St. Pierre.
Last update: 10/8/2002; 8:16:20 PM.
|
|
|
|
