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.
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 @firstname.lastname@example.org at #DevOpsDaysTO.
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 missed Dominica’s talk at #DevOpsDaysTO, 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.
Headed to #DevOpsDays 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.
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.