I have 27 years of experience, and this young man managed to summarize my work experiences as a joke, I am seriously thinking of copying his speech for my next job interview. 😄
Last year I started doing the CTO part, yep. The the V model used by the electrical engineering industry is , oh, chief kiss. It does work much better than scrum when you actually have "processes" and know what you are doing.
dude this line hit my soul... in corp world about 2 people per team write code and 7-10 make money by going to meetings deciding what those 2 people do.
@@jdubeau007 What is he saying is funny, because it is true on any product that is reliable and has tons of real profit generating customers. And all these "start-ups" for end user look like a broken toys, until they are bought by someone with the products mentioned above
yeah, recently we implemented a heuristic based customer search. it was painfully slow, and you had to click/tab out of a filter box to get the additional parameters into your query, but not before waiting for all the results for the previous search parameters. as a tester i reported that, first the speed is an issue, and then that even if it would run instantly, it would feel slow for some users because of the need to leave a filter box and to wait for the unfinished load. I was told, that its fine, because it works, and it will work better on our customers SSDs, then on our HDDs, so we will ship it. after weekend the customer made an incident, reporting exactly theese two defects :D
I understood the joke is that the interviewer asked him "do you test if it works?" and he answered "no, because it's not a non functional requirement", unlike the rest of the testing he mentioned
Says a lot about the tech industry, sadly. Everyone is trying so hard to be ahead that they are behind, haha. Not surprising, majority of these buzzwords come from the managerial class.
I was about to comment about the editing. Unlike all the other videos on this channel, this one has cars moving in the background. This means you can clearly identify which cuts were true edits and which ones where just added to give the impression of an over-edited clip. I always assumed that this technique was convenient for the actor because he can screw up as much as he wants but judging by this video he knows his lines very well despite the complexity
My company has an internal "academy" of self-guided training courses written by actual, practicing, in-house data scientists. Small Data Problems is a "prerequisite" of Big Data Problems.
@@bigbabyg They will never notice that you are imposter because r/programmerhumor consists of beginners only. Look at amount of posts about people not figuring out even simple concepts of C++ pointers and other stuff that's learnable if you spend more than 10 minutes on it.
i live in Switzerland and every code base ever is created like that, tons of management overhead and one guy implementing it in two weeks while 10guys try to maintain management changes yo already released features
either ways: WoPaaS (Workflow of Processes as a Service) is far ahead PoPaaS. Idea was nice, but implementation sucks... How to tell me you're trying to fix low level issues with only high level knowledge without telling me. '--
It's a 2 second video, "Scrap everything that guy just said and just deploy it as fast as possible on the cheapest server possible. We need 300 more users to make sure I can pay you next week!"
This reminds me of a time when I was asked to create some user stories for our backlog. I ended up with stuff like "proactively integrate pipeline delivery", implement holistic data" and "structuralize shared systems". The sad thing was that everyone just went along with it. They didn't dare to ask what was going on.
When a parody is disturbingly accurate 😅 Comedians are brilliant and this guy is no exception. I would love to work with him. This field is filled with jargon and the word play was perfect. Your vids are top notch and remind me all of us are just trying to figure it out. I am a DevOps guys so I felt this vid deep.
I created a Kubernetes cluster, ran ChatGPT on it, stored it in Neo4j and then used PHP to create a CSV of all the things he said and put it on my CV. Sillicon Valley here I come!
You need to implement "non functional function testing", "test testing", more processes to streamline workflow and become more agile. This is funny because it hits so close to reality in some cases where it seems like the buzz words themselves are the driving force. knowing all of them and relating to how they are used in the corporate world by real people gives some truly amusing reflection. 😄Brilliant!
its really very simple. you have cashflow, you have burnrate. you fire people until the burnrate is a bit bellow the cashflow. even Elon Musk can do that (but the stupid last Twitter CEO was a freaking communist, lol) If you don't have cashflow, then you are a startup, you increase the burnrate with more people, then you sell the company to another company, all the people are immediately fired, because you don't have cashflow, but you have the final product !
I worked in a company using a V-model. It was quite well organized, so maybe an outlier. The cycle length was 6 month. It was quite slow, but good documented. They build lab software, so they had very high standards to meet. It was oddly pleasant. Now I am working in the IT department of a big non-IT company and it is pure and utter chaos. Nobody has a clue, nobody follows any guidance or has any responsibility. Nothing gets done and there is lots of finger pointing. Currently looking for a new job btw^^
I'm at that unfortunate age where my younger half is laughing at all the engineering bureaucracy while my older half is unironically agreeing with the guy, which makes the viewing experience so much more fun.
Corporate IT is like this. We the oldies see the same problems staying and new technologies coming and going, it's like living in the Ground Hog Day. That's why we harp on about "processes" ;-)
You mean business processes being built around poorly designed software, rather than software being built around well designed business processes? The "tail wagging the dog" you could say.
Recently interviewed for SRE role, I was totally this boomer. Trying to talk about the processes and how to set up a plan to reach objectives, I'm afraid to set something up and be responsible for it if there aren't PROCESSES PROCESSES PROCESSES
I think processes are really important, but you have to pick which ones really matter and try to automate adherence to those processes. The worst thing you can do is run in the wrong direction with your product/company. The second worst thing is to clog your innovation with unnecessary processes that only serve to slow you down to the point you can barely crawl. When I was in a startup I advocated processes. Now at big tech I advocate against it unless completely necessary.
@@ejun251 Bureaucracy is hard to manage. We are at this point technology is so good at processing bureaucracy that we create unnecessary bureaucracy just to feel better and have no responsibility. The companies become ossified and can't change a thing, so they buy startups in the hope they can move faster and not die the slow death, but then they kill the startup with excess bureaucracy before it can change thing internally. You have to resist being sold as a startup, and put some bureaucracy/processes so you can start to ossify enough to not be fragile, but not too much you become a rock. That's it, companies are not anti-fragile, they ossify, then they break and die out of their own weight. Its inevitable.
@@ejun251 The funny thing is that you guys use the word "process" when you actually mean "boring, fixed, written down, repeatable procedure". It already indicates that you are beyond rescue because you started believing your own crap to the point of redefining common words.
@@harakiri23 Tbh I don't think so because it depends on what level of data analysis one does - if we are talking about truly extracting highly complex things from a huge dataset then that would be called data science, otherwise if it is just writing some SQL queries to pull data and slap it onto a chart for a board meeting then it is just ordinary data analysis. A lot of what is coined "data science" in the industry has gone towards the "make a report of some business figures and a couple charts to present to investors" rather than true epic data science - so I think it just depends on complexity and task at hand... if you're just a glorified data analyst that is one thing - but if you are pushing the boundaries of human connection to data, that is data science. Edit: Science is always the act of pushing human knowledge in some field beyond what is known... so if we apply the scientific method to data, we get data science - so that is the distinction.
@@poloska9471 I guess he was referring to the fact that calling yourself a data scientist is kind of marketing oriented. It's fine since that job title became standard in the industry, but a bit hype oriented I suppose. I used to be a data scientist, and then I moved to data engineering. Nowadays, I got fed up with all those data terms, I just call myself a software engineer. End of story.
This is absolutely how corporate tech works. On the one hand, this is great since it means that the "one guy who actually writes the code" doesn't end up taking down the whole internet due to a mis-configured bucket policy. On the other, this is how FAANG (or, rather, MAMAA) is able to lay off 10% of its workforce without batting an eye. Also 3:09 hits really hard right now.
Has someone written a Resume generator that works like the beginning of this video? It takes buzzwords and randomly generates resume bullets from it. I wonder how well that would work. Distributed- Blockchain- Load balancing Holistic- Distributed- Datacenter- Integration Block chain- Integration- As a service Zero-trust- Resource- Integration- Management Distributed- Zero-trust- Datacenter- Analysis Redundant- Multiplatform- Enterprise- Management and the list can go on
On one hand, I hate the management bloat. On the other hand... he said "fuck agile" and that makes me love him. What agile is today is a sick imitation of what it was meant to be. Agile should be injected into a properly planned out process. Not be the whole process.
For software that does important jobs you do need to do most of this - he just threw in a few jokes here and there. There's no way to get 100s of engineers distributed around the world to reliably deploy stuff often without processes and testing (and I've heard the "we only hire rock star engineers so we don't need processes" before - rock stars aren't known for being nice to work with or team players)
"No you can't just use Heroku" This is the one, why so many companies are against using this god-send of a product is beyond me. Of course it's not a panacea, but it covers 99% of the bases for most projects. It also is AWS.
It's because it's not easy to port stuff from Heroku and when you run into problems its hard to fix in that there's not as much transparency. I've worked at a startup that started on Heroku and of was a hot mess to maintain.
@@mantality312 It's one thing when your app is used by like 10 people and nobody cares if it breaks. Heroku is easy. However, when you have to deal with larger traffic and SLA agreements with customers I promise you it's not so easy. When you have multiple teams and business units that need to audit and analyze data it's not so easy. When you suddenly find yourself needing to do something complex like set up an ETL pipeline with insert (hippa, high trust, PCI) compliance suddenly Heroku is not so easy. The point I'm making is that although it's easier to use in the short term eventually, if your lucky, you're going to out grow it. It's too opinionated and oversimplified. And, when that day comes you're in for a world of hurt. I know this because I've done it.
Honestly, agile can have the same problems with "too many processes". I'm a strong advocate of a non-invasive and minimalistic agile implementation. Required meetings should be extremely short and concise. I hate meetings. One of my roles is scrum master.
@@dejangegic IMO it should just be each person listing off what work item they are working on and if there is anything that is pertinent for everyone in meeting to know about then it is mentioned, otherwise the next person goes, and then it is over - so for a team of 5 developers it could be as quick as 5 to 10 minutes - or even better if not done as a meeting but rather a Slack channel where every person just posts a brief list of what they are working on and any remarks that are necessary to mention.
Daily face to face stand ups are better than Slack - you need some social interaction to get people working well together. And you missed raising impediments which in a well functioning team is a chance to get some additional thoughts or help from others who may have experience in the area or get it escalated to scrum master and make it their job to go outside of the team to get it sorted. You can do that over slack as issues come up too but I've seen this become really distracting with everyone posting every little problem to slack and everyone jumping in to help through the day instead of the person taking an afternoon to figure it out themselves and take it to stand up if they are really blocked.
It’s daunting when you’re a young man showing up to your first job and there’s some grizzled old veteran who talks like this. You pretend like you understand what he is talking about. About a year or two ago I realized that I am now that guy as I was rambling something my colleague on the phone and after the call my wife said “you know I could hardly understand a single word of what you just said now”.
As a systems engineer undergraduate, I have to agree... Processes! Teams to manage teams! Coding comes at the very end! But the waterfall model is history nowadays
I have 27 years of experience, and this young man managed to summarize my work experiences as a joke, I am seriously thinking of copying his speech for my next job interview. 😄
Do no forget to have a dark mustache with the white hair and the ball cap.
Last year I started doing the CTO part, yep.
The the V model used by the electrical engineering industry is , oh, chief kiss. It does work much better than scrum when you actually have "processes" and know what you are doing.
@@Elasticmushroom Two dozen if you're shooting for lead dev.
27.5
@Master & Commander yes, You have it !!
"code implementation...comes at the very end... usually done by one person" 😂
I am that person usually :/
that gave me an idea Chat-GPT CTO !
🤣💀
dude this line hit my soul... in corp world about 2 people per team write code and 7-10 make money by going to meetings deciding what those 2 people do.
In France in the 90s real men wrote UML (actually, Merise) diagrams. Plebes wrote code, as an afterthought. Processes FTW.
He perfectly meets the requirements of a junior developer job.
What he is saying is funny because alot of it is bullshit.
@@jdubeau007 What is he saying is funny, because it is true on any product that is reliable and has tons of real profit generating customers. And all these "start-ups" for end user look like a broken toys, until they are bought by someone with the products mentioned above
Unpaid intership at best, he needs more experience.
@@first_namelast_name4597 absolutely, we need to complicate the process even more so we can justify the existance of the DevOps team
With all that experience he might even get past first-round interviews
""It works" is a non-functional requirement" made me laugh way harder that I should have.
I thought he said ""it works" is NOT [sic] non-functional requirement" and found that funny as well. Now I'm confused
He said it works is not a no functional requirement (startup culture : it works, ship it)
yeah, recently we implemented a heuristic based customer search. it was painfully slow, and you had to click/tab out of a filter box to get the additional parameters into your query, but not before waiting for all the results for the previous search parameters.
as a tester i reported that, first the speed is an issue, and then that even if it would run instantly, it would feel slow for some users because of the need to leave a filter box and to wait for the unfinished load. I was told, that its fine, because it works, and it will work better on our customers SSDs, then on our HDDs, so we will ship it.
after weekend the customer made an incident, reporting exactly theese two defects :D
I understood the joke is that the interviewer asked him "do you test if it works?" and he answered "no, because it's not a non functional requirement", unlike the rest of the testing he mentioned
@@magzpayne I see what you did there.
This guy has the most vast knowledge of industry's buzzwords. By joking around he has more knowledge than many CTOs
Says a lot about the tech industry, sadly. Everyone is trying so hard to be ahead that they are behind, haha. Not surprising, majority of these buzzwords come from the managerial class.
Low-Level Programming: ❌
High-Level Programming: ❌
Eye-Level Programming: ✅
⚰️
Right in the sweet spot...
as in "my eyes are up here" programming
ergonomics is no joke
this guy is a very good actor, but we need to commend the editor too. The "high level, low level, eye level" edit was amazing
it kinda feels like the editor just spammed the razor tool on the video clip lol
U are thinking to deep about it
Literally lost it
I was about to comment about the editing. Unlike all the other videos on this channel, this one has cars moving in the background. This means you can clearly identify which cuts were true edits and which ones where just added to give the impression of an over-edited clip. I always assumed that this technique was convenient for the actor because he can screw up as much as he wants but judging by this video he knows his lines very well despite the complexity
Maybe the actor is also the editor.
Load testing for data centers. Data center testing for load centers😏
Next level.😂
fucking died laughing
"and you need a third guy because you cannot trust the second guy". Of course redundancy, reliability and availability
Don’t forget a fourth guy because you need a control plane to manage metrics, load balancing, and self healing for the first three guys
everybody ask about big data, but nobody ask about little data
My company has an internal "academy" of self-guided training courses written by actual, practicing, in-house data scientists. Small Data Problems is a "prerequisite" of Big Data Problems.
Little data is what comes out of your pipelines when you don't implement Processes
@@slamwell3329 you have to trap the data out of the minds of humans, with processes.
stats
Everybody asks where is big data, but no one asks how is big data?
I've only got 5 years of experience but I gotta say he's making a lot of sense...
ive only got 1 year of experience but im going to say he's making a lot of sense so r/programmerhumor dont notice im an imposter
@@bigbabyg They will never notice that you are imposter because r/programmerhumor consists of beginners only. Look at amount of posts about people not figuring out even simple concepts of C++ pointers and other stuff that's learnable if you spend more than 10 minutes on it.
@Power Ball! the finer things
@@bigbabyg are you sure that you are good enough for imposter syndrome? :^)
i live in Switzerland and every code base ever is created like that, tons of management overhead and one guy implementing it in two weeks while 10guys try to maintain management changes yo already released features
He's talking of the new Process of Processes as a Service (PoPaaS), whose acceptance testing needs to be documented.
PoPaas sounds like the perfect model for all the IT problems right now! I will start recommending this in our next department meeting 🤝
PoPaaS is next generation consulting. Remotely on the cloud in a thunderstorm. Our slogan is “It’s alive”
Is this discussion a form of PoPoPaaS?
You're making it all sound very simple.
either ways: WoPaaS (Workflow of Processes as a Service) is far ahead PoPaaS.
Idea was nice, but implementation sucks...
How to tell me you're trying to fix low level issues with only high level knowledge without telling me. '--
"Code trashification" ahh lawd have mercy i lost it bad right there 😂
This is a venture-backed startup CTO. Can you do a bootstrap one next? :) There is a great contrast to exploit here.
Absolute +1
+1
bootstrap doesn't have real CTO, its just the investor with money getting 80% of your company
@@monad_tcp The definition of bootstrapping: No outside investor, everything on your own.
It's a 2 second video, "Scrap everything that guy just said and just deploy it as fast as possible on the cheapest server possible. We need 300 more users to make sure I can pay you next week!"
"Children's' magic like microservices" -- thats gold
This reminds me of a time when I was asked to create some user stories for our backlog. I ended up with stuff like "proactively integrate pipeline delivery", implement holistic data" and "structuralize shared systems".
The sad thing was that everyone just went along with it. They didn't dare to ask what was going on.
There is a great song by Weird Al Jankovic about that :).
@@nicknamenescioDo you know what the song's title is??
@@Ashystar067 I think it should be "Synergy".
Dude wrote the summary for my last job description
Absolutely 100% agree. Redundancy is very important.
Absolutely 100% agree. Redundancy is very important.
Absolutely 100% agree. Redundancy is very important.
Absolutely 100% agree. Redundancy is very important.
Absolutely 100% agree. Redundancy is very important.
Absolutey aggree (79%)
I found this channel and have been laughing about it ever since. Whomever you are, kudos.
How did he even get every professional problems in software field so accurately his skits just genius 👌
His video on vim was not good
@@opusdei1151I thought it was pretty spot on
@@opusdei1151 I wasted a couple of year on vim and I think he got the essence of it :D
I rewatch this every few weeks and it makes me laugh out loud every time!!! Pure Gold!
10/10 I worked for this guy from 2014 to 2019
Same, lol.
100% agree that redundancy is important. All the voices in my head agree too so that's at least 300 or 400% agreement.
When he said Test Testing, I felt that.
When a parody is disturbingly accurate 😅 Comedians are brilliant and this guy is no exception. I would love to work with him. This field is filled with jargon and the word play was perfect. Your vids are top notch and remind me all of us are just trying to figure it out. I am a DevOps guys so I felt this vid deep.
Okay you know my email
"From pacemaker firmware to NFT scam" 💀
At "and so on and so forth" he transformed momentarily into Slavoj Žižek.
“Eye-level design” ended me
I created a Kubernetes cluster, ran ChatGPT on it, stored it in Neo4j and then used PHP to create a CSV of all the things he said and put it on my CV. Sillicon Valley here I come!
Gosh…
I mean, if you can actually do that, there is a job for you in IT.
_"then used PHP to create a CSV"_
I threw up a little bit
@@enclave2k1lmao same.
03:09 I love how "Agile? Agile! Agile" transforms the W123 into E36 and back, but keeping the coupe body. That's apparently the power of agile.
I didn't understand your comment but liked it anyway as it just sounds hilarious 😂
Yeah me neither, E36 is something to do with AWS buckets?
@@theodorealenas3171 I think it is one of the legendary models of BMW
they're talking about the car in the background. its stitched video
Its about the cars in the background. The cut makes it look like the old mercedes w123 becomes the BMW and back
holy shit this is frighteningly accurate
please make rust dev
I think he did
You need to implement "non functional function testing", "test testing", more processes to streamline workflow and become more agile. This is funny because it hits so close to reality in some cases where it seems like the buzz words themselves are the driving force.
knowing all of them and relating to how they are used in the corporate world by real people gives some truly amusing reflection. 😄Brilliant!
LOL the black car at 2:20 just backed out of the intersection
lmao that's scary
"Huge, deficient data migration". I feel like everyone's seen this one if they've been around long enough.
Every video is a masterpiece. When we could expect an interview with the COBOL programmer?
The perl interview comes close :)
He's saving that one for Halloween - It would be an ideal time for a graveyard seance
When he emerges from his coffin.
Im 33 and am a mainframe dev. I use cobol and jcl everyday
👔 Merch: posix.store
🚀 Twitter: twitter.com/kailentit
a 3rd guy because you cant trust the 2nd guy 🤣🤣🤣🤣🤣🤣🤣🤣🤣
I was that 2nd guy in the last job :D
If it weren't for the fake moustache you could probably show this to a CTO and they would shake their head in agreement throughout the video.
My man slowly turning into a rapper with these fire bars 😂
Daft Punk could remix this :)
Okay up til a point I wasn't sure that he was trying to imitate Zizek, but 5:00 made it absolutely clear
it's the crossover the industry needs
🤣
Yeaah I noticed that too!
I miss watching that guy. ***Sniff***
Just rewatched it and saw that the question was building a 1 man startup 😂😂😂😂
omg
You need Dev ops team available 24/7!
@@AmstradExinYou need the third guy on call because you don't trust the second guy.
This is so awesome! being “CTO” or Tech “CEO” is all about processes and fire useless resources. 😂 I am dying….
its really very simple. you have cashflow, you have burnrate. you fire people until the burnrate is a bit bellow the cashflow. even Elon Musk can do that (but the stupid last Twitter CEO was a freaking communist, lol)
If you don't have cashflow, then you are a startup, you increase the burnrate with more people, then you sell the company to another company, all the people are immediately fired, because you don't have cashflow, but you have the final product !
Had never heard of V-Model before. Thank you Boomer CTO!
(hope to never hear of it again, now that I've looked it up on wikipedia)
I worked in a company using a V-model. It was quite well organized, so maybe an outlier. The cycle length was 6 month. It was quite slow, but good documented. They build lab software, so they had very high standards to meet. It was oddly pleasant.
Now I am working in the IT department of a big non-IT company and it is pure and utter chaos. Nobody has a clue, nobody follows any guidance or has any responsibility. Nothing gets done and there is lots of finger pointing.
Currently looking for a new job btw^^
Most people watch Fireship to quickly learn about something, but I find these videos more informative.
I'm at that unfortunate age where my younger half is laughing at all the engineering bureaucracy while my older half is unironically agreeing with the guy, which makes the viewing experience so much more fun.
Halfway through and I'm just laughing uncontrollably. Your writing and acting are on point!
it sounds like a joke until it no longer is a joke 💀
I've worked with CTOs just like this. This video is almost not a parody.
thank you for sharing. these all are precious fields. i will try to learn all these😊.
Corporate IT is like this. We the oldies see the same problems staying and new technologies coming and going, it's like living in the Ground Hog Day.
That's why we harp on about "processes" ;-)
You mean business processes being built around poorly designed software, rather than software being built around well designed business processes? The "tail wagging the dog" you could say.
Recently interviewed for SRE role, I was totally this boomer. Trying to talk about the processes and how to set up a plan to reach objectives, I'm afraid to set something up and be responsible for it if there aren't PROCESSES PROCESSES PROCESSES
I think processes are really important, but you have to pick which ones really matter and try to automate adherence to those processes. The worst thing you can do is run in the wrong direction with your product/company. The second worst thing is to clog your innovation with unnecessary processes that only serve to slow you down to the point you can barely crawl.
When I was in a startup I advocated processes. Now at big tech I advocate against it unless completely necessary.
@@ejun251 Bureaucracy is hard to manage.
We are at this point technology is so good at processing bureaucracy that we create unnecessary bureaucracy just to feel better and have no responsibility.
The companies become ossified and can't change a thing, so they buy startups in the hope they can move faster and not die the slow death, but then they kill the startup with excess bureaucracy before it can change thing internally.
You have to resist being sold as a startup, and put some bureaucracy/processes so you can start to ossify enough to not be fragile, but not too much you become a rock.
That's it, companies are not anti-fragile, they ossify, then they break and die out of their own weight. Its inevitable.
ok boomer
@@ejun251 The funny thing is that you guys use the word "process" when you actually mean "boring, fixed, written down, repeatable procedure". It already indicates that you are beyond rescue because you started believing your own crap to the point of redefining common words.
Oh boy, as a Data Scientist in corporate, I can understand this completely XD
That what happens when marketing takes over the science. I have two degrees one in CS and Mathematics.
As an old school developer, isn't calling yourself "Data Scientist" a bit too much of cringe?
@@harakiri23 Tbh I don't think so because it depends on what level of data analysis one does - if we are talking about truly extracting highly complex things from a huge dataset then that would be called data science, otherwise if it is just writing some SQL queries to pull data and slap it onto a chart for a board meeting then it is just ordinary data analysis. A lot of what is coined "data science" in the industry has gone towards the "make a report of some business figures and a couple charts to present to investors" rather than true epic data science - so I think it just depends on complexity and task at hand... if you're just a glorified data analyst that is one thing - but if you are pushing the boundaries of human connection to data, that is data science.
Edit: Science is always the act of pushing human knowledge in some field beyond what is known... so if we apply the scientific method to data, we get data science - so that is the distinction.
@@poloska9471 I guess he was referring to the fact that calling yourself a data scientist is kind of marketing oriented. It's fine since that job title became standard in the industry, but a bit hype oriented I suppose.
I used to be a data scientist, and then I moved to data engineering. Nowadays, I got fed up with all those data terms, I just call myself a software engineer. End of story.
Oh god, this is my CS teacher.
mine too
de.wikipedia.org/wiki/Mohsen_Rezagholi
"Mama mia, what is documentation?" made me lol for real
🤣🤣
Hot box testing got me wheezing
This is absolutely how corporate tech works. On the one hand, this is great since it means that the "one guy who actually writes the code" doesn't end up taking down the whole internet due to a mis-configured bucket policy. On the other, this is how FAANG (or, rather, MAMAA) is able to lay off 10% of its workforce without batting an eye.
Also 3:09 hits really hard right now.
The most mind boggling thing is at they lay off so many incredibly talented people but this middle manager stays.
MAAMA sounds so much sillier than FAANG.
@@4.0.4 As it should--the whole concept is ridiculous
@@monad_tcp Yep. Firing 70% of your workforce is a genius business move. Just ask anyone left at Twitter.
@@4.0.4 isn't it MANGA though
Has someone written a Resume generator that works like the beginning of this video? It takes buzzwords and randomly generates resume bullets from it. I wonder how well that would work.
Distributed- Blockchain- Load balancing
Holistic- Distributed- Datacenter- Integration
Block chain- Integration- As a service
Zero-trust- Resource- Integration- Management
Distributed- Zero-trust- Datacenter- Analysis
Redundant- Multiplatform- Enterprise- Management
and the list can go on
yes. another commenter in here did.
Time to update my resume.
"I have used all used databases. and neo4j" - so cruel, so true, so funny, lol
I liked all your videos in the hopes of more content and subscribers / viewers!
Its fun watching the building shadows jump around!
On one hand, I hate the management bloat. On the other hand... he said "fuck agile" and that makes me love him.
What agile is today is a sick imitation of what it was meant to be. Agile should be injected into a properly planned out process. Not be the whole process.
For software that does important jobs you do need to do most of this - he just threw in a few jokes here and there.
There's no way to get 100s of engineers distributed around the world to reliably deploy stuff often without processes and testing (and I've heard the "we only hire rock star engineers so we don't need processes" before - rock stars aren't known for being nice to work with or team players)
The most important testing, "Test testing".
"No you can't just use Heroku"
This is the one, why so many companies are against using this god-send of a product is beyond me. Of course it's not a panacea, but it covers 99% of the bases for most projects. It also is AWS.
It's because it's not easy to port stuff from Heroku and when you run into problems its hard to fix in that there's not as much transparency. I've worked at a startup that started on Heroku and of was a hot mess to maintain.
@@cprogrck If you find Heroku hard you are likely not that good of a dev. Heroku is literally designed to not be hard to maintain.
@@mantality312 It's one thing when your app is used by like 10 people and nobody cares if it breaks. Heroku is easy. However, when you have to deal with larger traffic and SLA agreements with customers I promise you it's not so easy. When you have multiple teams and business units that need to audit and analyze data it's not so easy. When you suddenly find yourself needing to do something complex like set up an ETL pipeline with insert (hippa, high trust, PCI) compliance suddenly Heroku is not so easy. The point I'm making is that although it's easier to use in the short term eventually, if your lucky, you're going to out grow it. It's too opinionated and oversimplified. And, when that day comes you're in for a world of hurt. I know this because I've done it.
is anyone else getting a strong Slavoj Žižek vibe from this? :)
so on and so forth
Honestly, agile can have the same problems with "too many processes". I'm a strong advocate of a non-invasive and minimalistic agile implementation. Required meetings should be extremely short and concise. I hate meetings. One of my roles is scrum master.
How short are we talking for daily standups and how long for other meetings?
@@dejangegic IMO it should just be each person listing off what work item they are working on and if there is anything that is pertinent for everyone in meeting to know about then it is mentioned, otherwise the next person goes, and then it is over - so for a team of 5 developers it could be as quick as 5 to 10 minutes - or even better if not done as a meeting but rather a Slack channel where every person just posts a brief list of what they are working on and any remarks that are necessary to mention.
Daily face to face stand ups are better than Slack - you need some social interaction to get people working well together. And you missed raising impediments which in a well functioning team is a chance to get some additional thoughts or help from others who may have experience in the area or get it escalated to scrum master and make it their job to go outside of the team to get it sorted.
You can do that over slack as issues come up too but I've seen this become really distracting with everyone posting every little problem to slack and everyone jumping in to help through the day instead of the person taking an afternoon to figure it out themselves and take it to stand up if they are really blocked.
@@ByronWWW but that means you need to go to the office...
Now watch his video about Scrum :)
Rich old dudes in STEM always be drinking San Pellegrino. Nailed it.
Reminds me of many of professor I had in college, spot on!
this is so real I live it every day
"if you are doing using validation, you are doing code trashification"
lmao
I work for a company that does projects with OEMs. This hits home so hard. Also I wish we tested this much lol
Testing my beloved
I read this video’s transcript in my latest interview and now I’m the CTO of amazon. I just wanted to work in the warehouse 😭
I can't... I just... I can't breathe. I laughed so much that I had to sit down on the floor.
"Azuros Cloudapi" made my day
I was just reading about additional testing Crowdstrike have put in place going forward. Immediately I hear Azuros Cloudapi's voice in my head.
watched this more than 10 times, This is fucking hilarious 😅😅
I mean, he's right about at least one thing - V-model is pretty good
This guy just doesn't miss
Funny enough as a baseline, but for people who've experienced it themselves or at work.
It hits different
"mama mia, what is documentation" (real)
Thanks to the vast knowledge of this pro I realized we forgot to implement test-testing in our system
I can just imagine how his Master Class for true programmers went during his college days.
I thought he was gonna say "small data" after big data lmao
As someone who’s dealt with buzzword CTOs in the past, this is real and pain.
When Slavoj Žižek decides to go full-stack
"I know I'm making all of this sound very simple..." 🤣🤣🤣
Perfectly summarised most of the software development happening now!
In the last scene he was doing an often overlooked process called “disappearablity”
Those hand gestures... 😂
Best video so far!
"You end up with code like Twitter. Am I too elaborate?" that's gold
“What is documentation?” got me good.
It’s daunting when you’re a young man showing up to your first job and there’s some grizzled old veteran who talks like this. You pretend like you understand what he is talking about. About a year or two ago I realized that I am now that guy as I was rambling something my colleague on the phone and after the call my wife said “you know I could hardly understand a single word of what you just said now”.
The repeated cuts to “V model” are bringing up mild trauma for me lol, having worked on a dysfunctional pharma IT project for 1.5 years
almost every line packs a personal punch
"Azuros Cloudapi" 😂
Microservices? Now your code looks like twitter!
Ahaha ))) this is a great one! ;))
Keyword overload!!!!!!!!!!!! LMFAO I literally started crying half way through
Didn't expect this to be so Italian flavored
As a systems engineer undergraduate, I have to agree... Processes! Teams to manage teams! Coding comes at the very end!
But the waterfall model is history nowadays
It is scary how relatable it feels
I thought he was skylability for so long but he's saying scalability 🤣