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
-
This post is in memory of all the devRanters fallen in battle against management stress and impossible deadlines.
Let their memories remain, and their loss never be forgotten.7 -
I work in a company where I'm the only developer, with everyone being designers or marketing or sales. Typically like the scene from Silicon Valley.
Moto was to create a ticket selling website for their products, and make sure they worked as well. It was all fine, until deadlines were discussed. They wanted it done within 2 weeks, the entire backend dashboard, API and front end.
I told them it's almost impossible to do it, but they insisted on it. So, I made a minimal dashboard and told them, I haven't completed a few things, such as if you edit data in one place, it won't reflect in other tables. So, be careful while editing the data.
They nodded their head for everything, yesterday was site launch and 2 hours before that one bastard decided to changed the product names to something "catchy" but failed to change the same in other places.
I had used the name as foreign key, so querying other DBs became a fuck all issue, and eventually API stopped giving any response to front end calls.
I got extremely pissed, and shouted at that dude, for fucking everything up. He said, you're the tech guy and you should've taken all this into account.
I sat and hardcoded all the data into database again, made sure site is live. Once it was live, these guys call a company meeting and fire me saying I was incompetent in handling the stressful situation.
At that moment, I lost my shit and blasted each of those people. The designer started crying since her absurd designs(though great) couldn't be realised in CSS that too within 2 weeks time.
One of the worst experience for working for a company. I could've taken the website down, and told them to buzz off if they'd called, I couldn't get myself to do it, hence ranting here.
I seriously feel, all these tech noob HRs need to get a primer course on how to deal with problems of a programmer before they get to hire one, most of these guys don't know what we're trying to tell in itself.
I find devRant to be the only place where I can get someone to understand the issues that I face, hence ranted.
TL;DR: Coded ticket selling site in 2 weeks. 3 hours to launch, data entry dude fucks up. I clean all the mess, get the site online. Get fired as soon as that happens.
Live long and prosper. Peace.16 -
Suddenly it hits me.
It’s 01:20 here but i get it.
It’s ALL a budget thing.
No dedicated tester means less expenses.
No personal parkspot?
No expenses!
And no good staging or testing environment? Less expenses!
Meanwhile every developer can setup, work on, and maintain about 20 websites on their shitty local Windows machine, that doesn’t even have a proper SSD installed, and we are setting impossible deadlines to figure out who will sink and who will swim.
Ow, here is a SSD.. Figure out the installation yourself because we have no IT knowledge or budget for people that do.
You want a challenge? How about 40 other people that are distracting you all day long.
Meanwhile everybody has to improve their skills in js, react, html5, ccs3, angular, .net and razor so money can made faster.
It would be nice if you could build apps as well.
You had a question? Sorry, no time. Expect some feedback 14 days later.
You finished the site?
Great!
But here are 101 bugs to solve before next week.
All hail their crazy company!2 -
Impossible deadlines are ubiquitous in our company. Our CTO has the opinion that development is a lightning-fast process that doesn’t require testing and deployment because every developer is a God.
It is normal to hear something like ”just develop it tomorrow morning, it is easy” from him, but in reality, it is never that easy. -
Programmers nowadays have to...
… write 100%-covering unit tests;
… set up continuous integration, linters, hinters, style checkers, …;
… follow style guides for every language;
… meet impossible deadlines;
… meet impossible management/customer/end user expectations;
… read through terrible code others made;
… read through terrible documentation others made;
… make terrible documentation themselves;
… fight with the IDE;
… fight with the build tools;
… deal with unreproducible crash reports coming in from everywhere;
… debug code written at 2am (by themselves AND others);
…
…
…
… KNOW HOW TO PROGRAM.6 -
I might lose my job this week
I'm part of a team of 2 tech people
We were hired as programmers. But over these past 10 months we've done everything from helpdesk to fixing network infrastructure, i setup a backup server for the company, started properly managing the companies passwords,and a host of other things not in my contract.
But my boss is changing the deadline again and she refuses to listen to anyone's concerns, she doesn't understand the complexity of what she wants and since the best we've done so far can be considered at best a prototype in my opinion shes going to be disappointed
So at the next meeting me and my coworker are going to politely list our grivences point out all shes had us do at the same time and the impossible deadlines.
I've seen herpitch a fit for less so I'm fully prepared to be fired in rage in which case I'll compile the documentation and information on what we've done to email her.
But I'm pretty sure she won't find anything long term for the 40k salary shes expecting. Especially with how slow she is to do work herself. I was supposed to be on company health insurance since October 2020
In a way I'm kinda relieved at the potential of being fired.3 -
Hi devs, newbie here and i want to tell you my story for introduce myself.
I work for a company that develop web-app for managing taxes and sell it to locals cities.
We develop this web-app in Rails framewok and i litterally learned and work with this company from 2 years.
But i'm not happy at all. I was always hated and blamed for my work. My boss always take impossible deadlines and pretend ti finish the work in time, even if i had to overstay at work, even at home, even saturday. I'm not a really smart guy, so i often do dumb errors and I really suffer the nervous burnout and stress. Now i want to change work and i'm search far away from home but still in Italy, like Milan i.e. but i'm still confused. What i should do? I'm the problem?
PS. I want to thanks all of you that with your post get me laugh, inspired me and make me feel part or a great group.
Sorry for my base english6 -
This was not exactly the worst work culture because the employees, it was because the upper level of the organization chart on the IT department.
I'm not quite sure how to translate the exact positions of that chart, but lets say that there is a General Manager, a couple of Area Managers (Infrastructure, Development), some Area Supervisors (2 or 3, by each area), and the grunts (that were us). Anyway, anything on the "Manager" was the source of all the toxicity on the department.
First and foremost, there was a lack of training for almost any employee. We were expected to know everything since day-1. Yes, the new employees had a (very) brief explanation about the technologies/languages were used, but they were expected to perform as a senior employee almost since the moment they cross the door. And forget about having some KT (Knowledge Transfer) sessions, they were none existent and if they existed, were only to solve a very immediate issue (now imagine what happened when someone quit*).
The general culture that they have to always say "yes" to the client/customer to almost anything without consulting to the development teams if that what was being asked to do was doable, or even feasible. And forget about doing a proper documentation about that change/development, as "that was needed yesterday and it needs to be done to be implemented tomorrow" (you know what I mean). This contributes to the previous point, as we didn't have enough time to train someone new because we had this absurd deadlines.
And because they cannot/wanted to say "NO", there were days when they came with an amount of new requirements that needed to be done and it didn't matter that we had other things to do. And the worst was that, until a couple of years (more or less), there was almost impossible to gather the correct requirements from the client/user, as they (managers) "had already" that requirement, and as they "know better" what the user wants, it was their vision what was being described on the requirements, not the users'...
And all that caused that, in a common basis, didn't have enough time to do all this stuff (mainly because the User Support) causing that we needed to do overtime, which almost always went unpaid (because a very ambiguous clause of the contract, and that we were "non-union workers"**). And this is my favorite point of this list, because, almost any overtime went unpaid, so basically we were expected to be working for free after the end of the work day (lets say, after the 17:00). Leaving "early" was almost a sin for the managers, as they always expected that we give more time to work that the indicated on the contract, and if not, they could raise a report to HR because the ambiguous clause allowed them to do it (among other childish things that they do).
Finally, the jewel of the crown, is that they never, but never acknowledge that they made a mistake. Never. That was impossible! If something failed on the things/systems/applications that they had assigned*** it was always our fault.
- "A report for the Finance Department is giving wrong information? It's the DBA's fault**** because although he manages that report, he couldn't imagine that I have an undocumented service (that runs before the creation the report) crashed because I modified a hidden and undocumented temporal table and forgot to update that service."
But, well, at least that's on the past. And although those aren't all the things that made that workplace so toxic, for me those were the most prominent ones.
-
* Well, here we I live it's very common to don't say anything about leaving the company until the very last day. Yes, I know that there are people that leave their "2-days notice", but it's not common (IMHO, of course). And yes, there are some of us that give a 1 or 2-weeks notice, but still it's not a common practice.
** I don't know how to translate this... We have a concept called "trusted employee", which is mainly used to describe any administrative employee, and that commonly is expected to give the 110% of what the contract says (unpaid overtimes, extra stuff to do, etc) and sadly it's an accepted condition (for whatever reasons). I chose "non-union workers" because in comparison with an union worker, we have less protections (besides the legal ways) regarding what I've described before. Curiously, there are also "operative workers", that doesn't belong to an union, but they have (sometimes) better protections that the administrative ones.
*** Yes, they were in charge of several systems, because they didn't trust us to handle/maintain them. And I'm sure that they still don't trust in their developers.
**** One of the managers, and the DBA are the only ones that handle some stuff (specially the one that involves "money"). The thing that allows to use the DBA as scapegoat is that such manager have more privileges and permissions than the DBA, as he was the previous DBA2 -
It’s so fucking ridiculous that business people that knows jack shit about programming are the ones that promise features within a specific impossible deadlines to the customers4
-
My new favourite quote...
"I can't be the only one worried about the deadline"
By boss speakign ot my team who is expected to deliver 6-8 months worth of work in 5 weeks time...
Too bad he does not know he IS the only one worried, when you going to miss a deadline by that much when you never agreed to it in the first place, have not seen a single API and the scope is still actively changing and lets not forget we have no DevOps yet...
why the fuck would you worry...1 -
I'm very tired of these impossible deadlines, it feels like as soon as one project finish, we have to rush to finish the other.
I should take some holidays.2 -
I hate arbitrary deadlines.
Cocksuckers just pull them out of thin air and force me to give estimates about tasks that are impossible to give an estimate on.
(Spoiler: The tasks are the problem and need to be split and analyzed)2 -
>>"Oh we're more like family here and we like to have people join our family style instead of setting strict rules and punishing people " == "You'll stay late everyday and you won't be paid any extra hours and you'll be ass fucked with impossible deadlines unless you could fondle the managers balls"
True
>> -
Battling impossible project deadlines and maintaining a work life balance. Estimating projects properly.1
-
Need Advice + Rant
I am an Android Developer, pursuing an Internship, which i thought would be good for my career. But I am being assigned the task to build search feature for the App using Elastic Search. I intially was halpy to work on Search since it had to be Algolia. I am hating the work now because I am getting so stuck with Elastic and there have been other factors which also have decreased my productivity, but I am being quite inefficient. Now the deadlines are coming closer and if I dont give output I will be laid off. I am thinking about quitting myself because now I feel extremely demoralized and demotivated to work because we first decided to work on Algolia and it was all ready before we thought of shifting to heroku and now on AWS. What do the experienced once suggest? It's not that its impossible to do, now i just have to write queries in Java, again I am stuck and not really looking forward to since I was given the deadline today, for 2 days later.
The only issue is, I may have to return the new phone (OnePlus 3T) which I bought planning to later return the money to someone through my stipend.23 -
Alright, buckle up, fellow developer, because we're about to embark on a thrilling journey through the world of code and creativity!
Listen up, you amazing code wizard, you're not just a developer. No, you're a digital architect, a creator of worlds in the virtual realm. You have the power to turn lines of code into living, breathing entities that can change lives and reshape industries.
In a world where everyone is a consumer, you are a producer. You build the bridges that connect our digital dreams to reality. You are a pioneer, an explorer in the vast wilderness of algorithms and frameworks. Your mind is the canvas, and code is your brushstroke.
Sure, there are challenges—bugs that refuse to be squashed, deadlines that seem impossible, and technology that evolves at warp speed. But guess what? You're not just a problem solver; you're a problem annihilator. You tackle those bugs with ferocity, you meet those deadlines with gusto, and you master that evolving technology like a maestro conducting a symphony.
You live for the 'Aha!' moments—the joy of cracking a complex problem, the thrill of seeing your creation come to life, the satisfaction of making a difference. You're a digital superhero, swooping in to save the day one line of code at a time.
And when things get tough—and they will—you dig deep. You summon that relentless determination that got you into coding in the first place. You remember why you started this journey—to innovate, to leave your mark, to change the world.
So, rise and shine, you coding genius! Embrace the challenges, learn from the failures, and celebrate the victories. You are a force to be reckoned with, a beacon of inspiration in a world that needs your brilliance.
Keep coding, keep creating, and keep being the rockstar developer that you are. The world eagerly awaits the magic you're about to unleash! Go and conquer the code-scape! 🚀💻5 -
never before have I been happy to be asked to work overtime, but for once, fuck yeah...
Bit of back story, I am tech lead on a massive project that has been run like a complete shit show, the PM who also happens to be the brains behind the project seems to think we are miracle workers and for the first 9/10 months of the project would make significant, like delete a weeks worth of code and start over changes, 3-5 times per week. There are features for the v1 release that have been built in excess of 5 times. I have been saying since October that even without all his constant changes, we will NOT make the deadline, and naturally as is part of my job I argued against every unnecessary feature he tried to implement, eventually he pulled me into a meeting to tell me how much he values my opinion, I need to stop arguing with him and he does not want to work with yes men (I have a rant about that convo already).
I believe our CEO finally started smelling a rat as he insisted on joining our daily stand-ups, during which said PM scripted some lovely stories to disguise the fuckup we are in, and since has assigned another PM to take over and do proper project management and risk analysis.
That is where the email comes in, a lot of the work assigned to me will miss the deadline by a month, honestly I am impressed that it is by so little and so few people will not be missing it, but anyway, he probably spun a few stories there too.
So I spent part of the work compiling the most perfect surgical response as not not actively throw him under the bu, but create a quite a few questions that they hopefully as, as himself and the CEO where cc'd into the mail.
And the jist is, the deadline itself was still impossible and 8 of the 10 tasks assigned to be have ZERO back-end whatsoever, and those tasks are about 80/90% integration to said non-existent back-end, some of those services and data structures have not even been planned yet and we are a week past the deadline and 3 weeks from the just as useless extension. -
So our sales rep got this email from some random dude yesterday (jan 12) saying he wants a simple webpage with a video background and some shit and that it's upmost important that it's done by jan 21.
Ignoring the fact that we are busy af, i thought well yeah it's doable. A simple onepager with some nice elements and some shit, ez pz.
In the email he also sent a link to a website simmilar to what he wants (as an example i presume) and it turned out to be a fully functional blog, a medium sized webshop (by the looks of it) and a whole lot of other stuff.
He didn't state a budget but seeing his demands I'd say his budget isn't much more than a couple of hundred €.2 -
3 weeks till deadline... Gonna be hard. Get in find emails from PM, boss and his boss, deadline moved deadline today... Ffs.1
-
whining
So I'm sitting here, working my ass off developing something far above my current skills.
On the opposite side of the table sits relatively new guy, working as a part of support "department". Relatively new means that he's with the company for around 1 month.
The guy started speaking to me. I took off my headphones and listened, while still reading code. He told me about how he'll have to carry out the recruitment process for the support department today. And that he was told to present himself as a leader of the department, blah blah blah.
To be honest, I stopped listening at that moment. I got really pissed. And it's not because of the absolute lack of the professionalism of the company (srsly, make a new guy do recruitment work?). It's because I asked boss to get someone to help me half a year ago. He did employ around 3 new support people (4th today). But no one for me.
And he has the balls to tell me that I NEED to work harder to make it for deadline that he imposed. That he won't employ anyone new for me because new people could stole his "idea". Because MAYBE in a month one guy, a junior like me, will come back (he's on a break to finish his master thesis).
Product I'm working on is probably the main reason other companies are even buying the system he's reselling. As a student I'm working only half-time, so those deadlines are almost impossible.
I wonder how he'll manage if I'll get accepted for the work I'm currently applying.4 -
Today I read a great article on mutation tests, how to use and why they are important. It looks like a great thing, but...
I have never wrote any unit test in any of my jobs. Nobody in my workplace does that. And now it seems like 100% test coverage is not enough (I remind you, that I have 0%), they all should mutate to check if the quality of unit tests is high.
It seems that I'm left behind. I played with tests in my free time, but it seems the more you write them, the better you get at it, so I should be writing them in my job, where I code most of my time. Not only that, of course, I would also want to ensure that what I'm working on is bug-free.
Still, it will be impossible to introduce unit tests to my project, because they are novelty to the whole team and our deadlines are tight. The other thing is, we are supposed to write minimum viable product, as it is a demo for a client, and every line of code matters. Some might say that we are delusional that after we finish demo we will make things the right way.
Did any one of you have a situation like this? How did you change your boss and team's mind?8 -
It seems like there is a whole another grade of fear — Basilisk grade. It’s impossible to experience it and walk away without serious consequences.
Imagine: I’m barely 20. It’s my first real, official, high-paying job. I’m already a team lead. A big Russian non-govt company with a blue logo. Huge new office in Moscow.
My “childhood” is officially over — I’m not playing around anymore. I’m an adult in every sense of the word.
Several weeks go by. Maybe even a month. Just a regular day at the office. I’m waiting for the coffee machine to heat up, and suddenly, it hits me. I’m here, at the office. Moscow, a city of 10 million people, is beautiful in the summer, yet I can’t just leave the office and go for a walk whenever I want to. When the day is over, it’s already evening, and I barely have time for myself. There are other people around me, with way higher positions, but their schedule is just the same as mine: nine-to-six. My adult life just started. I have forty years of this ahead of me. No matter the company, no matter the position: unless I’m the CEO, I’m doomed to get to work in the morning and go back home in the evening. And then I retire, old and not that beautiful anymore. And then that’s it.
I was never the same after that day. People are plotting my betrayal behind my back. They all act as one. Just out of my frame of view, their heads are turned to me, and they all look at me with the same devilish grin. There are no people — it’s all one huge shoggoth that lives under the office floor, and my colleagues are its ugly tentacles wrapped in human skin. I start missing deadlines. I become paranoid. Next thing I know, I’m at the psychiatrist’s office, being prescribed aripiprazol — a strong antipsychotic that is designed to literally make you slower. Anxiety worsens. I develop restless legs syndrome. I lose my ability to sleep. My intelligence is slipping away. I’m fired.
I have the return to Saint-Petersburg, cariprazine prescription that felt like lobotomy with extra steps, losing my ability to read, delirious manic episodes ahead of me.
It is only now that I kinda-sorta tuned my medication scheme in by going through countless psychiatrists of all sorts. But I sure as hell work at a place where I can do whatever I want if I meet deadlines.3 -
Waterfall.
I string dislike the waterfall methodology and much prefer agile or scrum. And it's incredibly difficult that upper management only understands waterfall while claiming to know agile.
Meanwhile they want things completed by deadlines that are only possible with an agile approach. So you have a mishmash of upper management running waterfall with impossible deadlines and developers trying to meet those deadlines running in agile.
Anyone else have this problem? -
My Office Sucks. They give me impossible deadlines, and never properly test my code. And when it breaks in the production, they blame me.5
-
So my laptop screen started flickering to black when movement occures on screen, making it look like a stroboscope and giving me a sweet migraine.
Impossible to code, write, browse or get anything done. Good bye finishing deadlines on time.
Don't know what's wrong, hardware or software, I have no freaking idea. But I'm tempted to take this as a oppertunity to blame windows10 whipe my computer clean and running some Linux OS instead.6 -
Any top tips for recruiting or things you look for in an ad?
Our company has just advertised 4 roles (one was a junior PHP/JS dev role) and we got 90 applications. Only one was for the dev role, and we decided not to pursue it.
We're keen not to go the recruiter route, they cost a ton and that means less pay for the dev in the end. Plus, you've only got to look at this week's rants to see how they work!
Every day without help feels like an eternity of ever shortening impossible client deadlines for me. 😩😭 (I'm the main dev on a team of 3 including our PM)5 -
"All Tech Projects Run Over Budget"
https://medium.com/@team_96861/...
I was on a nice streak of being calm for a while and then this article just dropped today. Fuck management and fuck whichever dumbass wrote this piece of shit.
Is anyone else pissed off at this? It makes it sound like software engineers are slow and never on time, and the main reason for a project's failure is the inability of programmers to meet deadlines. I find this a little sus, especially as it's written by someone in a management position.
I would argue that projects fail because:
1. Management takes the very feasible timeline given to them and throws it out the window, opting to impose impossible deadlines instead, because FUCK your employees right?
2. Clients have requirements that can't be met (I agree w/ this from the article, but not the part about developers not accounting for issues--I always do this and everyone I know does this)
3. Technical Debt arising from when management tells the software engineers to *just do it this way because it's cheaper*
The calculator they made is nice but it's also quoting estimates that I and everyone I've spoken to agree with, so this is clearly not a software engineer problem, it's a fucking management problem. "Budget" = accounting's job.
/rant
That being said, the "take their quote and triple it" part had me dead...1 -
Friday morning's meeting:
CTO: Ok guys, deadline is next Friday so today we close the last big issues and next week no more new features, only bug fixing.
Monday morning's meeting:
Business: So here is the new mock-up for the search feature (basically they changed the whole behavior).
😐1 -
Everyone here rants about clients, and as far as I understand frustration, I understand client's side too.
For 2 years I have developed a tool for our company, my manager was responsible for outcome and was directly accountable to company's management, which made him a client for our product. Of course requirements changed many times, he pressured us much, but he is nice guy and gave us knowledge why we had to change things again. We had meetings with him, HRs, PMs and others to gain requirements for features to implement and that made me better understand client's point of view.
My point is that when you work for external companies, you only see changing requirements, pressure, deadlines, etc, but don't think that your work is just a part of process - your client is responsible for your delivery, wants to make good impression on superiors or company needs some feature ASAP. He does not have to know tech stuff, he wants outcome to be good and to be fast and cheap - that is business.
And yes - we had to tell people that X is impossible many times, had to tell Y people how things work over and over. It may seem easier when it is your own company, but note that every single employee knew that you developed that tool and you have answers for his questions.
Top Tags
Weekly Rant
View