Krazam: High Agency Individual Contributor [video]
(youtube.com)269 points by asimpletune 3 days ago
269 points by asimpletune 3 days ago
I loved the Tree of Life reference, I want something like that printed out and put it next to my highly effective pyramid of success.
hunting for easter eggs, I found that https://www.saasiroth.com is an actual site and it contains the full manifesto. crazy.
Great find! Try logging in 4 times to be redirected to:
Surely you mean the Conjoined Triangles of Success?
> Just the mural on the whiteboard took them multiple hours - and, that's for a few seconds of the video
This is the absolute funniest few seconds though, the mural combined with the way it was shot and the classic BWOOOOOOMP soundtrack in the background actually had me crying laughing. it’s so good
Piggybacking to recommend another video of his, "The Hustle", which is a fast-paced memefest: https://www.youtube.com/watch?v=_o7qjN3KF8U
"Microservices" will always be my favorite: https://www.youtube.com/watch?v=y8OnoxKotPQ
Positive Affirmations for Site Reliability Engineers https://www.youtube.com/watch?v=ia8Q51ouA_s&pp=ygUGa3JhemFt
this hit so close to home I didn't know whether to laugh or cry
I was recently reading an article by a Twitter engineering team member discussing how they're reworking a microservice and kept expecting them to mention Galactus at some point. It lives rent-free in my head. This video is a true masterpiece.
I like to sneak in a Galactus reference during system design interview rounds when I feel like I'm about to overengineer the whole thing. I haven't done many recently, but for sure if I'm doing interview rounds, I will try to sneak in some Krazam references.
Mine is "leadership sync":
https://youtu.be/1RAMRukKqQg?si=K02Vsl7UhiUHos06
If you ever worked in a dysfunctional org this video speaks volumes.
These are all great, and for me it's even weird to pick a favorite because somehow he's managed to put so much genius into all of those videos and in so many multifaceted ways, it's beyond me. What kind of job/career experience has he had to come up with all of that, so creatively and accurately?
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.
For me its Microservices and the whole Senior Engineer video (and especially the outtakes)
https://www.youtube.com/watch?v=FDoH15ylAeo
Gotta go get my new shipment of caterpillars. Astral Plane combat ftw.
Their commercial is a low-key banger
“Need Salesfroce access ASAP for client meeting”
“Coffee machine in back kitchen wont connect to internet”
(On an unrelated note, TIL that you can highlight text to copy/translate etc directly from a YouTube video on an iPhone. I knew you could do that from pictures but never thought to try videos until now.)
You can kinda implement the 'strangler pattern' for this kind of ticket toil. The tool scrapes the ticket queue, tries to do what it can, either it is successful and closes out the ticket or updates it with a new state of what it was able to achieve (if anything) and hands it back to the humans. You can start with only the most basic tickets and then slowly start to expand its scope and capabilities to handle more patterns and edge cases.
Forget doing any of that until the OmegaStar finally ships, though.
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, meaning you'll almost never get management buy-in or any time to do it, leaving you in a perpetual cycle of manual work requests flooding in like in this scene.
I was kind of hoping the ending would be his tool worked and they all got laid off - actually seen this happen.
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 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.
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 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.
Yes. It's so bad where I work now that IT delegated approvals back to the managers. So now whenever you hire a new engineer, you have to click approve on all the systems they need access to do their job, because apparently RBAC doesn't scale to FAANG. And then they need to re-apply, and you need to re-approve, every year because virtually no accounts are 'forever' approved.
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.
I find the ending particularly funny, we have a small team where we're often building things in-house that we should probably just buy, or rely on manual processes for.
The fumbling with "oops, there's some test data in here" and the issues with the service worker hit a little close to home from some of our demos I've been a part of.
If you've ever worked in an org that has to be SOX (Sarbanes-Oxley Act) compliant, then you are familiar with a bunch of what's happening in this video. So much of your data, infra, and internal tools have to be gated by authorization and access logging tools -- so employees are constantly requesting access to the tools they need to get their work done.
These requests can be granted manually or automatically but they need to be logged and stored. Sometimes requests are required for every single access of a tool and sometimes it's time period based (24 hour access to Redshift or whatever) -- usually this depends on your role in an org. There isn't a coherent out-of-the-box way to provide the authorization and access gateways across all the different tools a business relies on -- so there is a big business opportunity for companies to basically provide turnkey identity and access management tools for companies.
Or, occasionally, an engineer loses their mind with the inefficiencies of these systems and processes and goes off on a jag to create the perfect internal tool to solve all these problems. That rarely (if ever) works, hence the video.
What I don't get here is the title. It's either referring to the employee who goes and creates the autonomous system, or even the system itself, but is "high agency" a corp buzzword the same way IC is?
Those last 30 seconds of the video, trying to get the demo to work for a group of people is so relatable.
This is obviously satire, but a significant problem organizations have as they scale is maintaining good taste--recognizing good solutions when they are presented.
Simply put, if that packet with a plan to automate away an entire department existed and was on a conference room table, no one would connect it to the business's bottom line. It would just go unnoticed. A typical corporate America manager would be unable to comprehend that something valuable was created that they were not asked to produce by their manager, and they did not ask their team to produce.
"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.
SaaSiroth is a combination of the acronym SaaS meaning “software as a service”, and the “Sephiroth” of Jewish mysticism.
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).
I'm 99% sure they were referencing evangelion's use:
https://evangelion.fandom.com/wiki/Tree_of_Life
(which if you haven't watched it's strange but I think for most hackers you'd vibe with it)
I wasn't involved in the process at all but I saw the creation of this video. I just want to say that I was mind-blown how much work these KRAZAM puts into their videos. Just the mural on the whiteboard took them multiple hours - and, that's for a few seconds of the video. Unbelievable how much love is put into something. And, it sounds weird but really touching to see creatives do something that they truly love.