Up until a couple of years ago, I was becoming increasingly active in the illumos community. I’d given a talk on the subject at Triangle DevOps, and indeed my most popular entries on this blog tend to be the ones relating to SmartOS. But something happend in my professional career, a conflict of interests, that compelled me to pull back from that community for awhile. The conflict is now gone, and hot on the heels of illumos Day 2014, my interest is re-invigorated. (more…)
The other day, I posted some thoughts capturing a conversation that happened in the illumos community over the weekend. If you missed it, head over first to The illumos Number That Bothers Me.
The conversation can’t die there. We’ve got to take pro-active steps to better understand how we got into this gender monoculture in the first place, and be catalysts to the change we wish to see in our community. I’ve been looking around a bit since then and found a few resources that should hopefully help to get the ball rolling. (more…)
I just got back late last night from Surge 2014 and illumos Day, which immediately followed Surge the next day. There were some great talks going on, which I’m sure I’ll also be writing about. But the first speaker in particular dropped something on me that’s bothering me, and it should bother pretty much anyone that hears it.
Garrett D’Amore, founder of the illumos project, crawled through all of the commits and made a really interesting discovery. This is a four year old project, and remains relatively obscure (though some very visible things have come out of it, like zfs). In those four years, about 150 unique contributors have committed code into illumos-gate, the shared core of the illumos ecosystem that distributions are built on. Now on the surface, this number sounds pretty wicked cool. illumos is a fairly unknown project, sadly, so to score commits from 150 engineers sounds like a really good thing. Or is it?
Of those 150 unique commiters, 0 of them were women.
Zero. Zilch. Nada. None. (more…)
I had the pleasure of addressing the Triangle DevOps meetup group on the subject of DevOps: Year One. The target audience was anyone who has bought into the idea of DevOps transformation for their business, but wanted practical advice for how to get started.
With only an hour to speak, and so many great questions to answer, we barely got to scratch the surface. But we did get to talk about some specific practices that have helped the Systems Engineering team at Bronto to work much more effectively.
View original post 1,462 more words
“We’re using a modified Kanban process.”
I admit, I cringe when people say things like this. It normally says to me “I haven’t put much thought into my process or my workflow, but we’ve got a board with some columns on it and the work goes there.”
In its simplest form, a Kanban gives you tools for two things:
- visualizing your workflow
- setting limits on each step (column limits) to maximize the completed units of work vs. the appearance of being busy
I’d been neglecting opportunities to work in my homelab for awhile so that I might take advantage of a bit of a creative streak and shoot some photography. That’s probably been satisfied, for a little while anyway, so I’ve spent much of this long weekend tinkering in the homelab. (more…)