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 - "resourcing"
-
I’m getting fucking tired of having this conversation:
Company “we need x”
Me “ok. In order to deliver x I need y”
Company “we can’t do that”
Me “ok. Then can I have y”
Company “nah ah”
Me “what about Q?”
Company “nope”
Me “okay. Well until you decide to provide me with the resourcing needed, this is getting deprioritized”
Company “wait this needs to be top of mind”
Me “okay. Provide me with y, and I’ll deprioritize other work”
Company “wait we also need that other work”
Me “you’re only getting one. Pick which one you want first”
Company “we’ll get back to you”
Me (muttering) “no you won’t”
Company “what?”
Me “what?”10 -
Got hired for my UI knowledge, then I get stuck doing backend work since I started, while the mountain of UI work just continues to grow and they refuse to let me work on it instead of hiring more backend help. Cool cool cool cool.12
-
Accepting a 3 year old scratched and beaten PowerBook as my "new" dev machine. Especially when my personal, 4 year old one is as powerful but with double the disk space (SSD) and RAM... Then of course the new guys just joining actually do get new out of the box devices just as we're accepting that it's just not how the company works... I guess that's the bane of doing dev in a company that does resourcing as it's main focus thereby never understanding what's needed by us developers and why it is, or rather should be, different from the rest of the company.2
-
Working for a large client converting paper forms to the web. Stated goals, simplify data entry for clients, improve data quality, reduce resourcing in backend human processing.
We met to review prototype and discuss workflow questions. Crazy deadlines, with the usual changing scope creep.
We start to point out the need for data validation, to shorten # of questions based on answers.
Business says no. All forms should be submittable regardless of what user enters, don’t put validations in because all that warning messaging confuses them and takes up more time.
Web form should behave like the paper copy....
Welcome to 1975!!! This is why 2018 won’t be like 2018...1 -
Nothing like constantly having to spend 3-5 days of spin up on trying to help another team with their microservices because they have such a severe lack of documentation that I can't just follow a readme to get their projects running. Instead, I have to bug one of their developers to help me get it up and running (because they use non-standard project setups and dependency management), delaying things even more. No matter how much I scream that we need documentation no one makes it a priority.
Did I mention these are microservices written in Golang and I'm a front end developer? And I'm being made to work on back end tasks because we have a crazy high attrition rate and they won't back fill the back end positions.3 -
Applied for an internship, they gave me a test which was pretty hard for me and I didn't finish completely and properly. I spent almost 2 weeks on it until I was too behind on uni work. They offered me a position, and I negotiated terms. Now they tell me their human resourcing plans are going in another direction and won't accept me. :''''''''(4