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
Search - "urgency"
-
Manager: The thing you working on. We need this now! Like end of the week.
Me: Desirability is not do-ability.
Manager: く( ・◇・)ヾ?
Me: I am still in the middle of figuring out how to do things in the first place, so there are some technologies to research and some problems I yet need to solve. I am in no state to just write down my solution. I don't even have enough information to even estimate how long it is going to take. I am getting there. And yes, I can rush things, but need I remind you that you want solid data as a result that actually means something? As this is *why* this whole project was started. We have some old project doing the exact same thing, but whose output we don't trust. I wonder how that came to be. Additionally, this whole project was on hold for months until I took over. So I neither understand nor accept this sudden sense of urgency. And by the way, you recently added manpower to this project. And adding manpower almost always decreases the productivity in the beginning due to on-boarding and communication overhead. Last Monday, I didn't write a single line of code due to that. So no, this week will not do, as I am also on vacation starting on Thursday that was requested and was approved by you at the beginning of the year. See you in January.undefined results project it went better than expected actually communication is key urgent deadline11 -
In may this year, the new mass surveillance law in the Netherlands went into effect. Loads of people were against it with the arguments that everyone's privacy was not protected well enough, data gathered through dragnet surveillance might not be discarded quickly after the target data was filtered out and the dragnet surveillance wouldn't be that 'targeted'.
They were put into the 'paranoid' corner mostly and to assure enough support/votes, it was promised that:
- dragnet surveillance would be done as targeted as possible.
- target data would be filtered out soon and data of non-targets would be discarded automatically by systems designed for that (which would have to be out in place ASAP).
- data of non-targets would NOT be analyzed as that would be a major privacy breach.
- dragnet surveillance could only be done if enough proof would be delivered and if the urgency could justify the actions.
A month ago it was already revealed that there has been a relatively (in this context) high amount of cases where special measures (dragnet surveillance/non-target hacking to get to targets and so on) were used when/while there wasn't enough proof or the measures did not justify the urgency.
Privacy activists were anything but happy but this could be improved and the guarantees which were given to assure privacy of innocent people were in place according to the politicians... we'll see how this goes..
Today it was revealed that:
-there are no systems in place for automatic data discarding (data of innocent civilians) and there are hardly any protocols for how to handle not-needed or non-target data.
- in real life, the 'as targeted dragnet as possible' isn't really as targeted as possible. There aren't any/much checks in place to assure that the dragnets are aimed as targeted as possible.
- there isn't really any data filtering which filters out non-targers, mostly everything is analyzed.
Dear Dutch government and intelligence agency; not so kindly to fuck yourself.
Hardly any of the promised checks which made that this law could go through are actually in place (yet).
Fuck you.29 -
Once, I overheard a conversation between my former PM and a client during a phone call.
Client: I will send the final draft of the project by Thursday.
PM: That's great to hear!
Client: When can I expect the updates to review the changes after the draft is sent? I need to present it at a meeting this weekend.
PM: It should be ready by Friday without fail!
Client: Excellent! Thank you. I will be expecting it.
PM: Sure, goodbye.
(After the call, PM joined the team.)
PM: So, team, the client for Project-A will be sending us a new draft for review and updates. They are putting a lot of pressure on us and need it to be ready by Friday at the latest. We need to treat this with a sense of urgency.
(After hearing this, we felt compelled to respond.)
Me: There's no way they would expect us to deliver an unseen draft within a day. Both the backend and Figma team members were forced to work last weekend, on Saturday, because you mentioned that Project B was behind schedule and the client needed an update by Monday. We simply can't continue working like this.
Backend guy 2: I also worked last Sunday on Project B.
Me: We overheard you telling the client that they should expect an update by Friday. It seems like you're the one directly putting the team under pressure, even though we still have three ongoing projects with tight deadlines.
(The office fell into an uncomfortable silence.)
(PM left the office without saying a word.)
Later on, I heard that he contacted the client to reschedule the expected time of arrival (ETA) after receiving the draft.7 -
One of the bigger and more important IT projects this fall. Technical solution proposal needs to be ready by Thursday morning but is far from complete. Solution? The responsible person for this went on a two day mindfulness training. Apparently totally oblivious to the term "sense of urgency". Must be a citizen of procrastiNATION.3
-
So I have been working at the same company for five years, doing pretty much all the IT stuff. Sys admin, help desk, you name it. I've also developed a fair amount of in-house software for the company.
Today, I learned from a trusted source that they are actively interviewing people to replace me. I probably have a week, maybe two until I'm fired. To my knowledge I've done nothing to warrant this.
I've been looking around lately for a new job anyway, but without any sense of urgency. I have put in several applications with very few responses though.
I have 5 years experience doing this professionally and 15 total years of dev experience, but only a GED.
I'm not sure why I'm not getting any responses from my applications, but I'm pretty scared right now. I have a 5 month old baby, a wife and a teenager that all depend on me.
I don't know what to do...13 -
Advice to new coders? I got multiple, unrelated to each other.
1. Start with the FUCKING BASICS !! Invest some time with fundamentals, don't just directly jump on frameworks like React or Angular.
2. You and everyone else are always going to blame your technical skills if you're unable to land a job. But you have to realize that is not always the case. Your attitude and energy towards the interviewer plays a vital role too.
3. You're gonna have to take a hit to your salary expectations starting out. It's just the way this industry works.
4. Think of yourselves as a freelancer working for companies. Those who call themselves Employees get stagnant and dependent on their company pretty fast.
5. Your objective is either to learn or earn. If there is both, amazing job. If there is either it's good enough. If there is none, time to jump ship !!
6. HR is there to protect the company from you not the other way around. Be better at spotting crocodile tears.
7. Try to find a WFH job over a WFO job. If you have an urgency, then either works but keep applying to WFH jobs. It's the best thing.
8. Focus on what you're building instead of what you're building it with. Devs have a tendency to fight over what tech stack they should use instead of focussing on the larger picture.
9. You're gonna get overwhelmed at some point when you're gonna get terms thrown at you like XML, JSON, API, Figma, Git, SOAP, REST. Don't worry though you'll get there.
10. You should know how to google your solutions, like really. This is like 60% of the job.19 -
Why in the world IT work is so stressful?
I never been like that since I start developing code professionally, 8 years ago.
Since then, I had many health problems due stress, and some were really scaring (heart problem).
I'm trying to adapt to a healthier way of work, but I'm starting to doubt if that is possible.
Work in technology seems cruel and soulless sometimes. The constant pressure to learn new things all the time, to specialize in a lot of skills, simultaneously. The urgency nature of ALL tasks - even a simple form field slightly out of place seems to be an issue of life and death for clients.
Easy and quick communication made some people lost boundaries and respect. Many times I received calls and messages after midnight, about things like elements alignment.
And the worst is when clients blame you about their business problems. If they are not selling well this week, it's fault of the website you did ( which they are using for months now).
This actually happened to me today, first thing in the morning. After I slept just 3h, because I worked until late yesterday (oh yeah many more of these life/death updates).
What happens in this industry? Will this ever be different some day?6 -
I recently got into an interview where the interviewer made a huge mistake:
R: “what’s your resignation period?”
Me: “well, long story short I’m working on a contract so it’s actually short, just 1 month”
R: “mhhh could you make it 2 weeks somehow? We may really need to start sooner”
This is a sentence you shouldn’t say as a recruiter as now I know:
- You are desperate to find someone
- You have a time urgency
- You failed to find someone before
- You basically confirmed you want me in9 -
Okay, I'm interning at a government institution & boy let me just tell you... mmmh... A FUCKING MESS!
So I'm tasked with developing a HR system that the whole company should eventually use. I tell them I'm not familiar with the open source technologies they'd like me to use, they tell me no worries, you can develop a prototype with a tech stack that you're familiar with. Also, they tell me that they don't quite have the requirements from HR so what I can do for my prototype is just develop something "general" that works according to their "idea".
Being the good intern I am, I develop quite a good functioning prototype & present it to the team who then present it to the managers.
Finally we're all called in for a final meeting with the managers & HR, and guess what? The requirements for the system are different. Almost 90% of the features we built into the prototype need to change. Also, the system must use open source technologies. The managers promise to send a detailed requirements specification document, with sample data. I think this is a great idea as there's still a lot I don't understand. I expected this to happen, so I soon start to redesign afresh, this time trying as hard as possible to consider open source technologies within my plans.
But noooo... My team wants me to "finish" the system!
"Finish" what system, I ask? That was a prototype!
"Just tweak the functionality you built to meet the new requirements".
WTF!
We don't even have the actual requirements specification document, so I'll still be coding blindly. Also, the whole system needs to be re-built using open source technology!
Instead of pushing me to develop a system blindly, with no requirements, how about you push HR to tell you exactly what they need and how it should work first!?
I'm honestly exhausted with the false sense of urgency from my team!!8 -
So I am finally plunging into continuous integration. If I make one more deploy script mistake, I've lost enough time to merit having learned a better solution than bash scripting calling git and rhc and py files I wrote. I have failing tests that are failing because they weren't updated after the million and a half urgent changes in the past 2 months, so it's time to act like I am a TDD fanatic and write the tests correctly. So much work. All from me listening to the constant req changes, listening to the urgency, letting non-devs get under my skin if you will. I'm optimistic in all the wrong places - I think I can write that by end of day let's try it. I'm lazy in the wrong places - I think that I can write that test later, because all I changed was XYZ (which took all night but I said I'd get it as close as possible didn't I?). And I think these handful of bash scripts are good enough to make sure I run tests? But remember, I didn't write the tests or I didn't go back and update them. Or the tests that fail, I'm too lazy. And so much of the tests, I would need to use, idk selenium for, and damnit if I really don't want to dig for element IDs to wait for every time I need an AJAX call.
Okay wow, I really did rant here. And discredited myself a bit lol I need to ignore the wrong lazy and embrace the right lazy. Protect myself from myself and from contributors. It really is, up to me now, to rescue myself from my bad habits. Bad habits perpetuated by clients urgency every day, to change things, that should have been finalized in November if we wanted a stable flipping system in January. It feels like the blind (client) leading the blind (me, when I do dumb shit like rush features out the door half tested).
Anyway all this came out, because I have been reading about continuous integration and stumbled upon this quote. And thought someone might laugh at the anachronism like I did2 -
A newish client just sent a channel ticket marked as "urgent", which set off the alarm for everybody in the chain, with an amazon link to lingerie.
I seriously don't know how to react to this, since I really hope it was a mistake and not how he expects us at the next meeting lol
To send such a ticket you have to confirm your pin and confirm the urgency reason too by the way, so the only thing coming to my mind is, it was some sort of clipboard fail?3 -
When it is a Sunday and you reply to an email with tone of urgency and you are torn if you reply to the other emails which doesn't seem urgent but still has the same client list reading. To email or not to email.2
-
Windows 10 - You unreliable fucking piece of shit excuse for an OS!
The fucking thing smells urgency, I tell ya. And it fails when you need it the most! The worst part is, you can't even open the start menu without letting a whole bunch of background tasks and network fetches from eating your CPU cycles and system memory. I don't need your fucking suggestions for your lame ass apps. I don't want to give you feedback about the "Microsoft experience" (which I'm reconsidering), I don't want to be prompted every 5 seconds to reboot my PC for system updates to take effect. Stop fucking with my productivity!
FUUUUUCCCCCKKKKK!!!!!!!4 -
So, you have to build an app for your company. Once it is done you submit it for the test team who ignores it completely. Then they assume that the best time to test it is after the production deployment and then everything becomes a urgency.
The best part is the PM trying to make you feel guilty about leaving after 12+ hours of work because you didn't finish everything.1 -
I cannot remember having seen a more unethical and pushy user interface than the one of viagogo.
I'm a frustrated to close the entire tab within the first 10 seconds. It's a sad story on on how it tries to instill a sense of urgency to BOOK NOW!
100 people are looking RIGHT NOW at the YOUR offer! Stop thinking, act fast! BUY IT, YOU FOOL OR IT IS GONE!
Here, see all those other options are already sold out m( Oh look, that option over there? Just sold out in this very instant you lazy ass.
I have seen something similar on booking.com and airbnb, yet this egregious implementation truly gets my blood boiling and sets a new low.
I'll take my business elsewhere.
If you develop a web shop, treat your customers as actual adults. Let them breathe. Let them make an informed decision.
If you need to rush them, your business model is broken.
If my employer would ask me to develop something like that, I'd escalate hard. If that wouldn't suffice, I'd reject implementing that anti-feature and would look for a new job out of principle.rant 13337 devs are looking at this rant right now unethical behavior book now why are you slacking off upvote now pushy fraud ui2 -
Time to remove access to tfs for the BA. She started adding work for us for features that don't have their requirements gathered yet.
Another BA just sent us an email today about it with just a generic "we need this now" urgency with no description, no requirements, no real functionality defined. The other one had access to tfs because she was working with us on a project, and was helping out with requirements. But it seems she's forgotten that you can't just slap imaginary things in.4 -
Update about my boss:
I was early too judge. Maybe still early to form an opinion.
But dude seems pretty level headed. Yes, he is agressive. Yes, he has weird way of complicating things.
But I got to learn things from him. I earned his trust, just like I did in the past with other managers. He is confident about my performance now. He gave me space to ramp up and pushed me to limits.
But now, Floyd is settled. Maybe with time, I might get occasional unpleasant interactions, but those are part of every job.
However, we as a society decided to be in agile mode. Fix a problem and the solution gives rise to another one.
The business head of my pod is going crazy over the deliverables.
They were surviving for years with a product manager. Everything was driven by tech without any research.
And now when I am in, they want everything to be done yesterday.
We spent some decent amount of time on strategy and it turned out to be good. Now they are questioning that why ain't I delivering?!
It's been a week we finalised the strategy, let me get some space and time to structure and plan the execution.
Business heads are pretty nice and level headed people. Just that I don't understand the sense of urgency. I get it that my pod often has to deal with fire fighting given the nature of the business, but holy fuck! Stop pressurising to deliver everything together on a war foot.
They are like, we'll ask for more resources. But whose gonna tell them that 9 women cannot deliver a baby in 1 month.
I need time for discovery and research. Without that, don't expect impact.
As the only PM space, leading the entire vertical, how can I even focus on multiple initiatives?
I really miss my previous life of my first company. It's exactly an year when I left them and I changed two companies since then.
My learning and earnings sky rocketed, but WLB took a toll.
I miss the time when I could finish my work in an hour and did whatever the fuck I want while at work like browsing new topics to learn, exploring places, attending events, connecting with people, making social posts to learn, finance as a hobby, yada yada..
These days, I feel too burned out. Not that I am worried about job stability, because I trust my skills.
But more due to the fact that I have to constantly focus on work for the time I am in office. No free space or time to collect myself together, process things, and focus.
This leads me to thinking about work (read processing office discussions), at home too.
I cannot enjoy music. Feels like a load.
I no longer attend events or meet people after work. No more wasting time on the internet.
And most importantly, I am not bored anymore. I miss being bored. I miss living a boring, mediocre lifestyle.
I miss doing my side projects and polishing my portfolio site ten times a day, because I got nothing better to do.
I used to spend time learning right grammar and why American and English words are different and which to use where.
I miss spending time of Google Maps exploring borders and remote regions.
Weekends fly by. No hobby to pursue. No free time.
I miss the days when I had nothing to do and I was bored and I could do anything.
I used to be always happy. Because no responsibilities. I used to be always up for a meetup. I used to be available for a phone call.
Now it's nothing but work which is surely exciting and some foundational learning with good enough money, but I miss my time when I used to get bored because I had nothing to do.5 -
Today, I randomly remembered a guy who was doing an internship at my college's tech lab. From what I gathered (I wasn't really part of that group) all they had to do was familiarize themselves with one of the many systems available and... I suppose maintain it or improve it.
.... Poor guy spent the first 2 to 3 weeks just trying to get Ruby on Rails to work. The work he was doing was not (and would never be) critical so there was not much of a sense of urgency.
Someone should have told him to use a fresh VM. Guy was trying to get it to work in his private laptop running windows. A doomed endeavor.3 -
I recieve a mail from xyz@abc.in and i reply back to the mail and recieve address not found because domain abc.in couldn't be found. I am like wow, and mail was regarding urgency to postpone an interview.3
-
A certain person deserves nothing better than the signs of the tires of a full-speed heavy truck tatooed on her face (even though, I admit, it could be an improvement to the overall aesthetic). Especially when she wants to push the office (1 week before the vacations and with no real urgency, while there a tons of other jobs that are way more urgent) to modify one by one some field in the data of 5500 customers only because SHE (and only she) has a bonus, when everything could be solved with a fucking simple sql update and we only need a simple approval for that from the company of the project management software. All of this while she spends the time planning her own vacations in internet, or complaining about EVERYTHING, including the colour of the icons of her pdf reader (30 min complaints about a stupid icon). Responsible my ass.
-
I hate reactive management.
It's when your boss instills fake urgency every time a client asks for something close to impossible, or <x> competitor is doing something in a different way he deems the best.
Everything must be dropped, the sprint put on hold, fuck requirements, everybody has to do overtime, why are you not contributing?, why are you going home when you have to?, fuck do I care you have a 1 hour commute - this <y> thing has to be made by sunrise tomorrow or it's a showstopper.
And it's never a showstopper. 90% of the time the feature gets dropped one-two months down the line.1 -
So burnt out. Zomg. The typos... the poorly constructed tests... the clients daily changes and the urgency of it all... my test created an unecessary object that had me looking at all the wrong things. My own dumbness. From overwhelmed import haste
-
Pharmacy... Preorder-mail got stuck in spam due to weird receiver passphrases so they didn't actually order it (it was "banana" followed by an steadily incrementing number). You wouldn't believe their faces after they saw my mail.
It took the pharmacy exactly ONE HOUR to get that medicine after I went up getting them to know that they missed an order. They express ordered it after I guess I signaled the urgency...
That's one of the pretty great things in Germany. If you need medicine and if you're in a medium populated area, you could get it within hours, or at least in 1/2 day if they not express the order and you order over their website.
But this is attacked due to European trade deals. Online pharmacy shops (the ones without local pharmacies) simply trade in from cheaper areas in Europe and can sell much cheaper. Also because they aren't committed to cross finance local hospital medicine delivery which then let's the health insurance raise their prices.
But due to the law for the minimum wage and therefore steadily decreasing wages the online-only pharmacies get more and more of the market cap....
Such problems aren't easy to fix...3 -
Ah, it was good.
In last promotion I got rise of 70%+ (it was on performance basis).
I did not became senior dev but I still maintain more than 3 projects and help most of the people irrespective of stack.
Mostly this happened due to things I'm working on, currently I'm the one and only guy who is working on entire different things and I was always given with R&D tasks maybe it's new tool, library, stack, they always give me.(But because of this I never learnt specific thing completely which is too bad in my perspective)
Our company actually moved it's location to another city and I don't wanted to migrate so I just told them I can't but our CTO is too friendly so he said just do work from home and come when there is urgency, so I almost did work from home for more than 5 months.
Later we mutually decided that mainly I will be working in office but I will do work from home for one week in every month and as I was already not ready to move they pay my rent whenever I come.
So here it is, my little story :)1 -
So this month I had to do two major features which required unexpected refactors and I had to handle unexpected edge cases all over the place. Since I work in another timezone and time was of essence, I was kinda working around the clock to complete refactors as fast as possible because it was "important and critical". I have 7 other devs in my team but only half of the team are actually competent and even less are motivated to push through. Most of the team prefer to sit on low hanging fruit tasks and cant even get that fucking right.
So that resulted in me doing at least 100 hours of overtime this month. Best part all I got for pulling it off was a thank you slack message from teamlead and got assigned even more work: to lead a new initiative which seems to be even bigger clusterfuck...
So today I had a sitdown with my manager and I asked for 3 paid days off and told him that I did 50-60 hours of overtime. He okayed it as long as my teamlead was happy.
So I created a chat, adder manager and teamlead to it and explained my situation. That Im feeling burned out, I need 3 days off and combined with the weekend that should allow me to finally relax.
My fucking teamlead told me that these days are mine and he cant take them away from me. But then he started guilt tripping me that no one else will be working on the new initiative these days so we will have a very tight timeframe to deliver this (only until August).
Instead of having at least a drop of empathy that fucker tried to guilt trip me for taking days off for fucking unpaid overtime. What a motherfucker. Best part is Ive talked with manager and we actually have until end of August to deliver the new initiative, so fucker teamlead is gashlighting me with false sense of urgency.
I guess a hard lesson learnt here. Waiting for my fucking raise to be approved for the past 6 weeks (asked for a 43% bump which is on the way since I got very strong positive feedback).
So Im done. I proved myself, will get the salary of which I only dreamed about few months ago. Not putting any overtime anymore. If something is very urgent, borrow fucking decent devs from another team. Or replace half of our useless team with just one new decent dev. I bet our producticity would increase at least by 50%.
Its not my fuckint fault that 2-3 people are pulling the weight of 8 people team. Its not my responsibility to mentor retards while crunching under immense pressure just because current processes are dysfunctional. Fuck it. Hard lesson learned. If you want overtime, compensate with extra days off or pay. Putting my 7-8 hours in daily and Im not responding to your bullshit slack messages or emails after work. I dont give a fuck that you work in another timezone and my late responses might result in stuff getting done postponed by a few days or a week. Figure it out.2 -
They're so much to learn and always urgency to update your development skills. Is learning them even worth my life? Coz it is talking a huge part of it.1
-
Creating a new class to help implement a new feature. Start with my tests (going full TDD).
Feature gets more urgency given to it, write slightly less tests as deadline approaches (half TDD).
Out of time, any future tests are burnt (no TDD) as I frantically wrap up the class with not even the time to write down a plan, it's live coding at this point. -
Well, there was some urgency but no deadline as a it was a personal project. I wrote a job hunter that applied for everything I had any kind of shot at