manager: we need to design an admin system for a veterinary centre

dev: ok, this is it, remember your training

class Dog extends Animal {}

Worst dev advice?

My first manager said, "You're young and single. You don't have a family. You should spend all of your waking hours on work."

Me thinking, "I understand the importance of extra effort the first few years but I do have a life. One that I intend to enjoy."

Our dev team got a new manager. On our first face 2 face meeting:

Manager: So, what technology are we using for web apps?
Me: TypeScript.
Manager: What is TypeScript?
Me: It's a superset of JavaScript.
Manager: Oh I know JavaScript, it's the latest version of Java, right?
Me thinking: He is joking. He tries to be the fun guy. Everyone knows the Java-JavaScript, ham-hamster joke.
Me later, also thinking: No he is not joking. Oh God, this is the end. We are all f*cked!

[Client]
We've noticed we gave you the wrong product prices for our new online shop.

[Dev]
Yeah, just login to the backend and fix them.

[Client]
But we don't want to use your fancy backend, we'll be using anyway soon - we want EXCEL!
Could you send us an EXCEL, so we can fix that?
How much will this cost?

[Dev]
Sure... here you are.
Not that much, takes about an hour.

[Client]
Great, you'll hear from us in a few days.

(a few months later...)

[Client]
We've finally managed to update the EXCEL. And btw, we've also added a bunch of columns with product pictures and new properties, highlighted products to delete red, inserted some comments with manual instructions and basically destroyed the entire data structure of this table.

Before I forget... also make sure to get this finished today, we have to go live ASAP. Our marketing campaign is already live.

[Dev]
Well, I'm sorry to say this, but this is not possible.
I'm currently working on another project and it will take me hours to clean up the data you sent me, before even starting to build an import tool for the new data you provided. Better stop the campaign and I'll do my best to get this done by the end of the week. Also it may be a bit costly.

(angry client calls immediately...)

(dev transfers to manager...)

