Joe Auricchio

My job search has been concluded

I’m looking for a full-time engineering job, starting in January 2012, in San Francisco (or reachable from there with shuttle/pubtrans). ¹

I work on low-level software and high-level hardware. I make the inside guts ugly so the outside product can be pretty. Then I make the inside pretty too. I’m allergic to bad design and to development cultures that don’t discourage it.

I don’t believe that “done is better than right”. I believe that doing it the right way is a worthwhile goal in itself, and anyway it’s usually the easiest and fastest way in the long run. Nobody ever lined up at 6am to buy the cheap 50% solution.

Here is my resume.

You should hire me:
… If you need someone to look simultaneously at several layers of your stack (hardware, firmware, bus, driver, application) and look for inefficiencies (“opportunities”),
… or to look simultaneously at several layers of your stack and tell you why they’re not working together.
… If a well-meaning director handed you a two-page project plan lacking details and illustrated only with a few comically simple box-and-arrow diagrams, then asked you to please “Build this. It’s just a couple of processors and an FPGA, it shouldn’t take too long, right?”
… and the hardware group laughed when you asked if they could spare an engineer this month.
… If sometimes the kernel panics with some message about skb buffer underrun and you think it’s a bug in your driver but you can’t quite track it down.
… If you’ve heard dark whispers that the C preprocessor can do ever so much more than simple inline functions, and you want a guide into the mysterious realm of generated code.
… If the local security wizard walked by your office last week, paused, scrutinized your whiteboard diagram, pointed at one ordinary-looking box, muttered “Yeah, you could get 0wned through there” to herself, and walked away. You don’t know what to do now.

Update 19:05 12 Sep: Resume and contact info added.

Scott liked my terminal style from yesterday, so I’ll reprise it.

heian:<<<umi-misc/pubkeys$ ssh cse125@neathat.com -p 14522 sudo ls \>/dev/null
[sudo] password for cse125: (echoed, which is unfortunate)
heian:<<<umi-misc/pubkeys$ cat djc_hmac_rsa.pub | ssh cse125@neathat.com -p 14522 sudo su -c \'cat \>\> ~djc/.ssh/authorized_keys\'
heian:<<<umi-misc/pubkeys$

Now DJ can use his key on that server.

The sudo ls is to enter the password and get the sudo authorization ticket. We can’t enter the password with the cat, because ssh sees its stdin isn’t a terminal and refuses to allocate a tty. A stupid workaround would be (echo "mypassword"; cat ... ); | ssh ..., but I like the two-phase solution more, for some reason.