@fennec said:
It has an interesting idea of the geography, though.So now I know what the recruiting agencies are using when they see my resume (saying I'm looking for San Francisco Area) and they tell me about this wonderful gig in Houston, TX.
@fennec said:
It has an interesting idea of the geography, though.So now I know what the recruiting agencies are using when they see my resume (saying I'm looking for San Francisco Area) and they tell me about this wonderful gig in Houston, TX.
@joe.edwards said:
My last job tasked me with building a LMS. By myself. From scratch. In a month and a half. I told them it would take a year. They said get it done in a month and a half. The specs filled a 3-ring binder to overflowing.
Ah. So you had to write something using SCORM? I ended up doing 6 months of work during weekends since my regular stuff couldn't be deferred. Came out to something like 300+ hours. 3% bonus.
Wait... They don't want an expert in Go?
I call shenanigans.
When I worked for one of the Local University IT departments, they did a slightly different version of that. Every year, they brought x/3 new machines at the high range level, although not bleeding edge. If you're machine was one of the oldest 1/3, you got a new machine. If you just started the job, you also got one of the old machines, but that put you in the running for a nifty new machine within a year.
So, yes, you had that "Oh, geeze, I have to redo my machine" in less than a year, but then you had a nice machine that slowly became an ok machine for three years, and then the cycle repeated itself with a nice machine.
@locallunatic said:
OK, now the important question: how did you avoid assault charges when finding a teammate did what you describe?
Make sure the body is never ever ever found.
So... My '3 minutes' of work experience should put me in the running?
I actually did 9 years, but those days are long behind me now.