A new job

I started a new job on Wednesday. My last day at the old job was Tuesday. It would be nice to take a break between but somehow anyone who wants to hire seems to want you to start Right Away. Go figure.

It was a frustrating start, actually, because the new company was/is so brand-new that they didn't have office space, so I and the other 4 in Utah were working from home. (We signed a lease Friday so this should change next week.) (The 2 in California are working from home too but that isn't going to change any time soon.) I'm fine with working from home, but this is the week that our Comcast internet chose to go from "intermittently flaky" to "constantly flaky," where constant flakiness is "up for no more than 10 minutes at a time." When you're dealing with code repositories on VPN, not to mention all the googling that comes with (re)learning a new platform, this is a pain.

We actually got lucky (at least, this doesn't seem to be typical for interactions with Comcast) and the tech we got Friday fixed it immediately. Something to do with how the installer had wired up the line made the modem unable to keep a connection very long. Why it suddenly went from "annoying, but not annoying enough to spend enough time on hold to get a tech out to fix it" to "almost completely unusable," he didn't say. But it's definitely been stable since his visit so I'm inclined to think he knew what he was doing.

The relearning of Java has been a little stressful too. It's been 3 years and 2 major releases of Java since I really touched it at all, and neither of the two IDEs (and a third build system) are what I used before. But I've always been able to be immediately productive in a new environment before, so I've been feeling that pressure, at least from my self. Still, thinking it over, always before I've had the former maintainers of what I'm taking over available at least for my first couple days to answer questions. Although that's true here too, the man in question is (a) my boss and (b) horribly busy with everything else involved in running the new company, both of which make me a little hesitant to ask the sort of "stupid" questions I'd usually ask when starting out.