Hoppip Hurray

"Burga-Dots"--Wednesday, 4/26/17

I had not tried wearing the burgundy skirt with the multi-red-shade polka dot blouse before, but I think it worked despite the burgundy dots being a much deeper hue than the skirt.  But then the scarf was an even darker burgundy color, which I think helped my cause slightly as the outfit is more clearly a melange of many burgundy-like colors, not the pairing of two mis-matched ones.  Or that's my hope.

Black/burgundy/red polka dot blouse (thrifted, Notations), $1.05/wear
Burgundy skirt (Nordstrom), $1.78/wear
Black tuxedo jacket (thrifted, Chico's), $0.56/wear
Black tights + black ankle boots by Sam Edelman, $1.63/wear
Burgundy scarf (Payless), $2.26/wear

Outfit total: $7.28/wear

This Florida white is like, Hmmm, there is something odd about your outfit, but I'm not sure what it is.  Oh well, silly humans, whatever.

I would have gotten more caught up on outfits this evening but I'm now also behind on downloading and editing photos from my camera, and while my headache is only about half as bad as it was at work today, that's still enough that I don't feel like dealing with all that.

Today I finally finished a project working with HR data that has required about 6 different attempts by my HR contact to get the data I actually need.  I don't blame her for that, really; neither of us really knew the data well enough (me, almost not at all) for her to get it right the first time.  It was kind of interesting to work my analyst muscles against this novel opponent, who was something of a shape shifter (the data, not my friend in HR).  When I delivered the spreadsheet to my co-worker this morning (who is working directly with our client in another department), she was thrilled because it turns out that the client has a big meeting on Thursday which this report will be perfect for.  (To the credit of both my co-worker and the client, neither were pressuring me or even told me about the meeting in advance because they knew that HR and I have discovered a gazillion issues to resolve in turning the pay roll data into useful information, they knew I was working on it assiduously, and they had accepted that it would take as long as it would take.)

This month is promising to be the busiest one I've had in a while.  In addition to a couple of major once-a-year projects and several brand new things coming up, people in other departments are realizing, "Oh wait, it's getting close to the end of the year (June 30) so we should get Sally busy working on things with that funding we've allocated to her."  I knew this would happen, and so far, it's looking manageable.  But I am definitely feeling myself straddling that line between "busy enough to be maximally productive" and "waaaaaaaah too much!"  I think I will be back on the busy-without-panicking side of things by the end of the week because I have a project I'm starting on in the morning that seems daunting but I've done several times now, so I've worked out the basic process (which is pretty well documented) and have written a lot of code that I will be able to use with minor tweaks.  I mean, it's different every year in ways that aren't predictable, but I'm familiar enough with the data and with the range of issues that can arise with it that I don't expect it to be that tricky.  I think I will basically zoom through it and produce a bunch of reports by the end of the week, which will be an invigorating and hopeful experience going into the completely unfamiliar territory that next week holds.

This post is brought to you by Hoppip...who is NOT the same as Hiphop the cartoon rabbit that I can't find on the Internet [wha?] (Robert bought me a pail featuring this character at Goodwill and it's perfect for keeping my medications in) or Hip Hop the sports ex-mascot I had never heard of before.

"This Pokémon drifts and floats with the wind. If it senses the approach of strong winds, Hoppip links its leaves with other Hoppip to prepare against being blown away."