somehow i picture a scrum master as a gandalf like figure with a staff incorporating the jira logo and a indiana johnes like bullwhip made out of a network cable.
@@matantamim1 Go to your boss with a proposal to permanently fix cloud issues: A purchase request for a server park with a very large number where the price is supposed to be.
Nah he's the one making a mockery of the company by taking the paycheck, putting in 4 hours of work (and getting all the assigned work done in that time) then running his side-business for the rest of the week. The company deserves it though
"you can't make a pull request, this is a closed source project" Jared with a resume in one hand and lockpicks in the other "I don't care, I'm getting in that building one way or another to patch this fucker myself"
I’ve mercifully only ever had one product manager who didn’t come straight from a developer background and the 3 months I lasted after that were enough for me to have enormous sympathy for the people who spend all day every day trying to explain to morons how we cant fix issues in the product caused by a completely separate team in a separate country reporting to someone completely different
@@w花b The trick is to explain it to them like they are 3 years old using the baby voice in a recorded meeting. They will never ask you to fix shit again and just let you get on with your work.
@@jewelplatei never bothered with that i simply went straight to "are you f*cked? Or are you so incompetent as a human being you dont understand i dont control the internet."
My personal best was bullshit I ever had was during my student job at a start up. A sales person comes to me and asked me to do a prototype for our project on the Google glass 2. I told him it's not possible, but he interrupted me and said it has to be possible because they are required to deliver by contract... Well, the Google glass release was in about 6 months so I politely asked sales to contact Google for an early dev access to the Google glass framework. At this moment, he knew he fucked up. I decided to never work at a start up after finishing my studies. It was a good time for a student job and I learned a lot.
@@w花b Story points are an estimate of how much time will cost a task to be done. They can be useful but a lot of managment forgets that the point is to have the developers be more productive not to make them lose time on reunions or on Jira and not actually working
@@davidguillenmateu657 story points is not really a time to get something done, but rather complexity and size of the tasks. I seen too many managers fall into a trap of equating SP to time. Sure higher complexity usually leads to more time spent, but it depends on developer and resources available, risks, multi team dynamics, procedures in place etc etc
@@MG-Alexandrovich In my team we equal 1 point to 1 day of work, roughly, I see what you say but in the end story points are for tasks, and tasks are for a single developer, if you have one that need multiple developers its a sign that that task can and should be divided
Easy, I have to explain this almost once a week. "It's an external service provider. We opened a ticket with them and are waiting for a solution. That's the price for outsourcing."
Eh, I can deal with a non-technical product owner. The non-tech people def need to stay in their own damn lane tho. Shut up about blockchain, if I thought blockchain made sense in the architecture for a comms/reporting dashboard, I would have A) included it and B) checked myself into a mental institution.
Managers don't need technical knowledge. The job of a manager is so divorced from technical ability that none of them should need it. A manager manages, and they don't develop, create, or design. A manager brings out your capability, facilitate effective work, and organize tasks, that is their job, and they should never overstep their bounds.
@Ali-coder92 He was tired of the devs not fixing it, he applied, got the job, fixed the bug as his very first thing, the put 2 weeks notice the following day
Jared sounds like that one Manager who knows just enough about what he's managing to not get in his employees' way, but is also good enough at office politics to protect his department when the impossible is asked of him.
Use big words and lots of jargon and the sheep will just nod along. They want to be seen as smart but they have the IQ of single digits. The trick is to judge how smart they are and then manipulate their ego.
I usually double the time and round up to nearest logical number. In this case it would either be 10 mins or an hour depending on if I need to do any testing after it comes back online...
Literally my life. We have an integration with a credit bureau in an Eastern European country that goes down at least once or twice a month. Each time this happens, I get shit on by upper management and even some executives.
Get it in writing, or if they're too gutless to put it in writing themselves, recap in writing. Then CC whoever the shitter reports to with one or two coherent paragraphs . But also make sure your resume is up to date
Omg dude i got laid off from my tech job and have been horribly depressed and not sure if I even want to do software anymore.. but you fuckin nail it with these clips.
Using any jargon or acronyms of a specific speciality is always a bad idea when talking to someone outside that speciality. Especially if that hides something like “another company is the problem” from an uneducated superior.
nobody needs to know what aws actually is either. but your managers should know atleast what the name of your cloud provider(s) are, if they dont they have no idea of what your work is and most likely are trash
Lemme get this straight, we gotta learn new skills every week + leetcode + have a stem degree. But managements lazy ass can’t be bothered to learn the acronym of a platform they’re paying millions to each year????
What triggers me is that nobody can apparently say "AWS is a vendor upon who we rely on and it's their infrastructure that's having an issue. I don't have a number to call for them but I think you're already in touch with our account representative so can you ask them?"
I've got no issue with non-tech manager IF THEY UNDERSTAND THAT THEY ARE NOT TECH! I've had managers like that. Then don't know all the details, but they know enough to know what they don't know!
When i was in the navy my system i maintained had a very specific storage setup that required complete rebuilds often (like daily) because it would fill up these partitions that i couldn't really go through manually and i wasnt allowed to repartition the drives to be more efficient. When this happened it would take only around 20 minutes at most for me to do except for one of the servers which was between two and four hours. You don't even want to know how many angry officers i had to deal with that refused to hear that military equipment might just be built shitty and i quite kiterally cannot make it go faster without committing crimes and altering their software lol
My God, this hits too close to home. My remember my previous company partnering with another company to get data monthly for an AI. One month, that company ghosted our team so we couldn't collect any data. When we brought the matter to the boss, he just ask us why haven't we contacted them.
We're all people at the end of the day, a dev can 100% translate anything to a stakeholder. Doing it neatly and fashionable has more to do with talent than skill.
Dude stop. Lol I just got out of a meeting this week where leadership has asked me, the only junior Google cloud developer, and my ONE teammate, the primary GA4/GTM developer, to explain the ETL process for moving our GA4 data to AWS, the entire GA4 data architecture (cough, cough model), and that they *believe* the hardest part is *only* going to be connecting the pipeline. Literally the first thing I said was, "I was just in a JIRA meeting where the folks working on AWS informed the group that AppFlow isn't working. Until you get one of the primary modules of AWS working, this is not really a discussion. Secondly, the hardest part is going to be the engineering man hours to define every GA4 element/variable inside AWS/S3, which still won't give you 1:1 data, as stated by AWS on their developer pages" At that point my manager cut me off because I think he knew I was about to go full anti-hero, possible villain. Mind you, these are well tenured Sr. Directors and Directors of technology or products from our data management and business intelligence department.... for a massive, financial enterprise.
I once had a manager who wasn't technical, as least from a software dev stand point. I was working for a company doing something cellular, and everyone else understood that very well, but trying to explain anything software dev to the manager was like explaining green to someone who's medically blind. I tried for the sweet spot between too much & too little information, but those didn't overlap. it was actually a bit of a noticeable gap. he made me feel like I was holding the whole team back, but I was the first one done by the end of the project.
We can't fix AWS. " I don't want to hear excuses" " let me use a metaphor. You're at home and the power goes out, you try everything but it doesn't come back on, you look outside and you see some idiot drove into the pole knocking down the power line down... clearly you're not going to go climb the power pole and reconnect yourself, right? Sometimes you just have to wait for the service to be reconnected."
I feel the need to explain to technical types the "Shit on pipeline" In this clip, you are getting shit on by upper management. They dont care why or how only that it gets fixed. This is because just moments before this meeting, they were getting shit on by an executive who was getting shit on by board members. Those 4 messages? They didnt see them, a higher level manager did. This shit gets tossed down the pipe until it hits the wall called technical staff. Your manager may even understand the issue, but his might not.
A general rule of my computer: At bare minimum we wait 15 minutes before even looking at the problem. Sometimes software flaps. Once the 15 minute mark hits then we escalate it. We had one there last week which was funny, the lady calls in letting us know the phone lines have been down since 10, its now 5:30. If they were down that long, how come you never called, and suddenly its an emergency now? It wasn't even an issue with our equipment, it was the ISP doing work in the area.
@@deepspacecow2644 Not OP but the company I work for has two separate lines from two separate ISPs except, unbeknownst to us, one of the providers was leasing bandwidth from the other. When a construction worker accidentally cut a fiber line miles away, both of our internet connections died.
@@frontiervirtcharter No. I get what your saying, but there is a difference between my business and lets say Comcast which deals with both businesses and residential customers. My company doesn't deal with residential customers, which means that 99% of the call waiting traffic doesn't happen. The best way to describe it would be that Comcast call us to report an issue with a wide spread outage and our company investigates and fixes it. The only people that have our direct line outside of big cable companies are the handful of companies not on grid, ergo that one lady who didn't report an outage for 7 hours. In this example, Comcast controls your internet, we control the maintenance of the physical lines. So if a network line shuts off, we send someone out to fix it.
This sounds exactly like my operations manager(s); doesnt understand shit and cuts you off, demands results that aren't possible, misconstrues what is said and overpromises upper management/C-Suite... Too real 😂
This is when you sign an outrageous 2-year contract with another cloud provider, host it there, and when the boss asks about it you say "You wanted it fixed immediately. You're welcome"
There is always this Developer who socially exploits this kind of situation, takes responsibility to fix it to show a good face to the management when other colleagues clearly disagree it can be fixed...
Ngl that response may be perfect. He delayed the expectation by a few hours without specifying, delivered a spicy sarcasm that flew above that guy like it's fucking Starlink, and Cindy drafted a ticket with novelist as her side-job. Perfect imho. Cindy is interviewing with a publisher already.
They shouldn't need to if they understand and stick to the systems of their position. Managers are non-technical by nature. A manager facilitates, and a good manager listens properly. A manager doesn't need to know why something doesn't work. They just need to properly listen to when it might work again and organize tasks based on that change. A good manager does not overstep their position and so never needs technical skills.
I did basic first line support in a school (make sure its plugged in, turn it off and on again etc) the whole schools network went down over the whole city and one teacher just couldn't comprehend that there was nothing that i could do about it
I had a State Director ask me to drive to Dallas in the middle of an active tornado because the internet at our office was down. When they asked why the cellular backup hadn't kicked in, i had to tell them it was because the cell towers in the area had also been blown down. I politely declined and sent a picture of the current radar.
I once had a boss, who when I needed time to fix a bug in an app, and when the boss wanted to use the app and still got an error, suddenly nagged and said this is why IT can't be trusted
A person who dont even know what AWS actually is and what is actually going behind the screen, I have a question for Jared the "Manager". HOW EFFING EFF ARE YOU A MANAGER OF THAT EFFING TEAM?
