31–40 of 60 posts
Earlier quoted context omitted.
"Microservices" will always be my favorite: https://www.youtube.com/watch?v=y8OnoxKotPQ
Their commercial is a low-key banger https://www.youtube.com/watch?v=duJwGSUhRQA
Earlier quoted context omitted.
"Microservices" will always be my favorite: https://www.youtube.com/watch?v=y8OnoxKotPQ
Mine is "leadership sync": https://youtu.be/1RAMRukKqQg?si=K02Vsl7UhiUHos06 If you ever worked in a dysfunctional org this video speaks volumes.
I just don't get how he can have had all this experience and at the same time be able to come up with those creative videos while still holding those insights. Because there's so many clever little things implying he's seen a lot. And created those videos in parallel.
I've enjoyed Krazam's other videos, but at the risk of having the joke explained (and thus spoiled), what exactly is this lampooning? Not asking from a critical place, I legitimately am curious about dysfunctional business processes at other companies and want to know if people really are drowning in SaaS access requests
Lol, yes, you can extend this same bit to any team that deals with a lot of ops. Usually goes like this - Too many requests come in for one team to handle. No budget to hire more bodies, or maybe you've already reached a point where that will no longer scale - the work can usually be automated completely, but stopping and taking the time to automate it will result in a 100% loaded team KPI's dropping significantly, m…
I felt the video was relatable to me in many frequent situations where I would like to automatize some sort of process, but I end up being overly enthusiastic, because I'm so biased towards automating routineus activities. I frequently end up spending more time automating something than it would've been worth to just do it couple of times. I end up creating PoCs that don't entirely work in situations like those and the demos can fail, because I got bored at some point and didn't check thoroughly enough, so this video made me cringe at myself.
I do feel however that this was just one layer of this video, and the other layer is about the other side where manual processes are preferred for irrational reasons over automation, so I think this video accurately reflected all sides of the story. Automating vs doing something routineusly is a balancing and tolerance act.
Earlier quoted context omitted.
this signal the death of the passive aggressive "take this offline" for me also favorite comment "This video captures the absolute weirdness of millennials and zoomers inheriting the bureaucratic systems created by baby boomers"
I find it weird how so much generation discussion seems to skip gen x. I see references to boomer, millennial, and zoomer/gen z way way more often than gen x.
Earlier quoted context omitted.
Lol, yes, you can extend this same bit to any team that deals with a lot of ops. Usually goes like this - Too many requests come in for one team to handle. No budget to hire more bodies, or maybe you've already reached a point where that will no longer scale - the work can usually be automated completely, but stopping and taking the time to automate it will result in a 100% loaded team KPI's dropping significantly, m…
Personally I think the successful automation ending would've been "too satisfactory and perfect". Real life is not that. I felt the video was relatable to me in many frequent situations where I would like to automatize some sort of process, but I end up being overly enthusiastic, because I'm so biased towards automating routineus activities. I frequently end up spending more time automating something than it would've…
Part of how I’ve made myself useful as a consultant sometimes in my career is by insisting on a strict set of processes that break down and identify bottlenecks like this. It’s almost always ops, it almost always can be automated, but there’s “no bandwidth or budget” to fix the problems so they expect superheroes to constantly save the day by pulling absurd hours or by inventing genius solutions that management buys into.
For me, as an IC or sometimes as a consultant, I try to chip away. We spend X minutes a week doing Y thing manually. what’s the easiest thing we can do to reduce X? and then slowly introduce whatever arises out of those processes, and then slowly “eat the elephant” one bite at a time.
when people come into a big messy manual legacy system they often, imho, make the mistake of wanting to tear it down and recreate it from scratch. having done several cloud architecture/IAC refactors in my career, I can tell you its definitely a way easier sell to management and other teams to whittle away at it than to recreate it entirely, and i think that’s also what the video is poking fun at. There’s always skeletons that your perfect solution will run into. Processes, standards, and monitoring will expose these dead bodies, but it’s not a one shot solution and I’m immediately skeptical when anyone proposes something in this space that is. Every situation is a snowflake.
I've enjoyed Krazam's other videos, but at the risk of having the joke explained (and thus spoiled), what exactly is this lampooning? Not asking from a critical place, I legitimately am curious about dysfunctional business processes at other companies and want to know if people really are drowning in SaaS access requests
And since many of these are "per-seat" licensing, finance is always cajoling IT into aggressively culling unused accounts. Which makes it to these poor bastards's DMs early in the screen, and the corresponding IT ticket hell of people requesting their access back.
The punchline at the end is basically just hubris: you've solved the megacorp RBAC problem in your head, but trip over the BS logistics of it all. Probably because your application doesn't have network permissions or some other ironic problem.
Also, please feel free to list other inside jokes in the video. I could see lots of potential ones, including the oil barrel.
"SaaSiroth" seems to be an inside joke. Anyone know what it points to? Also, please feel free to list other inside jokes in the video. I could see lots of potential ones, including the oil barrel.
The diagram on the front page and blackboard in the video is a representation of the Sephiroth, the Jewish Kabbalistic tree of life. It’s something to do with Jewish metaphysics and cosmogony, but it’s very esoteric, may you have better luck making sense of it than I!
Instead of the “ten emanations” of Kabbalah, the diagram in the video contains concepts from the technical domain of Identity and Access Management (IAM).
Earlier quoted context omitted.
Personally I think the successful automation ending would've been "too satisfactory and perfect". Real life is not that. I felt the video was relatable to me in many frequent situations where I would like to automatize some sort of process, but I end up being overly enthusiastic, because I'm so biased towards automating routineus activities. I frequently end up spending more time automating something than it would've…
I have fought this battle for my entire career. The problem is, incentives are tough - often senior engineers on ops teams have built the system on duct tape and bubble gum, and have a very specific and unobtainable knowledge about all the quirks of it which frequently involve a ton of manual, esoteric shit to resolve without a lot of know-how. Part of how I’ve made myself useful as a consultant sometimes in my caree…
Yeah, I mean, I think this describes it. Ultimately the video had many thoughts and layers, starting with a charismatic lead who is proud or pretending to be proud about completely meaningless, arbitrary achievements and metrics trying to motivate his team for rejecting access requests. Then it goes on to this individual who just can't handle it. Which is relatable. I don't think I could be able to perform a job like this at all. So I think this individual there was just so badly misplaced for handling this type of work - he really wanted out from there, but unfortunately it is not always so simple. In an ideal world he would've worked in another role.