Category: Job Experiences

Impressions after a few days at work

My office
Woo hoo, I have a job!

A few short impressions from 2.5 days of work:

  • The drive sucks. It’s about an hour and forty minutes each way, and today it was snowing so it was a bit longer. I’m going through a tank full of gas every two days, which even with a Prius seems expensive. They told me in the interview I’ll be able to start working from home soon, so I’ve got to get that set up.
  • The construction trailer I work in sucks. I sit next to the door, and it’s cold and drafty, even when people remember to close it behind them. Right behind me is a meeting room with paper thin walls where everybody uses the speaker phone. Worse still, the heater outlet is there so most times when the meeting is on, people turn off the heater. If we’re lucky, they remember to turn it back on afterwards, but yesterday we didn’t discover that nobody had turned on the heater until my toes were about to drop off.
  • My computer has two screens. I had two big screens when I was at Kodak, and I’d forgotten how useful that is when you’re programming to be able to devote an entire screen to Eclipse while you used the other window for running the app, as well as other web browsing and the like. As soon as I have my first paycheck, I think I’m going to buy a cheap LCD panel for my home office.
  • The pace is hectic. My supervisor never has time to show me anything, but he’s expecting results immediately. That can be frustrating. On the other hand, it’s good to have something to do and a project where things actually happen.
  • They wrote their own web framework. As if the world doesn’t have enough Java web frameworks, they wrote their own. And it has its good points and bad points. Each page starts with an XML page description document and an XSLT document. But it’s not what you think – the XSLT document doesn’t process that page description document. Instead, the page description document specifies the Java beans that either produce or consume nodes in a different XML document, which the XSLT document then processes into an HTML page. The forward and back buttons on the browser don’t work on many of their pages, for reasons I don’t entirely understand yet. They use Javascript a lot. I’m going to come out of here with a lot of experience in XSLT and JQuery, I hope.
  • The company seems equally split between people who are friendly and helpful, and people who refuse to look up when you speak to them. Fortunately it appears I’m mostly going to be working with people in the first category.
  • I’m genuinely getting a good feeling about working here. It’s such a refreshing change from the place I worked last winter.

A tale of two government documents

Spoiler alert: I’ve got a new job. Woo hoo! I start on Monday.

When I got my citizenship, they took away my high security Permanent Resident Card (“green card”) and gave me this fancy paper “Certificate of Naturalization”. At the ceremony, they told us that we should apply for passports immediately because the “Certificate of Naturalization” isn’t good for travel, but you had to send in the “Certificate of Naturalization” with the passport application as proof of citizenship and identity. Well, I had to travel to Ottawa for a kayak race the very next day, and so I kept it. And it worked for a couple of trips to Canada. I was expecting to get a new job any day now, so I kept the document so I’d have proof of citizenship when the time came.

Well, it wasn’t “any day now”, but I eventually got a job, and I had to fill out the I-9, which is your proof of eligibility for employment in the US. And that’s when I discovered that the list of documents that you’re allowed to use for proof of citizenship and/or identity doesn’t include the “Certificate of Naturalization”. I even downloaded the M-274, which is the guide for employers for filling out the I-9, hoping to find they just omitted it for brevity on the I-9 itself. No dice. And searching the Citizenship and Immigration Services web site shows that in 2007 they purposely disqualified this document because it wasn’t secure enough. For some strange reason, older citizenship documents, that unlike mine don’t even include photos and look like they were banged out on a crappy typewriter, are still valid. The document also said that you can use your Social Security card as proof of eligibility, but mine dates back from when I was here on a TN-1 temporary non-resident visa, and so it’s stamped on the front “Not Valid For Work Without INS Authorization”, so I figured it was not valid, and so I thought I was screwed.

After worrying about it all night, I had a meeting with the HR person at the company that placed me, and she basically said that the Social Security card would be valid, because the condition on it was no longer in force. So we filled out the I-9 and she thinks everything will be fine. But just in case, I sent off my passport application the very same day so I’ll have that if any questions are raised.

But here’s the thing that I think is really stupid: the Certificate of Naturalization isn’t a valid document for proving your citizenship to work even in conjunction with other documents, but it is valid for proving your citizenship and identity to get a passport, and a passport is a valid document for proving your citizenship and identity to work. Hopefully the reason is that the passport people do some sort of verification or validation that the people who process I-9s do not or cannot. Otherwise it’s just stupid. Coupled with the fact that a fairly fancy document like the Certificate of Naturalization has been disqualified because it’s not secure enough, while primitive documents like the Social Security card and older citizenship cards are still accepted, smacks of “Security Theatre”.

Reading Comprehension 101

After updating my resume on Monster the other day, I got an email today:

We found your resume and are very impressed! We believe you have the qualifications we’re looking for to fill our open insurance agent position.

Somehow I think they stopped reading my resume after they found my email address and postal address (because they did say they were representing the Rochester branch). Other than those two items, I can’t think of a single thing in that resume that would make some think I’d be willing to be an insurance agent. I think I’d rather live under a bridge.

Today in job requirements FAIL

I got a call from a recruiter asking if I had experience with “ETL”. I’d never heard of it, so I truthfully said no, I had no idea what it was, and she went away.

After the call, I looked it up. Evidently it stands for “Extract, Transfer and Load”. Isn’t that what 90% of computer programs do? Isn’t that what the programs I’ve written and maintained for the last god-knows-how-long to extract aviation data from various sources in various formats, transfer it into my own format (combining data from several different places into one semi-coherent whole, throwing away the data that doesn’t interest me), and load it into my database for future use does? Or when I took data from Island and RediQuote and massaged it so that it looked like what SunGard’s trading system was expecting so that SunGard UMA users could trade stocks on them? Or when I converted data from the SMPTE ShowPlayList schema and stored it into our database so we could schedule movies and disassemble and re-assemble our own concept of what a show schedule was?

So yeah, I think I understand the concepts behind “ETL”. But because I was honest to a recruiter, I’ll probably never get a job doing it when it’s called that. The problem with the whole job market is that it’s full of cases like that, where recruiters and HR departments have a checklist and are just looking for people with the right keywords on their resume. That’s why I hope that careers.stackoverflow.com and jobs.stackoverflow.com catch on with Rochester companies, or companies who understand that off-site doesn’t necessarily mean the sort of idiots you see on Rentacoder who think they can solve the Halting Problem for $500.

My situation in a nutshell

http://finance.yahoo.com/career-work/article/107267/pay-cut-cities.html

“Higher-wage people are likely being laid off to a greater degree than lower-wage people, or moderately high-wage workers are being replaced by temps or contractors who are paid less,” says Wial.

The picture is even worse in upstate New York, where average wages fell 2.3% in Rochester and 2.2% in Syracuse.

Shit, I’m never going to get a job that pays what I’m worth, am I?