Back to work
Wednesday was a bit of a slog. I managed to haul my arse out of bed, get in a short walk, and get to work a few minutes early. The first thing I did was update the damn DVD insert for the Japanese team. Yeesh. Then, when I got to my first meeting, things were on fire. The Japanese translated Help had come back, and how were we going to get it into the product? *facepalm* You mean nobody planned this out how we were going to change the installation folder structure and nobody created folders in source control and we haven't changed the Help URL yet? Argh. So I got the QA Manager started on that. He has more experience with Git than I do, and he's in charge of building the installers. Once we got the Help in, the UI developer would update the Help URL so it called the right language.
The rest of the day felt like putting out fires. The usual morning sucking meetings. Quick check in with HR (we still haven't made an offer yet, still checking references). Digging out from under my e-mail inbox. Reviewing (and formatting) two separate documents for developers. And then Git.
When I left the office on Thursday I was trying to check in changes to Git, but kept getting a variety of different error messages. I got friendly QA guy to help with this. And he couldn't get things to work either. It looks like there are a handful of files where the file name is too long for Windows to handle. Apparently if you're working in the development tool, it can handle the incredibly long paths (I couldn't even get a screen shot of the error message, they were so long that they went off the screen). I just want to know WTF developers, WTF? Even *I* know you need to keep folder and file names short. What's up with burying things inside 10 or 15 folders with long names? Git can't download/update those files, and it won't let me do anything else until it gets those files and is happy.
So we're going to try installing another tool and see if that allows me to update my project or not. If not, I have no idea what I'm going to do.
Came home and pretty much collapsed. Is it Friday yet?
The rest of the day felt like putting out fires. The usual morning sucking meetings. Quick check in with HR (we still haven't made an offer yet, still checking references). Digging out from under my e-mail inbox. Reviewing (and formatting) two separate documents for developers. And then Git.
When I left the office on Thursday I was trying to check in changes to Git, but kept getting a variety of different error messages. I got friendly QA guy to help with this. And he couldn't get things to work either. It looks like there are a handful of files where the file name is too long for Windows to handle. Apparently if you're working in the development tool, it can handle the incredibly long paths (I couldn't even get a screen shot of the error message, they were so long that they went off the screen). I just want to know WTF developers, WTF? Even *I* know you need to keep folder and file names short. What's up with burying things inside 10 or 15 folders with long names? Git can't download/update those files, and it won't let me do anything else until it gets those files and is happy.
So we're going to try installing another tool and see if that allows me to update my project or not. If not, I have no idea what I'm going to do.
Came home and pretty much collapsed. Is it Friday yet?