Life Update

You may have noticed that the blurb about me has changed slightly. My career status has been in flux over the last few months, but has now settled. Back in January the project I was working on at HP was canceled. My rather large R&D lab was told that we no longer had work to do. Our only job was to find another job. The upper managers would try to find spots for us on other projects within HP, but we were basically told to not hold our breath. So I didn't. I updated my resume and went to work. I interviewed with an interesting company located about an hour away from my home, up the Columbia Gorge, named Insitu. They were (and still are) busy interviewing and hiring many people and it took a while to hear back from them. In the meantime I was offered another position at HP. Not having anything else firm, I accepted. I quickly learned that it was a .NET/C# windoze programming position. No more playing with hardware, no more bit twiddling register manipulations, no more ISRs, no more using an oscilloscope to debug my code. I was sad, but I tried to have a good attitude. C# has some interesting things about it, right? Well, when I heard back from Insitu with a job offer to do embedded software, it was very tempting. When I considered more interesting work at a place that is hiring and growing rather than laying people off, the choice seemed pretty clear. The big downside is that 1 hour commute each way. HP was only 5 minutes away. I could move my family to White Salmon and get the same commute, but we aren't there yet. And so I drive. And listen to books on CD. It's not too bad. The work, and work environment, is just about what I imagined it would be as well. Upbeat, excited, and employee friendly. I have hardware on my desk again, and they even bought me a pair of ESD safe shoes.

Comments

ashawley said…
Piece of mind is the most important quality of a job. Congratulations!
May 6, 2009 at 6:23 AM
Post a Comment

Popular posts from this blog

SystemVerilog Fork Disable "Gotchas"

This is a long post with a lot of SystemVerilog code. The purpose of this entry is to hopefully save you from beating your head against the wall trying to figure out some of the subtleties of SystemVerilog processes (basically, threads). Subtleties like these are commonly referred to in the industry as "Gotchas" which makes them sound so playful and fun, but they really aren't either. I encourage you to run these examples with your simulator (if you have access to one) so that a) you can see the results first hand and better internalize what's going on, and b) you can tell me in the comments if this code works fine for you and I'll know I should go complain to my simulator vendor. OK, I'll start with a warm-up that everyone who writes any Verilog or SystemVerilog at all should be aware of, tasks are static by default. If you do this: module top; task do_stuff ( int wait_time); #wait_time $display ( "waited %0d, then did stuff" , wa
Read more

'git revert' Is Not Equivalent To 'svn revert'

I just learned that if you have some changes in your working tree that you want to get rid of, you don't type 'git revert' like you might guess. No, that's what cvs, subversion, mercurial, and bazaar (to name a few) use revert to mean, but not git. With git, revert is used to undo actual commits. Thankfully, you can undo your revert with another 'git revert', I just learned. So let me repeat to be clear, if you have changes to your working files that you want to abandon, DO NOT do this: git revert HEAD That will undo your last commit. Do this instead: git reset --hard HEAD I'm glad I have that straightened out now. I'm wondering if /etc was really a good place for me to start out playing with git. UPDATE: Nearly two years later and I'm still getting comments on this. I'm glad I've been able to help people out this way. The discussion in the comments is good, and one thing I'd like to point out is that I now always use
Read more

Git Rebase Explained

Image
Introduction Rebase is a helpful git command that can be used to turn a branchy two-headed version history into an easy to follow linear one. A linear history is much easier for a human eye to follow and a human brain to understand. Rebase is a very safe command to use, despite some fear that people have about it. This post should explain how rebase works and clear up any misunderstandings about it. Rebase Basics The short summary of rebase is that it cuts commits out of the git history and reconnects them somewhere else. Let's say the common scenario comes up: you commit a change to the main branch of a repository, you then run  git fetch , and in come a couple changes that other people made on the main branch. If your commit is version 46f and the others that just came in on the fetch are versions ef9 and 4a2, your version history might look like this: The main branch now has two heads, 46f and 4a2. You can run  git rebase  to disconnect your commit from version d88 and connect i
Read more