Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "too much repetition"
It's too many features for me to keep up with. And the client just bounces between this matrix of all the possible permutations of them, refusing to admit that he is asking for mutually exclusive behavior in more than one place. I have mentioned to him at least 12 times a year that there is too much going on, not organized, we need to simplify, prioritize, or we will have 100 half baked untested features.
Of course it is more or less made it out to be that this is all my fault, or at least it's hard not to feel that way when I say:
It will be a long time before X will be working, we need 25 other things first.;
Next day he asks:
Have you made any progress on X;
I reply: Now we need 24 things to be done at this rate it will be a month.;
Ok but I need this yesterday. How about if you add a new feature Y that does everything X does without those 24 things?;
I reply: That will not work at all like X. Y is just X + 1 more feature.
He replies: Ok well I need Y so when you're done with X I need a way to do it like Y also. I just thought it'd be easier.
EASIER TO ADD MORE FUCKING FEATURES YEAH SURE THATS EASY AS FUCK YOU FUCK FUCK FUCK. He's a nice enough guy, pretty smart compared to my first few paying gigs, but wtf really? How do I come out and tell you I need 25 days and you ADD more work? This was one example.
IN TWO days he has added 12 features. And during the week has asked for 29 UI interfaces to be COMPLETELY different. This is becoming COMMONPLACE. Every week there is either a huge change, or a conversation like about that finds its way into the entire business flow inside an dout.
The worst thing is: I TOTALLY understand what he needs. I feel that HE doesn't. This weekend I spent literally HALF of his retainer on getting equipment into my hands to bring it back to find out it DOESNT WORK. Why aisn't HE doing this so I can finish the features from NOVEMBER that HE NEEDS in order to PROCESS SALES.
I've tried and tried but I just can't get through to this client what a tremendous waste of time his \"process\" is, for lack of a better word. Constant changes, contsant additions, lack of clarity, needless repetition and contradictions, constantly adding moonshot ideas to compete with every industry in the region, and not beta testing anything until something goes wrong.
Fuck this guy! His business is failing and I felt responsible for the longest time but it is clear to me that if I wanted to save his business I would have to ignore 95% of his feature requests. I ignore 50% now because of the stress in trying to determine which of the 3 different paradigms he is talking about changing. I will lose this client, and I feel like he will sue me to get all of his money back. He holds me to very little honestly - BUT WEEKLY reminds me that he won't be able to pay me next month if feature XY and Z arent ready!
If a developer is CLEARLY overwhelmed, it makes NO sense at all to continue to PILE ON feature after feature
rant+=", after feature"
except DevHeadExplodes as inevitable:
There is so much confusion in the world of programming right now, at least for me. I bet there’s only so many concepts going on and that these concepts are realized in certain ways. E.g. programming following certain paradigms and practices, also different workflows, containerization, agile, devops etc.
When searching for tutorials in different subjects it’s horribly aggravating to learn to use the tools. Not because they are inherently hard or bad in any way. There’s just so many different tutorials, some badly given, some that are great but which bring up to many foundations you already know so you find yourself getting bored to the point that you just stop listening. Many tools are used for so many use cases, sometimes overlapping each other, they use concepts to that you’ve heard hundreds of times before. Many times they want to do things in a special way so even if the concepts are the same you still need to fucking listen to the same old thing while learning how to write a command a slightly different way or how some tool is supposedly better than another.
I’m realizing that what I’m so sick of is the lack of TLDR information about new tools with some short description of how to use. Where you didn’t have to re-hear stuff you already knew or had heard so many times unless for a very good purpose, such as to show exactly how it’s done differently than another relevant tool. In a dream world the TLDR information could also remember my skills and remove the parts I didn’t need to know about any new tool.6