bendingoutward @bendingoutward@mastodon.social

It's not every day that I mouth off at "uncle bob" on the birdsite, but when I do, it's today, and I use his claim to fame to do so.

Hey, anybody interested in roleplaying as a grandparent while reading the relatively short doc that I've just written for one of my projects? #halp

So ... acknowledging that test coverage is a bit of a nonsense metric, is anybody else incredibly interested in getting different metrics for, say, integration suites vs unit suites for Go stuff? #golang

And typos are the reason that one shouldn't release when one is stupid tired. Just pushed v1.0.1 to take care of a typo that broke the everything.

Hey folks! I finally got around to pushing a 1.0.0 release of this thing that I've been working on.

As https://github.com/DATA-DOG/godog is a pretty decent Cucumber implementation for #golang , I've found myself desperately wanting a reasonable Aruba implementation.

To that end, if you feel the same way and want to write awesome integration tests for your CLI Go apps, please do check out https://github.com/ess/jamaica (or read about it at http://ess.github.io/Jamaica/ ).

I've been beaten half to death by PEBCAK issues so far today. The problem is that the day isn't even half over.

After a whole lot of fighting and growling and rawhides, I think I've finally tamed #godog and should see about releasing my related support packages.

After the wounds heal, anyways.

Say you're using a tool to power cut a server. One step in the process is to run an external script that stops volatile processes on the server before the power cut. What do you do if that external script returns an error?

It's amazing to see a multi-day music festival with a name like "Common Ground" be so heavily genre-segregated per day.

"Perhaps this is why we don't do off-sites anymore. There is no single geographic location that has enough liquor."

Well played, kid.

Say I've thrown together a couple stupidly tiny godog-related #golang packages to help organize step definitions and implement a minimal aruba-like thing. Release 'em all official like, or just use them?

I'm desperately searching for a new gig, but not yet desperate enough for roles at knowingly toxic companies.

So, I suppose that's an upside.

"I'm going to die some day, and it will most likely happen while contemplating exactly where we went wrong as a species while reviewing somebody's code."

It's a good day when I get to toss out Joe Dirt quotes in quasi-official conversations about the employer's aging PaaS offering.

Happy holidaze for #420day folks. I can't join you directly, but there may have been extra bourbon-space in my afternoon coffee.

(Or, rather, novelty instruments of all manner.)