News

My campaign to produce Shakespeare's Sonnets: A Graphic Novel Adaptation needs your help! Please sign up at https://www.patreon.com/fisherking for access to exclusive content and the opportunity to be a part of the magic!

I'm also producing a podcast discussing the sonnets, available on
industrial curiosity, itunes, spotify, stitcher, tunein and youtube!
For those who prefer reading to listening, the first 25 sonnets have been compiled into a book that is available now on Amazon and the Google Play store.

Tuesday, July 10, 2012

the end of the weekend

on saturday night, pg's parents dropped me off at home minutes before the first gaming guests arrived. we spent the next few hours on the roof, beginning with fluxx and going two rounds of thunderstone.

thunderstone: the randomizers were cruel, and we played with a couple who refused to plan their moves before their turn. the thing about thunderstone is you have everyone else's turns in which to figure out what steps to take. it was very frustrating.

on sunday, i woke up early to get some work done, then joined pg and her family at an italian restaurant (rustico) for a delicious meal to celebrate her father's birthday. then i was off to work.

i really didn't feel like going to work.

---

between azure's failings and git's, this week has been really shitty. i actually called the boss for a private meeting to explain to him that although there are many advantages to having moved to azure, it creates almost as many problems as it solves. every time we manage to make progress with one of their tools we begin to discover undisclosed caveats, and that's really not a good way to work.

as for git - it's supposed to be by software developers, for software developers. it appears to be geared more towards those masochistic asswipes who believe that gui's are for the weak and that we should never have devolved from coding in assembler. the idea of git is great, and the underlying design is excellent, but in practice it's a mess. there's nothing worse than having git identifying changes that haven't occurred and blocking (blocking!) synchronizing or branch switching until they've been committed. and you can't uncommit, and more and more frequently even committing isn't enough. i can't access code that's sitting on my own damned computer, and i can't share it, so what the hell is it good for?!

not as bad as clearcase, not nearly as good as svn. and i've now read all the documentation... i didn't learn anything helpful. just like everything else in the global code ecosystem: broken.

---

drinks on sunday evening at barbara frye (pg's friend's birthday) were late, and i woke up yesterday feeling the night before. i "worked" until git had me so upset that i couldn't focus, and then spent the evening / night getting started on one of my papers. seriously? the deeper i go into tropic thunder, the more dazzled i am. i can't tell how much is incidental and how much is sheer genius on ben stiller's part.

...

today was almost as bad as yesterday from a work perspective, but i managed to get a fix done in spite of azure's table storage issues and git. they were collaborating, i tell you!

the good news of the day:
1. i got a groovy grade for my french exam! i don't care how much of a curve they graded on, the important thing is that i don't have to take it again.

2. i just flipped my wheels, and it turns out that they weren't ground to the core - that was an illusion. only three were really shaved, so i've flipped them all around and they should be good even for another of the same :)

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.