Post

I’m amused and delighted that this talk’s topic is coalescing for @vbrownbag.com in the way it is, in the morning on the day we air. (Thread coming. 1/10)

I brought my "Griping as a Service" talk to @vbrownbag.com, a podcast with IT systems administration roots, because I came up with these ideas while helping #ITOperations administrators plan #InfrastructureAsCode modernization initiatives. (2/10)

My initial audience was enterprise employees whose “customers” are all their own in-house colleagues, and who simply wanted to write code for themselves and their teams, to “automate the boring stuff” about their own jobs. I even marketed the talk with the hashtag #sysadmin in every post. (3/10)

The “griping” I had in mind–which seemed to be a key to unlocking LLM assistance with requirements analysis–was, initially, frustrations about the process of teamwork itself. LLMs can transform your secret complaints about your colleagues and bosses into roadmaps for useful automation code. (4/10)

Two days ago, pre-consulting for another such admin team led me to say: “You know, I’m doing a podcast about this Wednesday night. About how operations work so often constrains your options that the sky hasn’t been the limit to what you can theoretically invent. (5/10)

"So most admins haven’t had the chance to spend years thinking about code in a 'product' mindset with software development lifecycles. "Oh. Hey. "I should probably find a way to slip that into my talk.” (6/10)

And then this morning, @mistwire.com released all the official promo and didn’t say a darned word about #EnterpriseIT or #sysadmins. He talked about user frustrations and product feedback. (7/10)

And there are business techniques out there that can make that happen (largely well-known in the domain of software #ProductManagement). (9/10)