I finally broke down an bought a second USB-C charger for my MacBook Air, to leave in my office.

I got one with a bunch of USB-A ports as well, so now I can stop plugging those single-port USB chargers into every available outlet in my office.

Neurodiversity and the Essence of DevOps - Jeff Sussna - DevOpsDays London 2018

This is one of the things I really like about DevOpsDays in general. The tech is usually part of the discussion about enabling us to get our work done - but at its core, the DevOps ideology is about making better connections between people.


when you think about it, the idea that software should scale is actually really weird. "sure this garden is nice, but how nice can it be if it doesn't grow to cover the entire surface of the earth?"

"It's not a security issue, it's an availability issue"

*long sigh*

This is your periodic reminder that all the stuff you know and take for granted, is new and amazing to someone.

This toot inspired by #parenting and #coding both.

Not sure how I talked Philadelphia's Morris Animal Rescue into letting me name some of their kittens with a neural net. They did reject some names.

Got this awesome t-shirt from @bobbytables@twitter.com at .

We had a chance to chat over lunch and I really love the idea of what he’s working on at firehydrant.io - I was thinking this is something I’d love to have for our team after last year’s talks on incident response, and they’ve gone and built it.

I started reading “Making Work Visible: Exposing Time Theft to Optimize Work & Flow” by Dominica DeGrandis yesterday.

The production quality of this book is excellent. One of those things I really appreciate in a book. 👍

I missed Dominica’s talk at , but managed to catch her Open Spaces group discussion on Value Stream Management.

I grabbed some follow-up reading from the two Open Spaces on that topic.

I picked this one cause I’m in that room. 😄

I’m terrible at live updates at conferences. Can’t even keep up texting my wife never-mind writing to the world.

RT @SteveElsewhere@twitter.com

We don't let our servers get to 100% utilization, why would we want that for our people?

Headed to in Toronto for the next two days.

I really enjoyed last year’s event, and for the second year in a row, I get to cheer on a team member for their presentation.

Last year it was our co-founder/CTO. This year it’s our newest team member.

I’m mostly writing python code this weekend. Working on the Ansible side of my Terraform Dynamic Inventory.

I did some heavy refactoring toward a more object-oriented model. Now I’m working on a feature to add a “merge priority” setting, so that it can more intelligently more cars dictionaries from overlapping inventory definitions.

This is probably a feature that only I care about... but I think it’ll handle some edge cases where people might get hung up adopting this integration.

Playing the part of both parents today. Not much sleep, but I totally had lunches packed by 6am with coffee in hand and a few minutes for a little Minecraft before waking the kids.

Now their up and they play Minecraft while the other takes a turn in the shower. 🥰

If it doesn’t get merged, I guess I’m back at square one with my syntax highlighting for HCL (Terraform Configuration) in my docs. I can always work around it by building locally and pushing the generated code, but that just ruins the magic of the gh-pages branch.

I just submitted a PR to the github-pages gem to update to rouge v3.3.0, catching syntax highlighting for it up for nearly 2 years of changes to rouge.

The tests passed, so hopefully it goes through. It was pretty trivial for my part... I just connected the dots from other people’s comments on a PR with failing tests and submitted my own PR based on that suggestion.

How does something so small hold back updates to a project that supports over 100,000 docs pages and blogs?

Did a bit more work on my Terraform Provider for Ansible. Did my best not to bite off more than I can chew feature-wise for this long weekend, leaving it totally functional but not as complete as I wanted to.

Kind of glad I limited the scope of the actual feature to leave part of it for another weekend, because I realized after some release chores to make the feature available publicly that I didn't account for time to spend on documenting this new feature. 🤦‍♂️

I played around with my wife's Wacom tablet in Adobe Illustrator last night.

I sometimes enjoy doing a little doodling - but I also walk away from the experience with a profound sense that other people's talents often make their jobs look easier than they are. It's good to take a moment to appreciate people for the awesome work they do, that I could not.

Anyone can do almost anything with enough practice and effort. But there's only so much practice and effort that one can fit in a lifetime.

The idea was inspired in part by Greenkeeper, which can be used to keep NPM dependencies up-to-date.

I wonder how they handle this.

Granted, that’s a whole product unto itself that needs to handle more edge cases than my little special-purposed idea. Probably better just to build PR or branch names in a consistent manner so they can be parsed back to check if it has already been handled.

I suppose I could keep a database of which roles had what PRs already opened, but that seems like a lot of needless overhead. Perhaps there’s a way I could use the branch name or PR title to keep track of whether a PR was already submitted for the same version change.

Show more
Infosec Exchange

A Mastodon instance for info/cyber security-minded people.