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 - "#clients #frustration"
-
I'm tired of working for small companies.
I'm always either the sole developer, or the only dev for a specific stack, and therefore don't have anyone to ask for help. If I can't figure something out, it just doesn't get done.
It also means I don't have anyone to bounce ideas off, do code reviews with, or even friggin' have someone who understands what I do.
It sucks.
It would be nice to have someone I could actually ask for help! As it stands, I tear my hair out in frustration until I'm desperate enough to beg for help on discord or SO. whereupon, of course, I get ignored, as per usu. asdjfklasdjf
It really sucks.
It also means that I'm often surrounded entirely by sales people and managers... you know, those super-talkative people? who basically get paid just to talk? and are absolutely computer illiterate? Yeah. Think someone who says "I need my deliverables by end-of-week," "customer success representative," "turnkey solution," etc. completely seriously. (ew).
They're the people who constantly wonder why I can't push `n` features in `n/4` days, and ofc can't understand anything I say in response because of the aforementioned illiteracy. They're also the people who, almost every week, ask how long `y` is going to take, and then yell "But I need it by Friday! I just sold 50 clients on it!" (And they do this, of course, without ever asking for timelines)
It really fucking sucks.
Though I suppose larger companies would still have these problems.
but at least I could ask for help once in awhile. that would be nice.40 -
Life story of every Dev in nutshell :
Everything is working perfectly as expected and no body congratulates Dev and no one gives a shit.
Single thing is broken and the whole universe be like : "Where the fuck is that son of a b*tch? Bring that bastard in front of me right now."
😡😡😡😡6 -
You guys, I think I know what is it....I think I know why I wanted to be a developer.
It started off innocently enough. I was a young lad in IT. Wide-eyed. Absorbing anything and everything I could. Then, the asshole clients came.....
I would put on my best customer service face on, and address the client as calmly and as respectfully as I could. Reminding myself that their frustration is understandable.
To deal with the increased time dealing with clients took, I developed scripts to help me handle maintenance and keep my head above water. I developed scripts to streamline equipment provisioning for big deployments. I developed scripts to handle other technicians who didn't log-off the phone queue and fucked up our on-call flow. I put in place email rules to sift through the bullshit and time wasters.
I became a developer to streamline and make myself as efficient as possible. But the clients keep nagging. The bullshit keeps coming. The other players get in your fucking way.
There is no end you guys.... THIS IS ONLY TUESDAY. I can't script the passage of time. I'm....I'm.... I need a fucking nap.1 -
5 of us working for a larger team were tasked with doing some R&D, we blew everyone away and were given funding to start a new team and hire people to make the project come to life.
One of the high level sales / product managers we were reporting to, secretly had another team work on a similar idea because he needed it quicker (i.e. no time for research, just build it).
After forming new team, we were asked to work on his project instead because it was further along. 4 months later, big knob comes to a meeting and basically says "You know what, this doesn't look like we have enough features, we need more, but I don't know what".
Project blew up 2 months later, head of the unit kicked up a shit storm saying how badly everything was planned and canned everything. Now one of our clients is building nearly the same thing we were originally working on, the team no longer exists and i'm back on the R&D team.
Don't get me wrong, I LOVE the R&D team, actually didn't want to leave in the first place but was told I had to. But the sheer anger and frustration to see that walking cluster fuck strutting around like his shit doesn't stink, derailing entire teams, meanwhile we can't hire new staff due to lack of funding.
Heres an idea, fire the fucktards bleeding us dry ... then we'll have lots of funding. -
Client: can you spice it up a bit
Me: ok
Client: more spicing
Me: alright
Client: i liked the first one.....3 -
1. Learn to read and understand the errors and exception messages. While writing code you're going to be facing exceptions most of the time and the real cause of them is under a lot of generic error messages. That and a lot of patience and perseverance.
2. You're going to face clients and bosses that ask you to do a temporary "workaround" even though you know there is a best way to solve a problem even if it takes more time and effort. Don't "crash" against their ideas, try to find a mid-term between the fast and easy work around and the best solution and leave it open to improve it in the future. I have met a lot of developers that let the frustration stops them to be creative just because the approved development is not what they wanted to do. -
1. Manage my time better.
2. Find motivation to wake up and go to work.
3. Fake more smiles.
4. Kick ass hole (L)users in the throat when they piss me off...
5. Attend anger management.
6. Stop making shit lists.
In all honestly I need to dedicate more time to my personal clients and stop allowing my primary job’s frustration to drain my motivation to take care of their needs. It’s not fair to them that I chose the life I have. Find myself and attempt to love myself again. Create more time to focus on my health and goals. Surround myself with people that have goals and want to better their life. Find someone to share life with.
Then, with my luck; throw it all away and repeat these steps like a broken record. -
My team and I worked superrrrr hard for a client and help her build online presence, make graphic designs, motion graphics, Facebook posts, Instagram posts, digitalmarketing. After two weeks, she announced she is shutting her business down. All that hard work was for nothing.7
-
If only clients could understand the frustration of implementing things which don't seem to fit in the natural order of software development, then the world would be a better place.1
-
Building an export in our app for shapefiles; ancient and completely outdated format. Currently there are dozens of better formats available. Unfortunately our clients are too dumb/lazy to learn how to work with other formats. Moreover, the irony is that many of their issues will be solved by just using any other format. Saving tons of frustration and hatred towards me for things I have zero control over.
Anyway, as I am coding I run into many ridiculous and well known shapefile issues.
Me goes to stackoverflow to find hacks
Me finds many posts with a title like "how to <..> shapefiles"
Me finds the same solution for every issue: "Don't use shapefiles"
Clients, please, get your shit together. The whole Internet hates people like you for using shapefiles. -
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. -
mail: contactus @ hacksavvy technology . com
Website: https : // hacksavvy techrecovery . com
Whatsapp : +7.9.9.9.8.2.9.5.0.3.8
While working in Auckland, I found myself immersed in a vibrant tech environment. One of my coworkers was particularly passionate about a new blockchain project he had been developing. His enthusiasm was infectious, and after several discussions about the project’s potential, I decided to invest 20,000 NZD.At the time, I was aware that investing in blockchain and cryptocurrencies could be risky, but the vision my co-worker painted was compelling. Over the following months, the project gained traction and my investment skyrocketed to an astonishing 500,000 NZD. I felt a mix of excitement and disbelief; I had never expected such a substantial return. The success of the project fostered a sense of camaraderie among the team, and I believed we were all aligned in our goals.However, things took a turn for the worse. As the project matured, disagreements began to arise within the team. My co-worker and I had a particularly intense argument over the direction of the project and some strategic decisions. Frustration boiled over, and in a moment of anger, he made a decision that would change everything: he locked me out of my email account. This wasn’t just an inconvenience; it meant losing access to crucial information, project updates, and the ability to communicate with clients and partners.Feeling isolated and frustrated, I reached out to friends from work, hoping to find a solution. They listened to my predicament and provided me with some suggestions on how to regain access. One of them mentioned Hack Savvy Tech , a service known for their expertise in retrieving lost accounts and data. Skeptical but desperate, I decided to give them a try.I contacted Hack Savvy Tech , explaining my situation in detail. Their team was remarkably understanding and guided me through the recovery process step by step. They employed various techniques to restore my access, and within a few days, I received the good news: my email account was successfully recovered. Relief washed over me as I regained access to not just my email, but also my connections and the wealth of information I had been locked out of. While my relationship with my co-worker remained strained, I was grateful for the support of my friends and the expertise of Hack Savvy Tech . This experience taught me the importance of maintaining strong professional relationships and having a backup plan when investing in volatile projects. The lessons learned from this journey would stay with me as I navigated future opportunities in the tech world.