Losing ground

Yesterday morning I finished my first assignment for work; at least I thought I did.  Late this morning I actually got a chance to go over it with people who have been there a while, and it turns out that no, I didn’t.

Some of it is pure detail; I’m used to working in a small shop, so my issue notes were the kind of thing I’d write to myself.  This is fine for me, but since someone else will be taking my notes and going through them to determine what exactly to fix, it isn’t actually very useful.  I managed to rework most of those, and I think the new versions are actually pretty helpful.

Some of it is the hours- and document-tracking software, and that bit was mostly a case of straightening out what should and shouldn’t be done when and where.  Practically speaking, not too bad since I hadn’t had a chance to get formal training.

Some of it is… well.  I look at the work, and I can’t shake the feeling that I’m missing something huge.  I don’t know what it could be, and since the coworkers and supervisors who looked at it don’t seem to have found it I’m not sure it’s a warranted reaction, but it’s very hard to get rid of.

Plus?  It’s code.  So I get sucked in, and I didn’t actually make it outside today.  With the time change, it means Im getting out after dark, and it throws me for a loop.