Skip to main content

Going Camping

Today I spent most of my day in a windowless room cut off from the internet and the greater world, with no access to electricity, writing in my notebook, while a couple hundred other people did mostly the same thing. It was called Puppet Camp, and sadly it was not a day-camp where they taught me to make puppets (though, given that this is Portland, I'm sure that's actually something I could do). Today was when a handful of people talked at me about Puppet Enterprise application, which is a configuration and automation management tool from Puppet Labs.

I like Puppet; it's pretty nifty and if I were starting up my own company *shudder* I would probably mandate using Puppet from the get-go to reduce technical debt. One of the speakers today said "There is no future where IT is smaller or less important" and I agree, but I often feel like there are companies out there that don't understand how important dedicated Operations tools and Operations personnel are. The drive seems to be, in a lot of places, to reduce the Cost Center that is the IT & Infrastructure team to as close to zero as possible. In previous iterations of this issue, it's been outsourcing and *-as-a-Service contracts and "monetizing" and "chargeback". In the current iteration, the thought seems to be that if you turn your Ops team in to developers they can produce saleable IP in their "spare" time, when they're not Opsing and can Dev some.

I spent the lunch hour chatting with several people of both flavors: devs who are learning to Ops as well as Ops who are learning to Dev, and the agreement across all camps seems to be that DevOps, like Agile, means somewhat different things depending on who's saying the word, and how much agreement there is among parties in the conversation. Which I suppose is part of the point of both DevOps and Agile: getting parties to agree to terms and goals.

I'll probably go back over my notes and have more thoughts in the coming days, but mostly I wanted to note that being off the internet for the better part of a day induced withdrawal-like symptoms in me so strong that I ended up staring at my computer for the rest of the evening, not even doing anything. Just randomly browsing through my bookmarks, uncomprehendingly.

This post has no conclusion. Maybe tomorrow I'll be more articulate.

Comments

Popular posts from this blog

Organizing And You: Lessons from Labor History

    I made a joke on Twitter a while ago: Do I need to post the Thomas M Comeau Organizing Principles again? https://t.co/QQIrJ9Sd3i — Jerome Comeau says Defund The Police (@Heronymus) July 15, 2021 and it recently came back up because a member of my family got their first union job and was like "every job should be offering these sorts of benefits" and so I went ahead and wrote down what I remember of what my dad told me. My father had many jobs, but his profession was basically a labor union organizer, and he talked a lot about the bedrock foundation items needed to be serious about organizing collective action. Here's what I remember.    The Thomas M. Comeau Principles of Organizing -- a fundamental list for finding and building worker solidarity from 50 years of Union Involvement. This list is not ranked; all of the principles stated herein are coequal in their importance. Numbering is a rhetorical choice, not a valuation. 1) Be good at your job. Even in an at-will

Money and Happiness as a fungible resource

Money really does buy happiness. Anyone who tells you differently has a vested interest in keeping you poor, unhappy, or both. I know this because I grew up on the ragged edge of poor, and then backed my way into a career in IT, which is where the modern world keeps all the money that isn't in Finance. So I am one of the extreme minority of Generation X that actually had an adulthood that was markedly more financially stable than my parents. And let me tell you: money really does buy happiness. To be clear: at 45 years old, I'm now in a relationship and a period of my life where our household is effectively double-income, no kids. I live in the city, but I own a house, and can only afford to do that because of our combined income. We also have two cars -- one new, one used (though neither of them is getting driven very much these days) -- and we have a small discretionary budget every month for things like videogames, books, and the like. What my brother used to call DAM -- Dic

Activision, Blizzard, Game development, IT, and my personal role in all of that.

 I'm pretty sure if you spend any sort of time at all on Twitter and/or spend any sort of time playing videogames, you are by now at least aware of the lawsuit brought forth by the State of California's Department of Fair Employment and Housing versus Activision Blizzard, Inc., et al. From this point on, I'll add a Content Warning for folks who are sensitive about sexual assault, suicide, and discrimination based on sex, gender, and skin color, as well as crude humor around and about sexual assault , and what the State of California refers to as "a pervasive 'frat boy' culture" around Act/Bliz, especially in the World of Warcraft-associated departments.   Just reading the complaint is hard rowing, even with the clinical legalese in place. The complaint itself is relatively short; 29 pages laying out ten Causes of Action (basically, "these are the legs on which our lawsuit stands"). I'm not sure I have the vocabulary to properly express how a