(client transfers to client's boss...)

[Manager]
Ok Dev, I think I was able to explain it to them. However, it would be great if you spend day and night to get this thing out ASAP.

[Dev]
No problem...
I'll just do it by hand to get this out immediately.

(few days later; nearly done, exhausted)

[Client]
Hey Dev, here's another EXCEL.
We've just noticed there were a bunch of errors in the previous one. Please use this instead...

Manager: We need to setup the security in the Mexico server

Dev: You mean that 3rd party firewall add on?

Manager: Yes

Dev: And set up the billing on the Mexico account?

Manager: Yes

Dev: lol, sure thing I’ll create the ticket

Manager: What’s so funny?

Dev: Nothing

Ticket: Build wall and get Mexico to pay for it.

Me, a junior dev: * reports an important issue and a possible fix *

Senior dev 1: nah, it'll do just fine.

Senior dev 2: that won't be an issue, don't you see? It's under control, man.

Senior 3: why are you even here? Why are you even talking?

Manager: yeah, what could possibly go wrong?

* a year after releasing the product, one of the seniors got fired and another one was hired *

New senior: this thing is bananas, code is inconsistent and there's memory leaks everywhere, how does that even work?

Me: nobody believed me when I said that.

Manager: it did work very well, where's the issue?

Me: it's everywhere, goddammit! Don't you see?

New senior: junior dev is right.

Me: I've been a WHOLE YEAR saying that!

Manager: did you? Really? Nah, you didn't.

...

I'm tired of this shit.

If only more manager would think like this! Constant interruptions are poison to the performance of any dev team.

Manager: Why aren’t you working?

Dev: I am, I’m just not typing because I’m thinking an issue out.

Manager: Well what is taking so long? You haven’t written any code for like 15 minutes, you’ve just been doodling on your notepad.

Dev: I’m not “doodling”. I’m taking notes and trying to visualize the issue. It’s a complicated issue with application stat—

Manager: Well just simplify it then

Dev: ?

Manager: Instead of making it a complicated issue just simplify it and then it won’t take you so long. You’re likely overthinking it, I never spend more than 30 seconds thinking about any issue before coming up with a solution. That’s what makes me so effective at my job is my ability to be lean like that.

Dev: …this issue is a bit harder than deciding what to have for lunch

*came in this morning to see this conversation in slack from the remote teams*

Dev: Hey guys, I'm trying to push to the develop branch, telling me its locked. Is there a new process?

Lead dev: Yes I locked it because the repo is now dead, the last release that went out is the last for this year and ever for this app. Were merging this app with another, starting from the last release's code. We'll all have to swap over to the new repo soon.

Dev: ... eh ok I didn't put anything in the last release branch as it wasn't urgent. Normally our process is anything in /develop goes out in the new year. I've been merging to /develop for the last few weeks ... is that code now gone?
*14 question mark emoji reactions*

Lead dev: Yes
*27 angry emoji reactions*

Engineering manager: WHAT? when was this decided? When was it communicated?

Lead dev: oh I assumed my product counterpart had been spreading the messages around, have they not?

Several teams: no, nope, first i'm hearing of it.

Lead dev: Ok, i'll ask them what happened. Be aware then that most of the stuff thats going into develop now, most likely won't be allowed in until March. They want to prioritise releasing this new merged app and don't want anything to impact it.

Dev: So wait, i'm working on stuff now. What do I do? Where do I base the branch? Where do I merge?

<no response>

*My team comes into the office*

Dev: eeehhh ... what does this mean for our past 4 weeks of work? and all the stuff needed to go out in January?

Me: not.a.fucking.clue

One of the project manager came to one of our senior pro developer to say something. Before he even said anything the senior dev said:

Oh Fuck, not you again!

The pm politely left the area

Dance like noone is watching.
Encrypt like everyone is.
Sudo like you have backups.
Tag like you're a SEO.
Vim like you know how to exit.
Ticket frontend like you're the project manager.
Commit like saying "fuck you" in the message is appropriate.
Alert like you would use console.log
Design like you know CSS.
Comment like you aren't the only dev.
Code like PHP isn't outdated.

And finally:

Try to work like you know how to quit devrant.

Manager: Why haven’t you shipped any code today? It’s almost lunch.

Dev: Stuck on a bug

Manager: I’ll help you

Dev: Please don—

Manager: Have you tried thinking outside the box?

Dev: …Dear god please end my existence

Manager: You could try stack overflow too, have you ever used that site before?

Dev: 😮 🔫

Manager: Also sometimes bugs are caused by npm modules so rule that out first

Dev: *On knees praying to Zues for forgiveness and/or conveiniently placed lightning strike*

Manager: How come the intern does way more tickets than you?

Dev: Because you told me to only give him the easy ones since he either can’t do them otherwise or takes too long on the hard ones

Manager: Well how is he going to learn if we only give him easy ones?

Dev: That’s what I told you when you orig—

Manager: Assign him ALL of the hard tickets on your board immediately!

*Tickets closed per day drops significantly*

Manager: WHAT IS TAKING SO LONG ON THESE TICKETS!!!!!

Dev: …

Manager: This button is too dark, you need to lighten it. Have you no sense of design?

Dev: …

Dev: Hows this for an adjustment?

Manager: Wayyyyy too light now, jesus you need glasses if you think that’s good.

Dev: …

Dev: How about now?

Manager: It’s close, make it just a little more dark. God why does this have to take so long, do I have to hold your hand through this entire process!

Dev: …

Dev: There that good?

Manager: Yes that’s perfect! Send me a PR immediately so I can approve, we need to get this out ASAP, it’s critical!!

Dev: I can’t.

Manager: ????

Dev: There’s no diff, you had me gradually adjust the colour back to exactly what it was originally.

Manager: THAT’S IMPOSSIBLE IT LOOKS COMPLETELY DIFFERENT. HOW DARE YOU INSULT ME LIKE THIS, I HAVE A MEETING I NEED TO GET OFF TO BUT WE WILL BE HAVING WORDS LATER ABOUT THIS INAPPROPRIATE BEHAVIOUR.

Dev: …

Manager: Does anybody having any money saving ideas?

Dev: By switching our supplier from X to Y we could save $10,000/year and they have much better customer service.

Manager: So? I’m looking more for savings opportunities in the +$100k range. That’s a small idea, I’m looking for *BIG* ideas.

Dev: Do you have any big ideas?

Manager: No, but I really really want to save big money like that. I thought you would have something worthwhile.

Dev: $10,000 still a lot of money

Manager: I guess…. Ok we can do it. But don’t bother me with peanuts like this again.

Dev: ??? You asked me buddy

So i've been a dev manager for a little while now. Thought i'd take some time to disambiguate some job titles to let everyone know what they might be in for when joining / moving around a big org.

Title: Senior Software Engineer

Background:
- Technical
- Clever
- Typically has years experience building what management are trying to build

Responsibilities:
- Building new features
- Writing code
- Code review
- Offering advice to product manag......OH NO YOU DON'T CODE MONKEY, BACK TO WORK!

Title: Dev Manager

Background:
- Technical
- Former/current programmer
- knows his/her way around a codebase.

Responsibilities:
- Recruiting / interviewing new staff
- Keeping the team focused and delivering tasks
- Architecture decisions
- Lying about complexity of architecture decisions to ensure team gets the actual time they need
- Lying about feature estimations to ensure team gets to work on critical technical improvements that were cancelled / de-prioritised
- Explaining to hire-ups why we can't "Just do it quicker"
- Explaining to senior engineers why the product manager declined their meeting request

Title: Product / Product Manager

Background:
- Nothing relevant to the industry or product line what so ever
- Found the correct building on the day of the interview
- Has once opened an Excel spreadsheet and successfully saved it to a desktop

Responsibilities:
- Making every key decision about every feature available in the app
- Learning to ignore that inner voice we like to call "Common sense"
- Making sure to not accidentally take some advice from technical staff
- Raising the blood pressure of everyone below them / working with them

Title: Program Lead / Product Owner

Background:
- Capable of speech
- Aware of what a computer is (optional)

Responsibilities:
- Sitting down
- Talking
- Clicking random buttons on Jira
- Making bullet point lists

Title: Director of Software Engineering

Background:
- Allegedly attended college/university to study computer science
- Similar to a technical product manager (technical optional)

Responsibilities:
- Reports directly to VP
- Fixes problems by creating a different problem somewhere else as a distraction
- Claiming to understand and green light technical decisions, while having already agreed with product that it will never happen

Manager: This code you wrote violates the single responsibility principle!!

Dev: How so?

Manager: You have one function that you call in *MULTIPLE* places. That’s too much responsibility for one function! Functions should only have one responsibility!! Creeping the scope of a function beyond that is a TERRIBLE way to write code!

Dev: But why spin up multiple functions that all perform the same thing?

Manager: Well if a function has a bug in it and you use that function multiple places then that bug exists everywhere you use that function. If a function only has one responsibility then if it has a bug that bug will only exist in the single place it is called! You really should think first before asking questions like that.

Dev: …

Manager: You really shouldn’t be doing that

Dev: It’s in my job description

Manager: Yeah but you still shouldn’t be doing it.

Dev: Who should I hand it off to?

Manager: We don’t have anyone else to hand off that task to.

Dev: Ok, do I stop doing it?

Manager: 😡 Of course not, it needs to get done! I’m just saying you shouldn’t do it.

Dev: ???????????

Manager: I can’t believe you use Linux, that is such an outdated operating system. You need to get with the times and move to a more modern one like Windows or Mac. Literally NOBODY uses Linux anymore, do you still go to Blockbuster Video too? Ha!

Dev: …

I’m starting to realize that 80% of my job is resisting the urge to punch this guy in the face. Thanks goodness for remote work.

Manager: Hey what was that that you closed on your screen just now?

Dev: That popup? That’s NVIDIA letting me know that a new driver for my GPU is available.

Manager: Isn’t that for video games?

Dev: I mean that’s the reason many people opt into having a GPU but It’s not the on—

Manager: You are NOT allowed to play video games on your work computer!

Dev: This is my personal computer. It’s just an older GPU I popped onto this computer since otherwise it was just sitting in a drawer. My work computer is out of commission.

Manager: Well where is your work computer? How come you are not using it?

Dev: …Because of that blue screen of death issue we talked about yesterday.

Manager: Ok but that doesn’t give you permission to play VIDEO GAMES on your *WORK* computer.

Dev: …

Manager: You devs are constantly complaining about context switching, if you were on my level you would be able to multitask and switch from task to task without an— hold on I’m getting a text *tap* *tap* *tap tap* *tap* *send noise*

Manager: Right, what were we talking about again?

Dev: …

Manager: THE SERVER IS DOWN THE SERVER IS DOWN!!!!

Dev: Ok I’ll look into it

*5 mins later

Dev: Wow these are really strange logs, it’s like config values are being changed all over the place while I’m looking at it

Manager: Well I figured while you were looking into it I’d go i to the server settings and change everything I could find in order to try and get the server back up again. Two sets of hands are better than one, Is it up yet???

Dev: …No.

Manager: I THOUGT YOU SAID YOU’D LOOK INTO THIS. I NEED ANSWERS NOW. WHAT IS TAKING SO LONG?!?!?

Dev: …

Manager: Oh my god have you heard of libraries? I don’t even need to hire developers anymore, everything can just be done with code other people have already built for free

Dev: Well you actually cause a bit of technical debt when you use an abstrac—

Manager: EVERY TICKET SHOULD BE DONE USING LIBRARIES GOING FORWARD.

Dev: …This is going to implode…Can we at least fund some of the libraries we end up using?

Manager: WHAT? NO! Open source developers are suckers, what idiot puts code on the internet for free?? I shouldn’t be required to fund their stupidity. Let’s just take their stuff and make money with it.

Dev: *Phone rings 100th time today from recruiter*. One sec I have to take this call……It’s urgent.

Manager: Hurry up and login, I don’t have all day

Dev: One sec I have to lookup my password for the system

Manager: How can you not remember your password? Everything requires it these days

Dev: I use a different password for each service.

Manager: Wow you really like to overcomplicate things. Just use the same one for everything like I do, it’s way more efficient!

Dev: …

Manager: Good news everyone, I made a big giant announcement this morning that the app upgrades will be released today!

Dev: They definitely won’t be, we need another 2 weeks minimum. I told you yesterday

Manager: Ok well I already made the announcement that today was the day so too bad for you.

Dev: Doesn’t change the state of things

Manager: 😡 This announcement is supposed to motivate you to work faster! You guys are making me look bad when you don’t support me like this!

Dev: Working as fast as we can, it’s a 2 person dev team for 4 separate applications so it’s quite a bit to get pushed through

Manager: Ok well then stay extra then, we have to get this out asap. Tell your spouses they are not going to be seeing much of you until this work is done. People are starting to ask questions!!!!!

Dev: Not my problem, it’s done when its done. I’m not staying extra.

Manager: !!

// *************

Might be blowing my cover a little but what are they going to do? Fire me? Good luck getting this out without me. They’ve tried to replace me in the past but the cheapest person they could find was 60k more expensive than me and still couldn’t keep up. Probably they’ll ship the work overseas and the code will die in a dumpster fire and cost them even more. Ah well, just another company that doesn’t deserve code.

Manager: How long until the current set of tickets is complete?

Dev: Based on storyboard points it’ll be 1.5 weeks from now

Manager: That’s unacceptable! Let me take a look at the board and see if I can remove some low priority tickets.

*Later that day*

Manager: Oooo I found a bunch of really exciting tickets in the backlog that I forgot about. I’ve added them to the board.

Dev: Did you remove any?

Manager: Huh? Oh right. No, I looked and it all needs to get done.

Dev: With these new tickets added to the board our new estimate is 4 weeks.

Manager: WHAT?!? BUT I SPENT ALL DAY LOOKING FOR EFFICIENCIES!!

Dev: …

Manager: Why did you clear the data from the database? The client is now specifically requesting it and we don’t have it anymore!

Dev: You told me to.

Manager: Well why did you listen? It’s obvious now that that data was very important and should have been kept!

Dev: Last time you told me to do something that wasn’t a good idea I tried to explain why and told me not to question you ever again and that doing so was “disrespectful” and then threatened to have me fired. So now I just go along with what you say and let you suffer the consequences of not listening.

Manager: Well don’t do that then! It’s obviously not working very well! It’s ok to disagree with me you just have to make sure that what you think is something I agree with!

Dev: …

Manager: How come I go on vacation for 2 weeks and you are able to start, complete, and ship an entire sprint in that time where as when I'm around, the same amount of work takes months? I even got COMPLIMENTS from *the client* about how smoothly things went while I was gone...THIS IS COMPLETELY EMBARRASSING AND UNACCEPTABLE!

Dev: Well. I cancelled all of the status meetings, created tickets with clear expectations, didn't change those expectations, didn't add every idea that popped into the client's head during those two weeks to the current sprint, didn't pull anyone off their tickets to teach me to code, cut the budget for making degrading comments to zero, and incentivised everyone to work by allowing a half days on fridays to work on personal projects if we stayed on schedule.

Manager: THAT'S NOT YOUR JOB! I'M THE MANAGER AND ALL. OF. THOSE. THINGS. ARE. MY JOB! NOT YOURS!

Dev: ...I know.

Manager: You know you did good this week, take the entire day off tomorrow

Dev: Really?

Manager: Yeah my treat.

Dev: Can you send that to me in an email?

Manager: ….I mean yeah, but I don’t see why that is necessary

*** About halfway through The next day

Manager: WHERE THE FUCK ARE YOU?! YOU HAVEN’T COMPLETED A SINGLE TICKET TODAY OR REVIEWED A SINGLE PR OR EVEN SO MUCH AS ATTENDED THE STANDUP. EXPLAIN YOURSELF!

Dev: You said I could take the day off today?

Manager: YEAH BUT YOU’RE NOT SUPPOSED TO ACTUALLY TAKE IT OFF!! I WAS GIVING YOU THE OPPORTUNITY TO SHOW DEDICATION TO THE COMPANY BY COMING IN ANYWAY BUT NO YOU THOUGHT YOU’D JUST TAKE ADVANTAGE OF OUR GENEROSITY AND HAVE AN ENTIRE DAY TO YOURSELF?! GET YOUR HEAD OUT OF YOUR ASS, THERE ARE URGENT TICKETS ON THE BOARD!

Dev: …

Dev: If you force this to be done in this timeframe it will fail in a month.
Manager: Do it anyway.

A month later:
@@FAILS@@

Manager: Why didn't you tell me this would happen??

FUCK YOUUUUUUUUUUUUUUUUUUUUU

Manager: Feature C doesn’t work

Dev: We never built feature C

Manager: Nonsense, I remember feature C clearly!

Dev: It’s still in the backlog

Manager: But we had many meetings about it

Dev: Never got put on the board

Manager: Feature C is very important!

Dev: It was never assigned to anyone

Manager: What could possibly be more important than Feature C?

Dev: All the other features you placed on the board and assigned up until now

Manager: Well I need Feature C done asap! It should be top priority!

Dev: Ok then next sprint add feature C to the board and assign it to someone

*Next planning session manager leaves feature C in backlog in favour of other tickets*

*2 days later*

Manager: What is the status of feature C?

Dev: You opted to leave it in the backlog

Manager: BUT IT SHOULD BE TOP PRIORITY!

Dev: …

Manager: Have you fixed the problem?

Dev: What’s the problem?

Manager: We’re not here to discuss problems we’re here to discuss solutions!

Dev: …

Dev: *Recieves email from manager with several typos/grammar mistakes asking to open attachment with strange name and click on tinyurl style link*

Dev: *Flags as phishing*

Manager: Hey how come you didn’t action my email?

Dev: That was actually from you?

Manager: Yes.

Dev: …

Manager: I read an article today

Dev: oh here we go….

Manager: We must pivot to only functional programming, which means only using functions instead of classes

Dev: Actually functional programming is a bit more nuanced tha—

Manager: Any use of classes going forward is not allowed. Everything must use functions! Classes are an outdated way of programming, using classes is why we continue to miss our deadlines. Functional programming is lean, classes are waterfall.

Dev: What about the libraries we use? Many of those use classes

Manager: Wrap them in a function then, that way they are pure which is one of the requirements of functional programming. You would know that if you spent as much personal time as I do keeping up with the times.

Manager: "yeah so thanks for understanding we can't give you a payrise, by the way we need you to train the new guy we just hired who is your senior because even though he is more experienced than you as a c# dev he doesn't understand what an object is"

Me...

Dev: Hey our current server is starting to chug a bit. Can I get approved for $1200 additional spend to double the speed?

Manager: *Sharp inhale*. We need this project to cost as little as possible, we really can’t justify spending any additional money for any reason right now.

*2 days later*

Manager: YOU ARE APPROVED FOR $100,000 TO IMMEDIATELY IMPLEMENT SOMETHING RELATED TO NFTs IN ANY OF OUR APPS. THE BUSINESS NEEDS TO EXPAND INTO THE METAVERSE ASAP IMMEDIATELY. I NEED AN ETA BY EOD AS TO WHEN THIS CAN BE ROLLED OUT.

Dev: …

Dev: Ok issue fixed, you just need to log out and back in again on your end to receive the fix

User: It’s still not working

Dev: Did you log out and in again?

User: No why would I want to do that?

Dev: It’ll reset your locally saved login information which is causing the issue

User: I thought you said the issue was fixed?

Dev: On our end yes, we just need you to reset your end in order to receive the fixed version

User: Look I have been dealing with this issue for 6 months. Fixing bugs are your responsibility. I have too much to do, you have to get this fixed. *click*.

Dev: Yeah you submitted the bug ticket yesterday night though

Email from users manager later that day: <User> is saying you are refusing to fix this bug. This is unacceptable. Fix it or else I will escalate this. Also there are other bugs we noticed today too, fixing them is absolutely critical!

Dev: …

Dev: What other bugs did you notice?

*no response for 2 weeks and then:

User: Hey you can close this ticket, the issue seems to have resolved itself.

Dev: ….muppet.

Manager: So great news, we will also be building a new app this year!!

Dev: We only have 2 devs and we already struggling to maintain/build our current portfolio of applications. I don’t think we have the resources to support another.

Manager: Nonsense, this is a very small project management app that was requested by the CEO himself!

Dev: …We already have MS project, why can’t they just use that?

Manager: The executive team isn’t interested in learning MS Project, it’s way too complicated. They want us to build an internal version of MS Project one feature at a time so they can pick it up over time instead of getting overwhelmed with learning MS Project all at once. It also needs to have loads of customizable automation features so leadership doesn’t ever have to get “in the weeds” having to work with it. It needs to basically run itself!

Dev: …What about this is small?

Manager: Well that is the requirement.

Dev: …

Manager: *taps dev on shoulder* We need to do B

Dev: I know, you created a ticket for it yesterday

Manager: Yeah but it hasn’t been done yet. It needs to get done.

Dev: I’m currently working on A which is higher priority

Manager: Ok but B needs to be done too

Dev: I know, it’s next on my board

Manager: I’m just making sure you are aware of it

Dev: I am aware of it, it’s next on the board

Manager: Ok but make sure you do it after A

Dev: Yup it’s next up

Manager: Ok, don’t let anyone distract you

Dev: …

Dev: Why did you suddenly start adding random whitespace to the end of all of the files in your PRs?

Manager: IT’S NOT RANDOM!

Dev: ?

Manager: That’s a way I came up with for tracking my contributions. Every time I edit a file I add a line of whitespace at the bottom so it’s clear to everyone how much and how often I’ve contributed to the team. Although I haven’t been doing it this entire time so I had to make up for this by adding more to files that I *know* I’ve touched a bunch before. Just think! Especially with how big my PRs are compared to everyone else the tally of my contributions is going to get huge!

Dev: …

Dev: I think we should send Dev2 for some training and certification

Manager: We do not train people or have them certified. When you train people and especially if you have them certified they always leave the company for better offers so we no longer do that.

Dev: So the plan is to have a the company operated by a bunch of untrained uncertified people?

Manager: 😡 You are being disrespectful again

Mon: Ticket A is now low priority, Ticket B is top priority

Tues: Ticket B is now low priority, Ticket C is top priority

Wed: Ticket C is now low priority, Ticket D is top priority

Thurs: Ticket D is now low priority, Ticket E is top priority

Manager (Fri): You haven’t completed a ticket all week! What gives??

Manager (Following Mon): Tickets A, B, C, D AND E ARE TOP PRIORITY!!!!!

Dev: …

Dev: I’m taking a vacation next week

Manager: Good you need a break! I’ve put together a list of tickets for you to action during vacation since you’ll mostly be free during that time

Dev: Do you know what vacation means?

Manager: Well I work during *my* vacation

Dev: You write non-answers to emails and interrupt devs with status questions that are easily answered by a single glance at the kanban board. Also, you’ve just assigned a month’s worth of storyboard points to me on my week long vacation. We’d get more work done if you didn’t “work” during your vacation.

Manager: Well it all needs to get done! It’s the only way we can catch up and get ahead of schedule.

Dev: Why do you exist again?

Dev: So we’ve been working on X for about 2 weeks now, it’s about halfway do—

Manager: Btw what is the status of X?

Dev: I was just telling you

Manager: Oh, I wasn’t listening.

Dev: …

Dev: So as I was saying, we’re ab—

Manager: Oh and where are we at with Y?

Dev: …

Just got this little stinker added to my board this morning….

Ticket Title: Weird shit going on in app

Ticket Description: (blank)

Attachment: <Screenshot of app logo>

Manager: Well what do you think is causing it?

Dev: Causing what?? This ticket doesn’t describe anything at all

Manager: Well it’s a bunch of different things! The ticket is just a high level summary. Now how long do you think it’ll take to fix?

Dev: …

Manager: Everyone will be required to switch to Mac in the next couple of months.

Dev: Um, why?

Manager: Macs are more professional and developer focused than windows machines, I read it in an article. Plus they look way nicer.

Dev: Half of the applications we use don’t have a version that works on iOS.

Manager: What? How do you know?

Dev: I have a Mac for occasionally doing some work on the iOS app we support. I ran into that when I was setting it up as a development environment.

Manager: You have a Mac?

Dev: Yes

Manager: Why? How come you don’t use it for development?

Dev: …

Management: This project isn’t moving along fast enough, you know what we need?

Dev: An additional dev?

Management: No! An additional manager! We’ll have a meeting about it later today.

Dev: …

Dev: So how do you want this feature fixed?

Manager: It should work how it worked before.

Dev: I'm new to this feature, I don't know how it worked before or what is broken about it.

Manager: Well just make it work like it worked before.

Dev: I DONT KNOW HOW IT WORKED BEFORE THAT IS WHY I AM ASKING YOU. PLEASE TELL ME SO I CAN DO MY JOB.

Manager: Just how it worked before!

Dev: ...

Manager: ...

Dev: fuck you

Took yesterday off to sort out a new passport.
Today on the stand:

Manager: "So we've been trying to get app X running on a dev environment for client X but we couldn't expose it to them"

Me: "Well yeah it's a dev environment if you want to give them one give them access to staging"

Manager: "Oh well we're still going to give them access to dev because they asked for it. It's due for 10am but we couldn't get it to run. You have to get it running since we edited the config files"

*accessing dev environment*
half of config files is missing, random files committed to the repo, SSL certs manually edited, eth0 down and found swan vpn installed.

never taking a day off again.

Manager (via phone): You need to setup the CEO with access to the app IMMEDIATELY

Dev: Ok…What’s the occasion?

Manager: There is a big important meeting right now where we go over our achievements for the year and my plan was to have him log in and play around.

Dev: Likely would have been worth mentioning at this mornings standup.

Manager: Don’t be a smart ass. In fact, if you were actually smart you would have given him an account in the first place! So you’re just an ass then, what kind of idiot doesn’t give the CEO an account to an app like this?

Dev: Actually you specifically asked for him to be removed when I added him. “Unnecessary Optics” you said.

Manager: THAT’S BULLSHIT, I NEVER SAID THAT!!

Dev: It’s in our meeting minutes from 2 years ago.

Manager: STOP WRITING THE THINGS I SAY DOWN IT’S COMPLETELY UNNECESSARY.

Dev: I’ll make a note of that request

Manager: YOU ABSOL—ok looks like he’s waving me back in the room now the account must be working now bye. *click*.

Dev: Moron.

Manager: I’m so sick and tired of you devs whining about technical debt and how it’s slowing down our progress, so here’s the deal. You have until the end of this week to eliminate all technical debt in the codebase. After that I NEVER WANT TO HEAR YOU COMPLAIN ABOUT TECHNICAL DEBT EVER AGAIN!!!

Dev: …

Dev manager: great news guys. We’ve built a new tool to do automated testing on apps. We’ve gotten rid of the old Appium solution we were using and built this new one.

Me: why not just use the inbuilt native stuff? Click to record works really well.

Manager: nah we thought it would be more flexible to build it ourself.

Me: ... ok ... moving on ... how does it work?

Manager: well this new .jar, you download it, pass in a config file, setup up your simulator and appium and the jar will do everything for you.

Me: ... wait you said you hate Appium? Now you’ve built a wrapper around it? And it doesn’t even set everything up, you’ve to do it all by hand?

Manager: oh we had too, would be too much effort to replace it. Don’t worry we can now write all our tests in .yaml config files instead of using Appium.

Me: so we’ve lost the ability of auto-complete and type ahead, everyone has to upskill on a new tool, it offers no new features over what’s available out of the box and we’ll have to deal with new bugs and maintenance and stuff our self ... because we need more flexibility?

Manager: oh don’t worry. The guy who built it is staying here. He’s going to deal with bug fixes and add features. He’s only one guy, but he’s really sharp, it’ll be great for us and the team.

Me: ... ... ...

*audible noise of soul breaking*

Me: ... ok thank you. I’ll look into this new tool

Today I told a fellow dev to join devRant, and explained it was "like Reddit, but only for developers"

Wild manager caught us and said "Uh, just what everybody wants, some geek forum. Thank god I left that world a long time ago"

Fucker...

Manager: We do not identify as a tech company so don’t expect tech company salary increases this year

Dev: Well don’t expect me to bring a tech work ethic then

Manager: !!

Manager: Hey how come you left so many comments on my PR?

Dev: Well you’ve just recently learned how to code so there’s going to be a lot of things to learn beyond what you’ve picked up in your online coding tutorials. Don’t worry it’s only minor things like you put everything all in one function, left outdated comments in the code, have if statements 4 levels deep, have a console.log after every line of code some of which log .env variables, skipped error handling, cast to “any” a bunch instead of using more specific types, didn’t write any tests and some unrelated tests are now failing due to a circular dependancy.

Manager: THAT IS SO DISRESPECTFUL!!APPROVE MY PR IMMEDIATELY. IT WASN’T EVEN EASY FOR ME TO CREATE THE PR, NOW I HAVE TO MAKE AN UPDATE!? YOU’RE THE DEV, YOU SHOULD FIX IT NOT ME!! NEVER COMMENT ON ANY OF MY PRS AGAIN.

Manager: What’s taking so long on that PR?? It’s just some small styling adjustments

Dev: No it’s not you added an entire new calendar module that doesn’t work

Manager: Ok but besides that it’s just a small couple of css edits

Dev: You made styling changes in 50 files, half of which break our mobile responsiveness

Manager: Well then STOP talking to me and FIX IT if you’re so smart.

Dev: You also added a series of filters on a table in this same PR that cause th—

Manager: OK SO I GOT A BIT DISTRACTED THE FACT IS IT ALL NEEDS TO GET DONE SO IT DOESN’T MATTER IF IT’S ALL ON ONE PR SPLITTING THINGS UP INTO SMALL UPDATES IS JUST UNNECESSARY BUREAUCRACY AND IF YOU LIKE THAT THEN GO. WORK. FOR. THE GOVERNMENT!!!

Dev: …

fellow from the team was asked to do the estimate by manager - he said 2 weeks

then manager asked what if we add one more developer - he said, again 2 weeks and maybe add day or two

I was asked same question without knowing that they already asked fellow from the team same question - I said around two weeks, maybe day or two more! XD

as manager was confused and not satisfied with the estimates, goes to our team leader with the same questions - team leader said - 2 and half weeks and if you add one more dev to it, 3 weeks minimum

we didn't know that all of us were asked as manager did that behind our backs, in the end manager learned lesson in greed as we got to stick to team leaders estimate!

also that was very rude of underestimating someone's ability, same manager did had personal bias and frequently mocked us, for example when we said that that we will implement ML for cropping images at the right place (ie. crop part of the image where the face is) on the backend. Response was something like: 'You guys will do the ML? Are you shitting me? You're not /insert FANG company/!'

best team win ever!

second best team win ever is when whole team left the company in matter of weeks

Dev: Hey I found a bug in your PR

Manager: YOU BROKE IT ON PURPOSE!

Dev: … yes?

Manager : Developers are always over optimistic.

Dev : this task will take 4 days.

Manager : can't you complete it in 45 minutes? What are the complexities involved?

Dev : okay. I can. Thinks ** I'm a ninja developer** and I can complete this.

*** finishes it in 4 days***

Manager : That's what I said. Developers are always over optimistic.

Developer : -_-

*In teams meeting with client*

Manager: Yes we can do all of that and it will be actioned very quickly. We will make all of these feature requests top priority. We will set aside everything we are currently working on in order to get this done!

Dev: ...Are you writing any of this down?

Manager: I don't need to, I always remember everything!

Dev: Just so you are aware, I'm not writing anything down. You're going to need to create a ticket with requirements spelled out for each one of these promises you're making otherwise they won't get actioned by the team.

Manager: I know that!

Dev: ...

*Later that day*

Ticket Title: Action client feature requests TOP PRIORITY!!!

Ticket Description: *empty*

Dev: ...

Dev: Why do you have an identical if statement right below this one?

Manager: Because I want the code to double check, obviously.

Dev: …

Manager: Alright, we've decided we're gonna just going to accept PayPal and also credit card checkout through PayPal in the next two days!

Dev: ...

Manager: We can achieve this timeline, right?

Dev: ...

Manager: Alright, awesome to see your motivation! Let's do it!

Dev: YOU ANSWER PHONE CALLS, TALK TO PEOPLE AND 'STRATEGIZE' ALL DAY. YOU DON'T HAVE TO RELY ON THOUSANDS OF PEOPLE USING THE APP WITHOUT ERROR. THAT'S ON ME, NOT YOU, SO JUST SHUT THE FUCK UP!!!

Manager: ...

Dev: ...

Manager: You can’t define an async function without using await.

Dev: Yes you can.

Manager: Well you shouldn’t, there’s no point!

Dev: Yes there is. It can turn blocking synchronous logic into work performed concurrently. In this case the perform—

Manager: It’s called async *await*. Async *AWAIT*! Did you hear the two parts to that? You shouldn’t ever have one without the other. THEY GO TOGETHER. Worrying about concurrency is for people who use callbacks which just goes to show how out of date your skills are. I’m reading a book on javascript and there are so many advanced techniques out there that I haven’t even seen you use ONCE!

Dev: …

*I looked at the book he’s reading, it’s from the < ES6 era… no wonder he doesn’t see me using any of those archaic patterns/hacks/workarounds…*

Conversation I just heard

Manager: How's everyone doing?

Dev: I'm actually really tired. I've been having trouble concentrating and reading. I think I need a vacation.

Manager: Oh but that's good. You see, the brain is like a muscle. Today you lift 30kg, tomorrow you lift 40kg. So you will be able to handle more and more stress as you progress. That's great.

Dev: ...

Dev: I'm going to a engineering and robotics seminar this weekend

Manager: Stupid. Waste of time.

Dev: I also got invited to go to a 2 day tech and innovation conference

Manager: Another a stupid waste of time.

Dev: The CEO's son invited me and is paying for it, he said he thought it would be interesting to me.

Manager: ...Well as long as it's not on company time

Dev: It is on company time, I won't have time for tickets

Manager: WHAT!? YOU HAVE TO SAY NO, WE ARE BUSY!! WE CAN'T NOT HAVE YOU FOR 2 DAYS.

Dev: Duely noted you said that and you think the whole idea is stupid. Take it up with him I already RSVP'd yes.

Manager: 😡😡😡😡😡😡

“Your time zone is not my concern” - manager of the backend team

I asked if there’s another way for us to get test data into QA. That doesn’t involve us staying on until 9pm to get a backend dev to modify the db manually, everyday.

Manager: How come the push to prod didn’t happen?

Dev: We told you at the scrum yesterday. To reiterate, our dev environment was crashing so it’s not safe to push to prod until that is fixed.

Manager: Ok well lets set a goal to fix that and push to prod happens today so that it guaranteed happens.

Dev: That was our goal yesterday and it definitely didn’t happen.

Manager: I AM AWARE OF THAT. The corrective action is that this time compliance with the goal is 100% ABSOLUTELY MANDATORY!!

Dev: We’ll do our best, can’t guarantee anything until we figure out what the nature of what is occurring on dev though.

Manager: NO. I AM THE BOSS. YOU WILL 100% ABSOLUTELY COMPLY WITH THIS. THAT IS AN ORDER. YOU WILL SUCCESSFULLY GET THIS UPDATE OUT TO PROD TODAY. ANYTHING LESS THAN THAT SHALL BE CONSIDERED INSUBORDINATION. I WANT STATUS UPDATES EVERY 15 MINUTES ON WHERE WE ARE AT WITH THIS.

Dev: …

Dev: Can I get you to send me that request in an email?

*Manager leaves the meeting*

// *****************************

Job search is ticking along. It’s tough going though because I currently make ~120k and the best offers I’ve received so far are all ~70k because “You only have 2 years experience so you couldn’t possibly have the skills to be worth 120k. You are are junior level developer and 70K is already overpaying for you. We can pay you more later™. No we will not give you that in writing”. Ah well, the hunt continues.

Dev: * In the middle of pushing to prod *

Manager: Hey btw I forgot to mention the client asked for these 5 features awhile back as a part of this update and they just reminded me about them, I haven’t created tickets yet or told anyone about this. Will these features be included in the update that’s going out today?

Dev: …

Senior Manager: I have to use your app today, how do I do that?

Dev: Well first you log in, and then you clic—

Senior Manager: That’s way too low level, I only deal with things on high level! Explain it to me from a high level.

Dev: Use the app to orchestrate the visibility of action items to stakeholders and pivot the leverage towards buy-in.

Senior Manager: Hmmmm….

Dev: Agile.

Senior Manager: Aha! I understand how to use the app perfectly now!

Senior Manager’s Account: Last Login - Never.

Every 2 months without fail:

Manager: I don’t understand what the point of writing tests is. They only ever pass and when they fail we just fix them so they pass again! It’s completely redundant!!! An exercise in absolute futility!

Dev: …

Wait so I'm not allowed Spotify but it's alright for a manager to stream movies?

Don't give that we're not licensed to play music pretty sure we're not a licensed cinema either.

Either it's one rule for all or none at all enjoy your productivity dip from the dev team.

My first dev job. Me and another guy get hired at the same time. He will be the lead dev, and I’ll be the junior dev on a long term project. Project gets delayed (and eventually canceled, but that’s a different story), so the lead dev decides to give me programming challenges to test my skill level. I successfully complete the challenges, but they aren’t up to his standards. Belittles me in front of our manager. Afterwards I ask him to show me how he would have done it. The dude can barely type let alone show me the way it should be done. I say nothing to the manager.

A few weeks pass, it’s clear the project we were hired for is canceled, so we are given other work. They task the lead dev with porting the company website to Wordpress so non-devs can alter content. They chose Wordpress mainly because the lead dev said he is familiar with it. Two weeks later, no progress has been made. They ask me if I can do it, and I do it in 2 days including additional functionality that was requested. Manager asks me why I thought lead dev couldn’t do what I did. I said, “I don’t think lead dev knows what the fuck he is doing. I don’t think he knows how to program.” Manager says, “Huh.”

Several months later lead dev is still there, but has yet to work on any projects with any success. They finally let him go.

Glad to finally get that off my chest.

Manager: As you all know I called this meeting to discuss what we will do with all of the extra resources if we are done early. I was thinking a start a new ap—

Dev: We are not going to be done early. There are two weeks left and we are way behind schedule.

Manager: Don’t be so pessimistic! You never know when or how fast tickets will be completed.

Dev: Yes I do…I’m the one doing them

Dev manager: Can you fix this issue?

Me: Yeah, but i cant reproduce it using the explanation given in the ticket. Can i get a step by step guide and a confirmation that the issue is reproducible.

Dev manager: you're the lead dev, you figure it out.

askdjasfkjksadjkasd!!
Do you want me to spend an hour not developing things trying to guess? because that is how you make me spend an hour not developing things

Senior Devs made the Program Manager cry. Dev Lead did nothing to stop it from happening, Program Manager Lead was in shock.

Not only the manager/developer ratio is insane, but they are complaining about their top dev is getting an extra special status .. I just wish he sees this and quit immediately.

My current one, not Dev related but still...

Walked into my interview with a full head of hair and man bun with a big bushy beard.

Started the day after I shaved off everything for a charity thing, my manager went 3 days without realising who I was and just rolled with me being there .-.

Manager: I’m getting a strange error now….it says CORS? Any idea what that means?

Dev: Ezpz, just a matter of how many goats to sacrifice and incantations to recite

Manager: Are you serio—

Dev: Bring me my debugging pentagram

Manager: In order to increase business resiliency we will be doing cross training this week.

Dev: What does that involve?

Manager: Everyone will do everyone else’s job for one day each. After this you will all be considered trained so that if anyone can easily fill in for anyone else.

Dev: …

Manager: IT and I have decided that you will not be doing any rewriting of the legacy code. We paid a lot of money for it and throwing it away would be impossible. Instead you will create a “config file” that will customize the legacy code behaviour to whatever spec we need. IT said this would be possible and would be a very simple way of operating everything going forward. That way no future code needs to be written or maintained, it’s just a matter of changing this “config file” to match our needs.

Dev: Nobody in IT codes though.

Manager: Yes but they work with config files all the time. If you need to be shown how they work just ask them.

Dev: I know how they work it ju—

Manager: Good!! So that should speed things up quite a bit. See this is why developers need managers.

**at daily standup

Dev: and along with a push to production that is what I’ll be doing today

Manager: Good good, alright, nice….. ok who else hasn’t gone yet? Dev how about you go next

Dev: …I literally just went

Manager: What? Well what did you say then? Hey when is that push to prod happening? I feel like there should be one happening sometime soon.

Dev: …

Manager: In ALL cases if someone uses vanilla javascript to do something instead of a library then that is a sign they are an ABSOLUTE BEGINNER!!!

Dev: …

Dev: Hey that internal audit you asked me to perform didn’t go so well

Manager: It has too! I’ll get in a lot of trouble if it doesn’t pass.

Dev: Ok well it’s a lot of work to get it to a passing state, we have to dedicate a lot of resources to fix all these findings.

Manager: We don’t have any spare resources, they are all working on new projects! Why did you have to find things??

Dev: ….It’s a lot of hard to miss stuff, like missing signatures on security clearance forms

Manager: Ok can’t you just say that everything is all good? They’ll probably not double check.

Dev: I’m not really comfortable with that…Look all of these findings are all just from one member of the team consistently not doing their job, can’t you just address that with him and I can make a note on the audit that issues were found but corrective action was made? That’s the whole point of audits.

Manager: You don’t get it, if anything is found on the audit I’ll look bad. We have to cover this up. Plus that’s a really good friend of mine! I can’t do that to him. Ok you know what? You are obviously not the right person for this task, I’ll get someone else to do it. Go back to your regular work, I’m never assigning you audits again.

Manager: I NEVER SAID THAT!!

Dev: *Brings up email where he said exactly that*

Manager: I DON’T REMEMBER ASSIGNING YOU A TICKET TO LOOK THAT UP. GET BACK TO WORK!!

Dev: …

When I managed to minimize the processing time of the project I'm currently handling. It went down from 30min-1hr to 7min-15mins. The project owner was so happy, said it made his life easier. I was told I did a good job by my manager.

I feel like a real dev then and there. So whenever I'm having a bad day, feeling insecure, I try to remember that day when I was able to do something right. :)

Manager: I like nested ifs

Dev: They can be difficult to maintain

Manager: No they aren’t I write them all the time!

Dev: Have you ever maintained one?

Manager: No, I don’t do code maintenance. I don’t have time for it.

Project Manager: Hey Gid, we need to start migrating project-A to the new Server.

Me: Okay, I will inform Dev-Q.

Project Manager: Please do and treat as top priority!

Me: Hey Dev-Q, we need to migrate project-A to the new Server and we need to get it done asap.

Dev-Q: But I'm currently working on some critical bug XYZ which PM wants fixed before COB.

Me: I dunno maybe you want to speak with him.

Dev-Q: I was told to...

Project Manager: Yes! we need that done right away.

Dev-Q: What about the critical...

Project Manager: No! treat this as top priority the client just called.

Dev-Q: Okay.

Me: Any update yet?

Dev-Q: Yep but it seems like the database is quite large and the migration may take a while.

Me: Okay take your time.

Dev-Q: {hours later} Pheww done! All files and database migrated successfully.

Project Manager: Good good. So the critical bug XYZ was also completed and migrated to the new server right?

Dev-Q:

Dev: We need a better name than “Data” for this class. It’s used for displaying a set of tiles with certain coordinates so maybe TileMap would be a bit more declarative?

Manager: No I don’t like that. Data is perfectly fine, this class is for managing data so it’s perfectly declarative you just need to get better at reading code. If you have to change it then DataObject or DataObjectClass might be a bit more specific.

Dev: …

Dev: Your PR only addresses a quarter of the ticket

Dev2: *limps a commit so that now 1/2 of the ticket is addressed and creates a new PR for a separate ticket*

Dev: Your original PR only addresses half of the ticket

Dev2: *limps a commit so that now 3/4 of the ticket is addressed and creates a new PR for ANOTHER new ticket*

Dev: Your original PR only addresses 3/4 of the ticket

Dev2: *limps a commit so that now all of the ticket is addressed but two new bugs are introduced and creates a new PR for ANOTHER new ticket*

Dev: Your original PR introduces 2 new bugs

Dev2: *limps a commit addressing one of the two new bugs and creates a new PR for ANOTHER new ticket*

Dev: Your original PR still has one bu—

Manager: WOW GOOD JOB DEV2 THAT’S 5 PRs TODAY AMAZING! Dev you need to pickup the pace, you only have 2 PRs so far today. And get these PRs from Dev2 QA’d fast. He’s a rockstar!

Dev: …

*The 4 other PRs turned out to be equally dogshit*

Manager: Hey hurry up with QA, you’re holding Dev2 back!

Dev: …

Manager: I just created a new ticket! The website flashes when you reload it!

Dev: Yes, that's typically what happens when you reload a website.

Manager: ...

Dev: ...

I'm starting to fucking hate the word 'done'.

Scenario 1:

Boss: How's the spec coming along?
Manager: Oh, it's done.

Manager to me: Hey can you get it done?
Me: Why would you call it done? There's a days worth of work and it's only half done. Boss wasn't even rushing it yet.

Manager: Too late I've already committed it. I'm sure it's simple anyway. Just do it.

Scenario 2:

Manager: Hey is it done?
Noob dev: Yea it's done.

*Commits half assed incomplete sphagetti shit that breaks stuff*

Manager: Well done. Completed so quickly.

FUCK THIS SHIT.

Manager: Hey Dev I need to do QA on this PR.

Dev: That PR is not finished yet

Manager: Well do QA now anyway, that way when it is finished it can be merged in right away since QA has already been done on it. It’s a project management technique called “fast-tracking” and it improves efficiency.

Dev: …

Manager: We should do X with the database

Dev: That will cause issue Y

Manager: But I read an article that said that issue Y wasn’t a problem

Dev: It did?

Manager: Well it didn’t mention issue Y

Dev: …

Manager: How’s the progress coming along?

Dev: The section of code I’m working with is one of the more difficult ones so it’s a little slow

Manager: Ok well I didn’t write that section of the code

Dev: I’m not saying you did I’m just giving you the status update that you asked for

Manager: Ok well I can’t really do anything about that so how about you tell me something I can do something about instead of just complaining about code THAT I DIDN’T EVEN WRITE!! *Marks self as offline*

Dev: …

“Fullstack dev continues to be consistent”

We’d an enhancement request where we needed to support Ionic apps. Our manager didn’t know anything about Ionic so she asks us what it was instead of asking Google.

Manager: so what’s this Ionic thingy?

Me: Ionic issss.... (gets interrupted by Fullstack dev)

Fullstack dev: so the thing is ... it’s like... (consistent with his opening lines as always) it’s a third party plugin which converts react app and html pages to native code.

Me: (thinking of sacrificing him at the altar of Lucifer)

Manager: Nice!

More to come.

Manager: I don’t understand! How come you take twice as long to do tickets as anyone else but your PRs are stuck in QA for half the time as anyone else??

Dev: …

A day before the deadline.
Project manager decides that we are ready to publish the same app with the iPad version too. Without asking dev team.
+Yep, sure. What could go wrong?
I'll keep you posted.

If I flag a bug on your PR don’t fucking do this:

if (bugOccurs()) handleBug()

Fix what is causing the bug, don’t bandaid it.

Manager: wElL yOu NeEd To ExPlAiN tO tHeM eXaCtLy HoW tO fIx It, hOw ArE tHeY sUpPoSeD tO kNoW?!

Dev: …

Manager: We will be building a new app. THIS TIME EVERYTHING MUST BE ABSOLUTELY PERFECT, ANYTHING LESS THAN TOP QUALITY WORK WILL BE REJECTED!!

*Not even 2 days into the new project*

Manager: Ok that’s good enough, we can fix it later. Can you go quicker on the next feature? Just sacrifice a bit of quality so we get these tickets closed as fast as possible. I said we can fix it later. Getting tickets closed asap is top priority.

Dev: …

So that coworker of mine who got promoted to manager keeps continuing on abusing her new power. She convinced upper management to implement a new policy where you would be disqualified from your monthly performance incentives if you take 2 total sick days a month. She says this is to reduce the number of sick days people take, which of course upper management loved hearing.

By the way, since she's a manager now, this particular policy doesn't affect her - it only applies to us in the trenches. She can still take as many sick days as she wants, since being a manager she can work from home.

Needless to say, save for a couple of suck-ups, she's lost a lot of friends and made a number of enemies in our department, particularly on our dev team.

Manager: That last dev you hired is working out well. Where did you get him from?

Dev: *Looking at new hire’s resume which only contains a single bootcamp and nothing else*

Dev: He’s a rescue.

HR: Hey we heard about all of the apps you are building and we were wondering if you could build one for us too

Dev: Well I’d have to run it by my manager first, what kind of app were you looking to build?

HR: Ok basically it’s a button that when you press it it completes the list of daily tasks that normally take us all day everyday like payroll and attendance reporting.

Dev: You…. want me to…automate your entire job away?

HR: No! We would be the ones to push the button😡.

Dev: I….. I’ll…. I will pass that along.

Manager: "We can't have new releases breaking older versions of the mobile app!!!!! We'll lose all our customers!!!!"

fullStackChris: "That's fine, we can do API versioning, but it will take some time to implement, I'll have to be quite careful and write some tests to implement it. Probably 2-3 weeks..."

Manager: "NO WAY, THAT TIME ESTIMATE IS WAY TOO LONG, WE DON'T HAVE TIME FOR THAT!!!"

fullStackChris: "So how do you wanna support multiple versions of the app without doing any sort of versioning?"

Manager: "...we'll think of something!"

Dev: "..."

And with 99% certainty, I expect to hear this in a week or two:

Manager: "fullStackChris, we'd like to introduce you to the highly technical concept, API versioning. It's a way to version the API so we can support multiple versions of the application our customers use! It's amazing! Please implement this immediately so we can support multiple versions of the application!"

Sigh... each day managers learn a bit more how physical reality works... you can't have your cake and eat it too.

Be me, new dev on a team. Taking a look through source code to get up to speed.

Dev: **thinking to self** why is there no package lock.. let me bring this up to boss man

Dev: hey boss man, you’ve got no package lock, did we forget to commit it?

Manager: no I don’t like package locks.

Dev: ...why?

Manager: they fuck up computer. The project never ran with a package lock.

Dev: ..how will you make sure that every dev has the same packages while developing?

Manager: don’t worry, I’ve done this before, we haven’t had any issues.

**couple weeks goes by**

Dev: pushes code

Manager: hey your feature is not working on my machine

Dev: it’s working on mine, and the dev servers. Let’s take a look and see

**finds out he deletes his package lock every time he does npm install, so therefore he literally has the latest of like a 50 packages with no testing**

Dev: well you see you have some packages here that updates, and have broken some of the features.

Manager: >=|, fix it.

Dev: commit a working package lock so we’re all on the same.

Manager: just set the package version to whatever works.

Dev: okay

**more weeks go by**

Manager: why are we having so many issues between devs, why are things working on some computers and not others??? We can’t be having this it’s wasting time.

Dev: **takes a look at everyone’s packages** we all have different packages.

Manager: that’s it, no one can use Mac computers. You must use these windows computers, and you must install npm v6.0 and node v15.11. Everyone must have the same system and software install to guarantee we’re all on the same page

Dev: so can we also commit package lock so we’re all having the same packages as well?

Manager: No, package locks don’t work.

**few days go by**

Manager: GUYS WHY IS THE CODE DEPLOYING TO PRODUCTION NOT WORKING. IT WAS WORKING IN DEV

DEV: **looks at packages**, when the project was built on dev on 9/1 package x was on version 1.1, when it was approved and moved to prod on 9/3 package x was now on version 1.2 which was a change that broke our code.

Manager: CHANGE THE DEPLOYMENT SCRIPTS THEN. MAKE PROD RSYNC NODE_MODULES WITH DEV

Dev: okay

Manager: just trust me, I’ve been doing this for years

Who the fuck put this man in charge.

Laziest dev thing I've ever done.

An annoying "I-do-nothing-but-delegate-and-make-fuzz" manager proposed to create a new application with redundant functionalities, that would take me at least half a year to build.
Practically, the app would never be used and I didn't want to put effort in that monstrosity.

So, naturally I...

Pressure the right people, schedule numerous meetings, become the project manager for all internal applications and... I cancel the project.

Manager: Messages not visible! bug ticket!!!!

Dev: oh fuck, there's an issue with our chat system, not good! _inspects ticket_ oh, it's just a display issue that actually is according to the previous spec, yawn...

Dev: please describe the bug better next time, I though we had a major outage, this is simply a small design issue...

Manager: ...

Dev: ...

I think I'm quitting soon guys. I literally do not get paid enough to deal with these incompetent idiots each day.

Meanwhile:

Management: forget your shitty salary, take one for the team, you get 3% of the shares in the company!!!!

Dev: what fucking shares, you haven't even converted to a corporation yet, THERE ARE NO SHARES

Management: ...

Dev: ...

Oh yeah and they called me at 6:30 PM today: "so i guess you are winding down for the day"

fuck outta here i haven't been working since 5 you fucks

jesus i swear some people need to screw their fucking head on straight, so far gone into the hUsTlE CuLtUrE they don't even know what reality is anymore

Senior manager: I cant understand how this project has taken so long?
Me: Well you hired me as a C# WPF developer and then asked me to deliver an android app without any kind of training so i had to teach myself app development and reverse engineer the undocumented protocol it needs to use to communicate with our product.
Senior manager: Ok. I get that, but it should only take around 3 months to get up to speed though right?
Me (to myself): how in the hell? New platform, self teaching, undocumented protocol for a complex low level real-time system, other responsibilities taking at least 50% of my time and i should be as productive as an outsourced app dev company in 3 months???!! FFFFFUUUUUUUUUUUUUU!!!!!!!!!

Unaware that this had been occurring for while, DBA manager walks into our cube area:

DBAMgr-Scott: "DBA-Kelly told me you still having problems connecting to the new staging servers?"
Dev-Carl: "Yea, still getting access denied. Same problem we've been having for a couple of weeks"
DBAMgr-Scott: "Damn it, I hate you. I got to have Kelly working with data warehouse project. I guess I've got to start working on fixing this problem."
Dev-Carl: "Ha ha..sorry. I've checked everything. Its definitely something on the sql server side."
DBAMgr-Scott: "I guess my day is shot. I've got to talk to the network admin, when I get back, lets put our heads together and figure this out."
<Scott leaves>
Me: "A permissions issue on staging? All my stuff is working fine and been working fine for a long while."
Dev-Carl: "Yea, there is nothing different about any of the other environments."
Me: "That doesn't sound right. What's the error?"
Dev-Carl: "Permissions"
Me: "No, the actual exception, never mind, I'll look it up in Splunk."
<in about 30 seconds, I find the actual exception, Win32Exception: Access is denied in OpenSqlFileStream, a little google-fu and .. >
Me: "Is the service using Windows authentication or SQL authentication?"
Dev-Carl: "SQL authentication."
Me: "Switch it to windows authentication"
<Dev-Carl changes authentication...service works like a charm>
Dev-Carl: "OMG, it worked! We've been working on this problem for almost two weeks and it only took you 30 seconds."
Me: "Now that it works, and the service had been working, what changed?"
Dev-Carl: "Oh..look at that, Dev-Jake changed the connection string two weeks ago. Weird. Thanks for your help."
<My brain is screaming "YOU NEVER THOUGHT TO LOOK FOR WHAT CHANGED!!!"
Me: "I'm happy I could help."

Developer came to our area to rant a bit about a problem he was having with Xamarin. A particular android device was receiving a java runtime error trying to de-serialize data from a WCF contract. What he found was not to use WCF and use WebAPI (or a simple REST service that sent back/forth JSON).

When he proposed changing the service (since the data transport didn’t really matter, he could plug the assembly into a WebAPI project in less than an hour), the dev manager shot down the idea pointing him to our service standard that explicitly stated no WebAPI (it’s in bold letters).

I showed him the date on the “standard”, which was 5 years ago. We have versioning on our sharepoint server, so I also him my proposal notes on the change request document (almost two years before that) stating we should stop using WCF in favor of REST based web standards. Dev manager at the time had wrote in his comment “Will never use REST. Enterprise developers prefer RPC.”
He just about fell over laughing when I showed him this gif.

Manager: I don’t understand what is so complicated about this feature. Under a certain set of conditions do one thing, under a separate set of conditions do another. It’s just an if else statement! Those take seconds to write!

Dev: The problem is the memory required to calculate the conditions is quite cumbersome

Manager: Well then find a faster way! It’s just an if else!

Dev: …

Talent Acquisition/HR: 🤪

Dev: 🤪

Technical Interviewer: 🧐

Dev: 🧐

Hiring Manager: 🤡

Dev: 🤡

This strategy has yielded some dishearteningly successful job application results this week.

I fucking hate people who tell me what i should do when they obviously dont know a fucking inch of anything related to the dev world fucking idiots ruining my day with fucking retarded orders.

I AM THE DEV UR THE FUCKING MANAGER STAY AT UR FUCKING PLACE

If you are in a job interview with the dev manager of java and the other dev manager of C++ and a fundamental discussion starts:

Dropbox TLS 1.0 & 1.1 is deprecated
Dev: we need to upgrade our projects
Manager: we don't have time for that. can you call to their helpdesk, so we can keep using our projects w/o upgrading?
Dev: ....
Manager: call them!
Dev: ...

I learned a valuable lesson today about the life of a manager. I’m not a manager, but I am a senior level dev.

Today I was told there wasn’t room on the new team for 1 person, and I had pick that last team member. I had to choose between a friend who really isn’t cut out to be a dev and a non friend who is a better dev.

I talked through my reasoning and ultimately chose to put the friends job in jeopardy. They told me that I had solid leadership traits for being able to separate my emotions from my decision making. But I felt like a piece of shit.

I cried back at my desk. The friend doesn’t know yet and I can’t tell them. Is this what execs feel when they have to let people go?

Manager: How's the site going. Can I see it?

Dev: ya sure

M: what's that

Dev: that's a * it means some restrictions apply.

M: hmmmm

M: make it a diamond

Me passing time on the weekend

Random call from unknown number

Turns out it's the manager

M: hey , how is your weekend going ...

Me: nothing much ... Whatsup ?

M : yeah well , we wanted to push some minor adhoc fixes as some clients wanted it urgently

The Devops folks need developer support . Can you pitch in and monitor

Me : I'm not aware of what changes are going , i don't think i can provide support

M : don't worry it's minor changes , it's already tested in pre prod , you just need to be on call for 30 mins

Me : ugh okay .. guess 1 hr won't hurt

M: thanks 👍🏽

Me: *logs in

*Notices the last merged PR
+ 400 lines , implemented by junior dev and merged by manager

*Wait , how is this a *minor* release...

*Release got triggered already and the CI CD pipeline is in progress

*5 mins later

*Pipeline fails , devops sends email - test coverage below 50%

Manager immediately pitches in ...

M: hey , i see test coverage is down , can you increase it ?

Me: and how do u suppose I do that ?

M : well it's simple just write UTC for the missing lines ... Will it take time ?

Me : * ah shit here we go again

Yeah it will take time , there are around 400 lines , I am not aware of this component all together

Can you ask junior dev to pitch in and write the UTC for this

*Actually junior dev is out on a vacation with his girlfriend

M : well he's out for the weekend , but
as a senior dev , i expect you to have holistic understanding of the codebase and not give excuses ,
this is a priority fix which client are demanding we need this released ASAP

Me : * wait wat ?

---

I ended up being online for next 3 hours figuring out the code change and bumping up the UTC 🤦🏾

Manager: Here's the design for the next feature, we're ready to hand it over to the consultant

FullStackClown: Uh... okay... is it spec'd out with requirements?

Manager: Huh?

FullStackClown: Well, already look at this design and user flow, did you consider what happens when <insert edge case X here>, <insert edge case Y here>, or <insert edge case Z here>? How is the consultant going to know what to put in for business logic if you don't even know or define it yourself?

Manager: Huh?

FullStackClown: Sigh... yeah, I'm too busy right now to be a kindergarten teacher, come back in a few days once you understand how your own feature is supposed to work

Manager: ...

Dev: ...

On my first dev job ever, I got sent to the client's office after studying CSS on my own for 2 weeks.
Client: "So, you're the great expert your manager told me about?"

I was on vacation when my employer’s new fiscal year started. My manager let me take vacation because it’s not like anything critical was going to happen. Well, joke was on us because we didn’t foresee the stupidity of others…

I had to update a few product codes in the website’s web config and deploy those changes. I was only going to be logged in for 30 minutes to complete that.

I get messaged by one of our database admins. He was doing testing and was unable to complete a payment on the website. That was strange. There was a change pushed by our offsite dev agency, but that was all frontend changes (just updating text) and wouldn’t affect payments.

We don’t want to enlist the dev agency for debugging work, especially when it’s not likely that it’s a code issue. But I was on vacation and I couldn’t stay online past the time I had budgeted for. So my employer enlists the dev agency for help. It’s going to be costly because the agency is in Lithuania, it was past their business hours, and it was emergency support.

Dev agency looks at error logs. There are Apple Pay errors, but that doesn’t explain why non Apple Pay transactions aren’t going through. They roll back my deployment and theirs, but no change. They tell my employer to contact our payment processor.

My manager and the Product Manager contact Payroll, who is the stakeholder for our payment gateways. Payroll contacts our payment gateway and finds out a service called Decision Manager was recently configured for our account. Decision Manager was declining all payments. Payroll was not the person who had Decision Manager installed and our account using this service was news to her.

Payroll works with our payment processor to get payments working again. The damage is pretty severe. Online payments were down for at least 12 hours. Our call center had logged reports from customers the night before.

At our post mortem, we had to find out who ok’d Decision Manager without telling anyone. Luckily, it was quick work. The first stakeholder up was for the Fundraising Dept. She said it wasn’t her or anyone on her team. Our VP of Analytics broke it to her that our payment processor gave us the name of the person who ok’d Decision Manager and it was someone on the Fundraising team. Fundraising then starts backtracking and says that oh yes she knew about it but transactions were still working after the Decision Manager had been configured. WTAF.

Everyone is dumbfounded by this. How could you make a big change to our payment processor and not tell anyone? How did our payment processor allow you to make this change when you’re not the account admin (you’re just a user)?

Our company head had to give an awkward speech about communication and how it’s important. The web team can’t figure out issues if you don’t tell us what you did. The company head was pissed because it was a shitty way to start off the new fiscal year. Our bill for the dev agency must have been over $1000 for debugging work that wasn’t helpful.

Amazingly, no one was fired.

Manager: *taps dev on shoulder* Hey I noticed a minor bug I think

Dev: Sigh…. So then create a ticket for it

Manager: Can’t you just fix it right now?

Dev: I can but I’m currently working on that other issue you told everyone was “top priority” at the morning status meeting. Should I switch to actioning this minor bug instead?

Manager: Don’t switch just multitask and work faster!

Dev: …

Action takes place during demo to the stakeholders.
Manager : During the demo we will show a working prototype of new functionality. In this sprint we focused on that feature not on UX. Please do not pay attention to UI and focus on business values
*Dev starts sharing screen*
*1 sec after*
Executive : This is unacceptable. It looks gross, why you don't use default controls.
Manager : We did, this is how they look like, but please do not pay attention to UI, it is not finished
*Dev continue presenting*
*1 sec after*
Executive : I see missing comma in that sentence. It is unacceptable to show features in that state, lets move on to another team.

It was really large feature working as a charm, but they focused entirely on unpolished UI :/

Manager: The way you built this doesn’t accommodate any of my future plans!

Dev: What future plans?

Manager: I have a bunch of different ideas, I haven’t decided which ones to go with yet or how it will all work but you’re making it so we’re running out of room in the UI. It’s too busy, you need to clean it up so we can add more stuff!

Dev: …

<Email thread>

Manager: Hey @iiii, please, create stories for {things that shall be done}. You will be responsible for that implementation next sprint.

Me: *procrastinating like a bitch*

**several hours later**

Dev from another team: Actually, we discussed that with {upper management guy} and it seems like those things are unapplicable for current project, so we'll send a letter to {client} to remove those requirements.

Manager: @iiii, don't create stories.

</Email thread>

Me: *welp, good thing I did exactly nothing so far*

Me: I prefer to make sure dev is fully separated from prod, that way if we fuck up, it doesn't matter.

Manager: It's fine, the service isn't fully deployed and dev/prod are named differently.

Me: runs ansible script to stop dev
*prod breaks*

Me: Huh. Wonder why that happened.

developer: hey, want to hear a joke?

manager: sure

dev: what did the developer say to their manager after doing flaming shots in the server room and accidentally setting fire to all their systems?

manager: i don't know, what did they say?

dev: "hey, want to hear a joke?"

It today's team meeting my manager asked, "What is GitHub?"

Seven years leading the group. Hired with no dev knowledge. Can't be bothered to acquire any.

Manager: You know you really shouldn’t pay off your mortgage faster than you absolutely have to. It’s the cheapest money you’ll ever get!

Dev: I’d rather work towards being debt free. Besides my RRSP (401k) is already maxed out

Manager: RRSPs are a scam! TFSAs (Roth IRAs) are way better

Dev: My TFSA is maxed out too

Manager: 😡 You still shouldn’t pay off your mortgage!

Dev: …

Today on "I'm Not Crazy, I'm Just a Burnt Out Dev".

Project Manager: "What day would prefer to demo your work?"
Me: "Tomorrow or Wednesday"
Project Manager: "Tomorrow is Wednesday"
Me: "O"
Project Manager: "O"
Me: 🤝
Project Manager: 🤝

Anyone else having problems remembering which day of the week it is? 😂😂

Dev: (Watches user print out screenshot of maintenance app to do list, walk across facility to printer. walk across facility to equipment and check things off on paper, then walk across facility back to their terminal and copy the findings over.)

Dev: We made the app responsive so they could do that on a mobile device. Why are they printing?

Manager: Printers are cheaper than getting more tablets.

Dev: …

Dev: Can we at least get a printer at each terminal so they don’t waste so much time walking across the facility?

Manager: That’s too many printers to maintain. It’s easier to just have one.

Dev: …

Tester Dev. And Manager

Nature of Startups

Sales executive go and sell the features which are not available in the product.

They come back and inform them to the manager, then the manager makes the request to dev team to do the features.

After all these the discussion will be made in the morning and delivery is expected by evening.

New spin on the Manager / Dev format!

Recuiter: WE NEED AN ABSOLUTE NODE EXPERT, NODE NODE NODE, WE LOVE NODE! WHAT IS YOUR NODE EXPERIENCE?!?!

Dev: Well I've had exposure to it since it was nearly new, all the way back in 2012, and since my professional career started about 7 years ago I've used it fairly often on a per-project basis.

Recruiter: WELL HAVE YOU BEEN USING IT DAILY FOR THE PAST 5 YEARS!?!

Dev: Well no, as I said I've used it for specific projects... anyway, there are these things called weekends...

Recruiter: WELL WE ONLY WANT NODE ZOMBIES SO SORRY.

Dev: Thanks for reaching out and wasting my time.

Recruiter: ...

Dev: ...

God recruiters are like robots, don't they understand senior-level engineers are language agnostic?

Ah the day before launch of a new app. And right on schedule the businesses is attempting to completely alter their requirements including a COMPLETE OVERHAUL OF THE DATABASE MODEL TO ADDRESS AN ISSUE THAT HAS ALREADY BEEN FIXED. I wish they would share the drugs they are clearly on so I could also live in this dreamland delusion where you can turn something completely on its head right on the finish line and expect everything to go well.

Manager: Hey I think I have a solution to that performance we talked about last week

Dev: I already fixed it, it only takes 1 second instead of 30 now.

Manager: Ok but I’ve also figured out a solution. If we completely change the entire database model that one query could potentially be even faster according to my understanding of how databases operate.

Dev: I fixed it without the need for that, actually it was just a matter of better conc—

Manager: I think we should go with MY solution. Drop everything and restructure the database immediately! Be quick, as you know we launch this application tomorrow! Have an extra coffee today and just crush it out, don’t overthink this either just do it.

Dev: …

Today I learned a lesson from corporate survival 101.

The difference between get it done vs get it right.

Boss, manager always want to get it done, while developers always want to get it right, most of the time. If you don't listen to your boss, manager and insist get it right, will eventually cost your job. I saw many get it done code, either the dev moves to another team or already left. They avoid their own code forever.

Perhaps be a good student, not the smart student is a good way to survive. Thought????

Manager: Dev, you will submit to my leadership and surrender all common sense to agree with what I say or face consequences.

Dev: Manager, Fuck you!

Dear non-webdevs,

We don't talk bad about you. Why somayou mad at us? :D

"What we can do to get all on time? ", manager asks
"Can we have 4 more developers on the project?", dev asks
"No, that's not gonna happen. Let's be realistic", manager says
"Is it realistic to ask 3 devs to ship 20 features in a week, reviewed and tested?" dev asks
"Actually 2 of you, because our contractor goes into a vacation. But you can do overtimes, can't you?"
"I prefer not to but even in that case I can't guarantee that as it's not realistic. But at least can I leave earlier and work more from home more because there are severe delays on the train lines and if I have to commute 4 hours a day it won't help", dev says
"Well, I'm not sure if that's a good idea. You have to communicate with people, you know. We have to ship things. But we can discuss this tomorrow as I have to leave early today. I have to take my kids from school"

Really? Wtf?

So I just got let go because there was not enough work to keep me full time. Yet my manager was farming out dev work to a 3rd party developer... Fml

Manager: What's your time estimate on that latest ticket?

Dev: It's literally written in the "time estimate" field on the ticket, even in standard human units like "hours", "minutes", and "seconds"

Manager: ...

Dev: ...

Dev: You’ll want to store money values such as $2001.01 as 200121 when using javascript.

Manager: Why? That’s stupid.

Dev: Javascript doesn’t behave with decimals the way you think. It’ll show up as $2001.01000001 when you least expect it

Manager: Well I’ve never had that issue before! Besides that’s only a fraction of a cent off, that won’t even matter!

Dev: … literally the plot of office space but ok

story of my life

*2 months ago manager forces me (frontend dev to work on backend) and he agrees to do that only until new year*
*new year arrives frontend dev wants to go back to frontend*
*manager surprised pikachu face*

(Micro)Manager: Just a reminder you have a meeting at 4:30 today. (note that micromanager has nothing to do with this meeting)

Dev: Thanks, I think I can read my own calendar myself I think; I'm an adult.

Manager: ...

Dev: ...

Me: junior dev

Assignment: build a REST search service that also does (thing x)

Me: gosh I just can't figure out how to make (thing x) work! Nothing I try works and there are no online resources!

*goes to meeting with client*

Client: (thing x) is impossible in our application, so we are expecting (much more manageable thing)

Me: awesome! I think I can build that

Manager who can't code: what are you talking about, (thing x) is clearly better and it should be possible to do

Manager: *sends email outlining shifted requirements after the meeting, including (thing x)*

Dev manager: Php 8 is around the corner and i'd like to move the project to it
Dev: this would be a huge change I don't think you understand what you're asking...
Manager: Yes I understand, we'll plan 2-3weeks for the migration
Dev: the app is under symfony2.4, what you're asking is completly off the mark
Manager: look we'll plan it and we'll see don't be pessimist
Dev: ok whatever

I left the company, good luck to my fellow dev

Where I currently work (and have done for 10 years) we were recently recruiting for another dev, and one of the other devs and our line manager were running the interviews.

After 3 or 4 failed interviews they decided to test the questions on me... I got 3 out of 10 :(

My argument was (and still is) if I get stuck programming I can google, or you can teach me new stuff. And I can make a good cup of coffee

Manager: "Hi Almond, how is X going?"

Almond: "...I don't know, Bob is in charge of that."

Manager: "Ok. Do you know the status of Y at all?"

Almond: "Not sure, isn't that Bob's responsibility too?"

Manager: "Well, yeah, but I never seem to be able to get a good answer out of him. Find out on both fronts and let me know ASAP please"

...sure, I know how this goes. I'll stop all the dev work I'm doing, do your job for you, talk to the lazy bonehead that never bothers doing anything, report back that he's done sod all (or still "in a requirements gathering phase" as he puts it), be asked "why is he taking so long", have a bit more back and forth, then decide we'll just leave him be as actually trying to get him to do any work is going to be too much like hassle 😒

He said make me an apk of this website ... lol

Holy fuck I did it. I convinced my non tech manager not to do code QA after he brought the whole system down approving things without testing them and getting devs to make changes that caused bugs. Don’t get me wrong he threatened to fire me twice during the conversation but I dunno…I think I’m just about ready for my second dev job anyway ¯\_(ツ)_/¯.

Web Devs - How many projects do you typically work on at once? I am currently developing 24 websites at once, most of them custom (homepage). I just feel like that is absurd and my company is absolutely insane. Not to mention I'm the front line for client communication as well, pretty much the project manager AND developer. We're a huge company too, not a start up. Just feel like not having project managers for web dev industry is unprecedented except for freelance. 😡👎🏼

Manager: This dropdown is hard to use on mobile

Dev: I thought building this for mobile wasn’t in the scope?

Manager: I changed my mind. It’s a lot easier for me to test on mobile so just rework it so it works on mobile. But only for testing.

Dev: How about I make the dropdown a rotary dial instead?

Manager: Good idea!

Dev: …

The push back phrase my manager uses when I try to discuss a requirement which I think is incorrect:
"It was discussed and agreed upon at the beginning b/n PM and engineering"
To hell with that, if 10 people arrive at a stupid decision, its still a stupid decision

I just sit back until the project progresses much further and wait for another senior dev whom they can't ignore to bring up the same issue.
It is supremely frustrating 😤

Being me. Fresh out of UNI with a three year bachelor in CS, no work experience. Starts in a big tech company with a lot promise of exciting project etc. Starts in 3 projects with one lead dev and two senior devs.

First month begins. I start by setting up my local environment and read documentations, which is fairly irrelevant and old. One of the senior devs quits.

Second month begins. Lead dev quits as well and the other senior dev having sick leave for the rest of the month. Basically I'm on my own, but thankfully not responsible for the projects.

Third month begins. The other senior dev is still sick. Nobody to help. Now I'm forced to talk to customer with a lacking knowledge of projects. Nobody knows what is going on. Hopefully my other senior dev will come back.

Fourth month begins. My senior have quit as well. I've been assigned as responsible of all three projects now. FML.

Fifth month begins. I begged my manager for help. Got a junior dev to help me with one of the projects. He and I still have no clue what we should do.

What a shitty start to a career as a developer.

Anybody having a similar experience?

My recruitment story is a bit funny,
i had two interview, first one was to evaluate working style, behavior and ethics, where the interviewer and i spent almost 20 minutes discussing video games 😀.
second was technical, was interviewed by a lady dev manager and the team's technical lead "which i didn't know their roles at that time" went really good and at the end they asked:
Do you wanna ask us any questions?
Me: *leans back, with one arm on the chair arm and with a curious look and pointing one finger at both of them😕*
So what are you two?
them: *both had a shocked face and looked at each other for few seconds, manager chuckles😓😓* Well i am the team's dev manager and this guy is the team's technical lead, and in case you were wondering, we are not a couple.
technical lead: 😂😂😂
Me: 😨😨 no no that's not what i meant i swear.
Interview was over, i left the building thinking 😢😢 oh god, i totally blew it.
2 weeks later i get a phone call asking me to come and discuss contract terms 😂😂😂
sorry for the long story

Manager: Explain “Kooburrnehteez” to me.

Dev: Well when a mommy server and a daddy server love each other very much…

Dev: The requirement is not clear. This seems to be a general usecase which you are thinking we might need but we won't actually need it.

Manager: You have to do it. This is the requirement. No other option. Don't ask any questions.

...... One week later....

Manager: Why is the team not open to me?

Yesterday I had an interesting interaction

- I complain about not having tickets for something, as it makes it unclear who needs to do what
- manager tries to call out on me for “not giving precise infos”
- A frustrating argument starts, ends up with manager defending himself telling we need a meeting with [other team] to sync on infos that are not clear
- meeting starts, manager starts to make a buffoon about himself
- other dev out of nowhere tells that the manager is not giving the task to him for some reason
- other manager is speechless at our manager’s incompetence

Managers.😎

Manager: How's (insert dumbass task that they assigned literally 1 hour ago) going? 😊

Dev: We have JIRA for a reason, you'll see it will be moved to demo / review when it's ready.

Manager: ...

Dev: ...