Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Classes are classist.
Objects are objectifying.
Race conditions are racist.
Foreign keys are xenophobic.
Functions are ableist.
Thin clients are weightist.
Bitmasks perpetuate heteronormativity.
Code beautifiers promote unrealistic beauty expectations.
Test-driven development is victim blaming.
Forced commit pushes are rape.
Motherboards perpetuate gender roles.
And don't get me started on white space.9 -
string excuses[]={
"it's not a bug it's a feature",
"it worked on my machine",
"i tested it and it worked",
"its production ready",
"your browser must be caching the old content",
"that error means it was successful",
"the client fucked it up",
"the systems crashed and the code got lost" ,
"this code wont go into the final version",
"It's a compiler issue",
"it's only a minor issue",
"this will take two weeks max",
"my code is flawless must be someone else's mistake",
"it worked a minute ago",
"that was not in the original specification",
"i will fix this",
"I was told to stop working on that when something important came up",
"You must have the wrong version",
"that's way beyond my pay grade",
"that's just an unlucky coincidence",
"i saw the new guy screw around with the systems",
"our servers must've been hacked",
"i wasn't given enough time",
"its the designers fault",
"it probably won't happen again",
"your expectations were unrealistic",
"everything's great on my end",
"that's not my code",
"it's a hardware problem",
"it's a firewall issue",
"it's a character encoding issue",
"a third party API isn't responding",
"that was only supposed to be a placeholder",
"The third party documentation is wrong",
"that was just a temporary fix.",
"We outsourced that months ago.","
"that value is only wrong half of the time.",
"the person responsible for that does not work here anymore",
"That was literally a one in a million error",
"our servers couldn't handle the traffic the app was receiving",
"your machines processors must be too slow",
"your pc is too outdated",
"that is a known issue with the programming language",
"it would take too much time and resources to rebuild from scratch",
"this is historically grown",
"users will hardly notice that",
"i will fix it" };11 -
Me : We have 3 guys , 850 hours of content to develop, and you want this by mid Feb...
Account Manager : Yes
Me: ... (Doing math in head)..
Account Manager : This has to happen , what do we need to MAKE THIS HAPPEN..
Me: A time machine....
- awkward silence -10 -
Surprise surprise, that unrealistic deadline you set even when the engineering team told you that it wasn't going to work has backfired! Maybe you wouldn't be so stressed if you learnt to listen? It's a pretty basic skill, or at least I thought so.
Oh and when you say "we have two options, stay late or work weekends" you have a critical bug in your conditional. Your missing option 3, go the fuck home. Time to enjoy my weekend with friends and family.4 -
I need to stop sending my third personality to interviews. I'm just creating unrealistic expectations.3
-
So I am at the client's location for onsite consultation of their projects.
The HoD asked me to create an application to accept feedbacks from multiple points urgently. Although I was there just for consulting, I thought why not, I am anyway getting bored here.
So after explaining the functionality, she asked me, when can she accept a working app. I told her that it would depend upon a lot of factors, so give me till evening to figure it out.
When she insisted I told her, that it can take at least a month with all the APIs, logins, UI, QA etc. She was surprised and told me that she expected it in 4 days since the requirements can be fit into a single page of her notebook. (That's how she measures project duration).
I told her it's impossible, given that I am the only one working on it. So she told me that her team can do it in two days. I probably have more experience than her entire team combined, but still I thought they might know some simple magic or faster way, that I might not, so I asked her to discuss with the team and then decide.
After explaining the requirements, when she mentioned that it should be done in 2 days, everyone was kinda frozen. One of them said that it's going to take at least 4 months.
I couldn't hide my smirk 😉2 -
After refusing to work over 40 hours a week and refusing to work last Sunday, today I was fired. It's been the 2nd time in my life and it's been the same deal: totally unrealistic timelines and totally unrealistic work expectations.
No big loss. Fuck that place.9 -
I get really defiant when i repeatedly get micromanaged with bullshit instructions, such as asking me to have my just started c++ library poc which also involves a lot of learning and will earliest be usable in a few months, "ready for our customer devs" in 2 weeks from now.
just no, you fucking retard.
also, the lib alone wouldn't make any sense, since the code parts working with it don't yet exist at all.
and then getting instructed to ask customers if they can provide you with c++ code that solves the task for them in their own software, which of course will somehow magically fit in my existing codebase. even if it existed (which it fortunately doesn't because they do everything in C#), i don't think i'm going to be faster trying to somehow solder in their code into my library, of which i'm still brainstorming about the general architecture.
if you have so fucking unrealistic expectations, maybe stop sniffing glue all day and don't make this my fucking problem.3 -
I hate white boarding sessions. They feel unnatural to me. I simply don't work well when put on the spot and I have 3 ogres staring at me waiting for me to fuck up in front of them. Fight or flight engages, the adrenaline rush, my mind freezes. Suddenly it's like I forget how to code at all and I'm expected to solve a problem at once, correctly the right time, or I'm out.
I can't work like that. I need time to process a problem on my own, with my coffee in my one hand and a pencil and scratch paper in the other, not with some demanding employer standing over my shoulder the whole time scrutinizing my every key stroke. I get things wrong the first time sometimes, and more often than not have to google things I can't recall spontaneously. But I always figure it out, test it, make sure it's right before putting it into use.
I've been through several "probationary" periods when first starting a job. They just tell you, they're giving you a month to see if you can handle the job. If not, sayonara. I don't see what's so hard about evaluating candidates in a real world scenario.
So many employers have totally unrealistic expectations.2 -
2 leetcode hard questions in 60 mins. That's what I faced in few company interviews. Trust me, if that's the expectation you're having from candidate, you're looking for a leetcode monkey but not a software engineer!
To the interviewers who have such unrealistic expectations, please change your mindset. It's literally impossible to come up with optimal solutions to 2 leetcode hards in 60 mins if I haven't solved those problems before! It just becomes a memorization game not a problem solving round!!!
:)2 -
One shitty thing about working in a Japanese company is that they make you write personal goals/targets (目標). These goals they expect you to achieve don't actually relate to your work most of the time and it's not about personal growth, but more about what you did to improve the company.
Another thing is their expectations that you can achieve all this within a year on top of your work is kind of unrealistic. Plus even if you achieve such goals, it does not equate to good performance review and/or salary increases.8 -
I dont work weekends ever. And I dont bring my work home with me, once I finish for the day, Im finished. Even if there is a deadline looming or something is due for a weekend release. I will only work when Im in the office. And I wont work extra unpaid hours. All that does is create unrealistic expectations from your employer and clients. I did it once and learned that there was no point and I could have just gone home and it would have been fine. Im never doing it again.3
-
Actually I feel I am prety lucky about the relationship between my yamily and me being a dev. My dad is a developer as well (in fact, he was the one who taught me most of what I know today; not as in general coding, but good and bad programming practices, tips what to do next ...) and my mom just started learning Python.
So they know prety well what it means to be a dev and have quite realistic image of what to expect.
To be fair, I am still the one who usualy fixes broken printers and replugs unplugged ethernet cables. but that is because I enjoy doing that. I take it as a challenge for myself to figure out what/how/when went something wrong. Most of the times I try to figure that even without touching the broken things.
Anyway, getting off topic.
Alltogether I don't think that they have too unrealistic expectations, but if I had to chose one, it'd be my learning capabilities. I can't learn complete java in 2 days ...1 -
Yup, sure our team of three devs will build you a fully functioning e-commerce site from scratch that grabs data from several APIs and uploads it to several more.
You need it in two weeks? No problem.
Me: Wait...what the...?!
One week in and I only have access to test one of the four necessary APIs as the client hasn't signed the necessary paperwork with other providers.7 -
-Management puts unrealistic deadline as usual-
_Tries his best but fails to deliver on time_
*Puts a clearly visible bug in code*
~Tester finds it and creates a issue~
*Solves the issue, wraps up the remaining things and closes the issue*
**Wakes up from dream, cuz he is the tester as well** -
At a previous job, boss & owner of company would waste hours of my time to show me, at his own desk, every small detail of some random feature he had fallen in love with on some random webpage he found, while saying "I don't want to disrupt your plans or anything, this is just something to keep in the back of your minds, as this would be a really nice thing to have, even tho none of the clients have asked for this and I have asked no one else for a second opinion, and I will most likely ask you to remove this feature in the future because I will finally have realized it wasn't that good an idea anyway."
Ok dipshit, what the fuck are we supposed to do with this information? Every week from this moment on you will ask whether we have found the time to implement this feature, even though you are fully aware that our schedule has no room for random, unplanned features and that we are already not able to meet the unreasonable deadline you pulled out of your ass two weeks into a development process that would end up taking 8+ months.
We are already overworked, we already work hours upon hours of unpaid overtime, and yet you still think it reasonable to pull us away from our work every other fucking day to talk about random extra features you want added, but don't want added to the roadmap because you want no delays... Fuck you, fuck your toxic attitude, fuck your meetings where you spend half an hour complaining about features we are still in the process of developing the backend functionality for (on test servers) not having the right font colour for the text, and fuck your legacy desktop software originally written in COBOL that you now want moved to "the cloud".
I would rather be unemployed and live as a hobo on the streets with a "will code for food" sign than work for you ever again. -
"Can we do X?"
Yes, we can do almost anything you want.
"Can we have it ready by last month?"
No.
"What about 2 weeks ago?"
Not feasible.
"Yesterday?"
Sorry I don't think we can.
For real though, how do you deal with unrealistic delivery expectations? I'm not sure if I'm supposed to keep saying no to everything, or if they keep asking in hopes that maybe this time it'll be ok.2 -
So today is my last day working in [censored] company. Even though today is the last day and they have my replacement, they still expect me to complete the project 'NOW'. So I decided to make it quick the way it supposedly was. He wanted me to do tonnes of adjustments.
To prevent me from getting more stressed over satisfying my boss' requirements or meeting my boss' expectations, I made the app return the screenshot of the design. So I screenshot the design and render it to the app. So far that's the fastest route I can think of.
I really do not want to do this. But he left me no choice due to his impatient and adamant behaviour. That's why I decided to haste the project by returning the screenshot. (To be honest, this is unprofessional and dishonest, but he left me no other choice to violate my principles).
We argued about the negotiation with regard of the timeline for the deliverance of the project, I proposed 6 months countless times. He constantly denied that I did not negotiate with him. Unfortunately, the 'negotiation' defined by his action is merely a projection of an illusion of negotiating, but whatever is discussed on the table will deliberately fall into his idea and unrealistic high expectations.
Working in this company caused me damages beyond repair. My 4 weeks in this company were my worst nightmare. I don't get enough sleep due to the constant stress from the employer to complete the project in the 'immediately' phase. I brought these issues afore the table for the discussion. He simply deny it and blame it all on me, saying 'that it was my own negligence, to the company. I do not subscribe to his methodology of handling stress, by working more and contributing more to the company as passionate as possible. I am passionate about what I do and my position, what I do not passionate about is being unreasonable, ignorant, delusional and inhumane.
I learnt my lesson now. I vow to myself that In the future if I have the opportunity to be a team leader, my former employer is not and never be someone who can be my role model as a leader.
Refer: https://devrant.com/rants/5379920/...
4 -
A whole bunch of new features were added mid-sprint without ever consulting any of the development team. They dogpiled on devs from other projects who had no prior experience with the code base, so naturally I lose traction because I'm tied up answering questions and explaining things.
This sprint I'm not getting any feature work done as I'm stuck fixing bugs and awful half-ass implementations (by well meaning devs that were thrown at unrealistic expectations).
Concerned at the burn down rate, next week they're planning on dogpiling on more guys to play catch up.
I'm so sad -
More and more declining respect for programmers, unrealistic expectations from managers, and worse and worse code as everyone becomes dependent on taking modern hardware for granted.
-
My problem with “The DevOps Handbook” is the same problem I have with Star Trek: The Next Generation: it gave me seriously unrealistic expectations that senior leaders can be convinced to abandon stupid ideas.
Or maybe it’s just that in my mid-to-late thirties my tolerance for manglement is as low as it’s ever been, and I’ve grown out of that idealistic kiss-ass stage of my career.
…🤔 -
I've been reticent to chime in on this weeks group rant, feels too personal...but it is what is is.
Most emotional was losing a dev to cancer, and an analyst to an allergy, and an engineer to an accident...ugh.
Most intense was probably losing servers and hard drives without recovery, not being able to get databases back online because they went down so bad, websites being down, not meeting some quarterly goal, shit not building, email campaigns that go sideways...fuck...anything involving reactionary leadership...unrealistic expectations.
But all that shit, while seemingly important or "stressful", pales in comparison to someone you fought with in the trenches not being there anymore.
restore -if friends -
Smart contact lenses and the appropriate software. It would be the ultimate AR experience. I have no idea how to produce them, as they would need to be super high resolution, lag free, completely wirelessly powered and connected, safe to use and to wear and useable 24/7.
My current concept is a ultrabook sized block that can be taken around in a backpack.
Oh and wireless handoff ...
meaning everything I grab and throw in your general direction becomes available to you, kind off like they do it in Avatar. This should also work with PCs, tablet and everything else.
Speaking of grabbing you would also need some kind of minority report glove so every bit of hand movement can be tracked precisely. But probably a bit more elegant meaning only small stickers on the back of your hand.
Did I mention that sharing stuff should enable working together on the same object in real-time?
Also this system should integrate seamlessly with a smart environment, meaning looking at the light, opening its context menu and changing its brightness or colour should be no effort at all.
And of course all of it should be open source, highly scalable and either hosted on public infrastructure (funded by taxes or smt) or by each individual for himself to protect his or her privacy.
So who is with me?2 -
So I joined this digital agency where they are working on this ad-tech product and right from day one, I was given a task to implement a new feature on the product. No knowledge transfer. No onboarding process. So, I had given estimation about the task and apparently it took longer than expected. But what were they expecting. Anyways, my manager asked me to have a KT with the only senior guy that has been working there for last couple of years. And man, since the KT started, it's been hell for me. The guy is such an asshole and won't even give me a basic walkthrough of the system. He only took one call and that ended within 30 minutes. On top of that he went ahead and told the product manager that I am not keeping up and am not ready. And my product manager apparently wants me to take his place within a month. It's been only two months since I joined. I have already pushed two major features, tried to understand the system architecture, codebase and everything on my own. On top of that, I got yelled at by that senior dev in a meeting about a PR. I was quite confident guy when I joined and now I am anxious everyday at work and i am scared that they'll let me go because I won't be able to meet their unrealistic expectations. I also can't stand this senior dev and he can't stand me which makes me really demotivated to work. I have anxiety issues and now I am thinking if I stay, I am gonna mess up big time and they'll fire me or worse. I might break something in production because I didn't have proper onboarding.2
-
Oh you have plenty of excuses why I shouldn't have any reasons (which YOU call excuses) but don't see that yourself -- you fucking hypocrite!
There is NO EXCUSE for your bullshit lack of facing reality and setting unrealistic expectations that no one can possibly follow! Yet you continue to have an excuse for every legitimate reason (proven by facts by the way) that I have when everything doesn't turn out the way you expected.
Well GUESS WHAT motherfucker?? YEP, YOUR FUCKING EXPECTATIONS ARE THE PROBLEM not my actions. Just fucking grow up you piece of shit micromanager who has to have his nose in everyone's face all the time! Fuck that shit! -
So I went to a car repair center and asked if they could fix my bike. They said they could but they won't. This is outrageous, obviously a bike is less complicated than a car and they can actually fix it, they just won't because it's "not their job". Unbelievable!
//This didn't really happen of course
//people don't think this is acceptable, but if I won't fix their laptop they are surprised and act the same way. I study ICT (embedded software engineering and cyber security, but they don't understand that so ICT it is) so I HAVE to fix their laptop....
//Non-techies should really learn that just because we can do something, we don't have to do what they ask of us11 -
Programming an app for a friend = inevitable feature creep, unrealistic expectations and insane time frames. How do you guys deal with developing for non devs? It's like talking to a brick wall 😔7
-
Just after feature launch, major bug on production and now I am getting yelled at by my lead as the issue happens to be with the PR i was responsible for reviewing yesterday. Somehow a logic error got past my review. But considering how large the project is it wasn't possible for me to test out every possible scenario myself. They should have had QA handle that. Also, that was my first code review. I can't understand why my boss has such unrealistic expectations. Bugs are expected at this stage. I feel like he just puts too much pressure on me for no other ther reason other than to just trigger my imposter syndrome. That way, I feel like a bad developer even though I am working my ass off. And he gets to avoid giving me a raise. Cant believe I rejected multiple offers to stay at this company. I don't even know why am I still working for this company anymore.4
-
Been applying for jobs lately and despite the years of experience and using the latest toys I’ve been finding it harder than ever to even get a positive response to my CV. One thing I’ve been noticing is that companies seem to now not care so much about frontend skills and more about complex algorithms when the role is ui focused, or to have a demand for dev ops experience. Are we really getting back to the days of thinking that jack of all trades can be experts in everything?3
-
How to deal with having to work on a very boring task?
I work as android dev in a company where there are around 40 of android devs in total. When I was working on frontend architecture and UI related tasks everything was perfect and I loved my job.
But now for the next couple months all of us have to work on migrating all of our db layer models and business logic related to them to a new built in house ORM library and its a total trainwreck.
Everyone is confused, the task is very boring and obscure and deadline is around 2 months. Just to clarify: one guy did 50% of migration and it took him couple years. Now they are throwing roughly 20 devs at the problem thinking they can do this in 1-2 months.
One week already passed and TBH I havent even started working on this, I just picked up a task and now Im trying to wrap my head around this. Its so boring and obscure and expectations are so unrealistic that I want to kill myself.. Thinking of just taking my 2 weeks vacation to escape this shit or even quitting my job if this goes on longer than a month or two.3 -
Repeating story, here, isnt it? A dev dislikes a PM, a QA, a Boss. They don't understand, or have unrealistic expectations or say something "stupid"...
But it requires guts to work with other people, cause often the facts we devs have to tell isn't popular. But to lower unrealistic expectations with the bosses, isn't that part of being pro?
Wish *I* had guts...
Top Tags
Weekly Rant
View