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 - "nitpicking"
-
😎 = me, 💩 = client
💩: "I must emphasize that I'm on a tight schedule. I need this done in 2 weeks."
😎: I cut some features and take the job.
As agreed, I send a progress report at the end of the week to get feedback.
💩: *nothing*
😎: He must be busy... I'll call him if he doesn't reply in a few days.
💩: *doesn't answer call*
😎: Time running out, still no feedback, I assume everything is fine and finish it a day before the deadline. Suddenly:
💩: "Hi, how's the project going?"
😎: "...good... WHERE HAVE YOU BEEN???"
💩: "Oh, I went on a quick vacation"
😎: *wants to die a quick and painless death*
"There's only like a day left..."
💩: "Right... Soo, here's the feedback you asked for"
*dumps 4 paragraphs of stupid nitpicking on me (rants following)*
😎: *wants client to die a slow and painful death*13 -
I’m going to fucking kill my boss.
He’s known about how I’ve been writing this fucking ticket (screwdriver followup) for four fucking weeks, and on the last fucking day (yesterday) he tells me it’s not the correct fucking architecture and to rewrite basically all of it using <unknown bullshit> instead, and that i must have it done by today — by this fucking morning — so it can make the release.
WHY THE FUCK DIDN’T YOU TELL ME ABOUT THIS AT ANY POINT IN THE LAST FUCKING MONTH WHILE YOU WERE BUSY NITPICKING MY FUCKING CODE YOU FUCKING CUNT?!30 -
Front End programming is the worst of all worlds.
I am a Full Stack developer that during every interview says "i can do front end stuff if needed". Something gets lost in translation and becomes "I do only front end stuff".
I don't mind front end development, but i hate urgent nitpicking that happens every time. Everyone else on the team works by regular tasks and deliveries (sprints and release dates), but my work consists of being the brush of the creative mind of someone else, that could not figure out how to make a good design before sending it out to me.
I am not a designer, a designer job is a creative one, i am just a brush that the team uses to complain why this button looks wrong on this not designed platform.9 -
Managers: wE wAnT tO bE LeAn aNd MoVe FaSt As PoSsIBLe wiTh NeW FeAtUrEs
Same Managers: Can you make this icon 2 pixels smaller?! Shift this element left?! Swap out this icon?! Use a different color here?! A perfect feature and design is critical!!!!!!
FullStackClown: You can either be lean and fast, or be fucking nitpicking clowns 🤡 about this stuff and slow us all down. Choose one.
Managers: ...
FullStackClown: Sit down and shut up7 -
The nightmare continues.
Currently dealing with a code review from a “principal” dev (one step above senior), who is unironically called a “legendary dev” by some coworkers. It’s painfully obvious he didn’t read the code, and just started complaining and nitpicking.
It’s full of requests to do things that make absolutely no sense, and would make the code an unmaintainable mess.
• Ex: moving the logic and data collection from the module’s many callers into the module instead of just passing in the data.
• Ex: hiding api endpoint declarations by placing them in the module itself, and using magic instance variables to pass data to it. Basically: using global functions and variables instead of explicit declarations and calls.
• Ex: moving the logic to determine which api endpoint to use, for all callers, into the view.
More comments about methods being “too complex” (barely holds water) right next to comments saying “why are these separate? merge them together!”
Incredulously asking how many times I’m checking permissions and how ridiculous it all is. (The answer? Twice.)
Conflating my “permissions” param and method names with a supposedly forthcoming permissions system overhaul, and saying I shouldn’t use permissions because my code will all have to get rewritten. Even if that were true, and it’s likely not, the ticket still needs to use the current permissions. I can’t just ignore them because they might be rewritten someday.
Requests to revert some code cleanup because the reviewer thought the previous heavily-nested and uncommented versions (with code duplication) were easier to read. Unsurprisingly, he wrote them.
On the same ticket, my boss wants me to remove all styling and clientside validation, debouncing, and error messages from a form. Says “success” and “connection failed” messages are good enough. The form in question sends SMS and email using arbitrary user input for addresses. He also says it shouldn’t be denounced on the server, and doesn’t want me to bother checking permissions. Hello, spam!
Related: the legendary dev reviewer says he can’t think of a reason why we would want to disable the feature for consumers, so I should remove the consumer feature flag.
You can’t make this stuff up.7 -
Here's to clients who wish to pay "per project" instead of "per month". Man, fuck that.
Back when I was still a novice, I took on a couple of small time projects from clients who contacted me after looking at my GitHub, and they all wanted to pay me a lump-sum for the project. Because I'm an idiot, I thought sure, what difference would that make. Boy was I wrong.
What followed was me finishing the projects well before time but because of the clients' constant reiterations and changes in design and nitpicking every decision I made while creating the websites for them, the projects dragged on for weeks longer than they were originally intended. And I fucking got paid that one-time amount in the beginning. All this maintenance, for free. Even though I had not explicitly agreed to the maintenance part, since they never finalized the specifications of the project, it just never got "done" officially, and all the maintenance part just came under development.
How many different kinds of disgusting does someone have to be to do this? I should've fucking said NO to those terms, but I had to have experience. Well, nice experience that was. Never again. :(1 -
Retarded senior web dev:
shouting 'STOP' to the ones who pointed out his design flaws
cannot accept a js file with more than 100 lines.
nitpicking others not limited to his owm group
eager to try bleeding edge alpha builds packages for large application
left the company before finishing the project he started2 -
Me and my manager throughout 2020
January:
Me: So umm, we can release the new app version
Manager: No we promised client X app first go build that
Me: umm, ok.
February:
Me: so the app is done, but client hasn't setup area L so there is no data there
Manager: ok, I'll have them setup area L soon ™️
March:
Manager: area L is too much work to setup, use workaround L thats way better
Me: ok ...
April:
Manager: client is nitpicking on design and layout please make this mess even greater
Me: ok, anything else?
Manager: yeah also start on app for client Z!
Me: and our app update?
Manager: later son! Risk tooo muchos!
May:
Me: the mess for client X is done, and first version for client Z is also ready for test
Manager: ok good work, here is a new set of things to mess up
Me: but... Seriously, wtf?!
Manager: clients want quality
Me: ah ok, not nitpicking, cool
June:
Manager: client X went MIA, but client Z will send you a weekly list of things they don't understand and want to change
Me: ah great, truly worth postponing my February holiday to release nothing
July:
Manager: so, how we doing on all them changes
Me: well, I am a loyal custodian with alot of pleasure in my work!
Manager: ah ok good!
Me: any news from client X??
Manager: who
Me: mkay ... n.v.m
August:
Me: can we release yet?
Manager: change, we can!!!
Me: are you Obama?
Manager: ambitions
Me: fuck you pay me
September:
Me: I am confident we can now release all 3 apps as promised mid september
Manager: great!! Good work
Also manager: you know that immensely complex area within the app? That needs a complete rewrite because we have bad ux there!!!
Me: ok... To which requirements?
Manager: good ux, we must have standards
Me: but the layout of page R id generic as page F so then we need to align there as well
Manager: go! Do!
Me: ok I'll come up with my own requirements then
Manager: we also need documentation
Me: really!!!! How clever of you to fire colleagues T & P and we now have zero workforce for that
Manager: things will get better someday
Me: ah, great! Put it on my calendar
October:
Me: I need a sabbatical biatch
Manager: a what?4 -
Oh man where to start:
Not wanting to use LINQ because he did not wanted to "download external dependencies"
Not wanting to use prepared statements on their php sql code, and refusing to use pdo because they will "always use mysql"(moved to postgreSQL shortly after I left)
For some reason including a php file that only had ?>......thats it....only ?>
Use c++ but refused to learn oop and use structs for everything, importing stdio.h and printf everything.....like really?
Maybe just nitpicking, but refusing to use the recyclerview pattern on am android app. The implementation was faster after I made the change.
Importing a library for promises instead of using the ones already in the language(JS)
Changing the style of aaaaall p tags instead of using classes as well as refusing to use divs in place of p tags...well...fuck
Not indent his ASP classic code
Use notepad on his asp classic code
Use ASP Classic in 2017, even for new projects6 -
With over 10 years as a dev under my belt I never wanted to change company before my probation is even over. I never felt so drained, and pissed off for the entire duration of my working hours, every day for about 4 months straight. I was thinking it should get better, I listened to all the rubbish webinars about the company culture, how inclusive and diverse we are and how they value phycological safety and how everyone should feel safe to speak their mind. The people are fucking reviewing my approved and merged PRs and expecting me to address their comments. Like someone goes on holiday and when they’re back they want to spray wisdom around, and that seems to happen to everyone not just me. When we have technical discussions and I express my opinion I get given out to for speaking too much. Like what the actual fuck, your code is shit, everyone knows it and complains about it, but we should look at what we already have as an example. How the fuck you think you can improve your code if your not going to change your shit. Writing class diagrams for about two weeks at start of each project and nitpicking every fucking thing, only to abandon it after our first sprint as the fucking requirements have changed and what we agreed at the beginning as no longer relevant. No shit as if they don’t know requirements change ALL THE FUCKING TIME AND THIS IS EXPECTED. I was also asked to send a slack message every morning when I start working, when I get my lunch, when I am back from lunch and when I finish work. Have to fill in some stupid weekly update system with what tickets I’ve worked on during the week, like have you heard of Jira filetrs ? Stop asking me how I am getting on if I’m fucking closing all my tickets every sprint. I don’t ask you questions, if I finish all the work you asked me to on time, you can safely assume I am doing fine. Also your fucking back to back meetings are not helping me close my tickets any faster. Already got an offer from another company I am out of fucking here.
YOU CAN ALL STICK YOUR PR COMMENTS, ENDLESS MEETINGS AND WHAT NOT UP YOUR FUCKING ARSES. 🖕🏻🖕🏻🖕🏻🖕🏻🖕🏻🖕🏻4 -
@dfox sorry for nitpicking, but could you check the "viewport" meta tag? The "-" in "minimum-scale" is missing.
I like the Chrome console to be clean :P3 -
Attention: incomming resentful boiled up for months rant.
Hands down G2APAY is the worst because:
Merchant account aproval takes fcking months. It starts with unreasonable delays in documents approval. I mean insane nitpicking. They want to see merchants name surname and address on every god damn document that you submit even if for example bank statement doesnt include these details. I had to manually edit pdf’s just so that they would fck off and approve the merchant application. Insane requirements for document check also combined with their email only support answering only once a week you will have to wait one month just to get your account approved.
Then you get to the fun part, approval proccess for vendor gateway and webhook integration. They are nitpicking everything you can imagine: about website not having https, website forum missing some icons, merchants phone number being from another country then he is, and bunch of other hundreds of problems imagined only by them. Again combined with their one email reply per week policy you will waste atleast one month to finish up your integration.
Now finally you are their client and you think you can chill and go back to focusing on your business? Nope bro. Prepare for threatening emails. Last time I got a request to install https or my merchant application will be shut down. I was given 3 days notice on a fcking friday and had to do it.
Then g2a backend is crashing quite often. Combined with their one email per week policy you are fcked in the ass if your users were not able to pay through g2a and you will get no compensation.
Their backend documentation is shiet. Not clear how to integrate everything and after you integrate they make changes without publishing any changesets. Your integration is working? Good luck if it will still be working tomorrow.
And the very worst part is that they stopped proccessing credit cards like month ago with zero notice. Its been weeks and still zero news about bringing card proccessing back. They sad that they were acquired by some other company so shitty support got even shittier now while they are in a proccess of handover.
So yeah thats the worst vendor I have ever seen in my life. For example integrating paypal took me 30 minutes. Integrating stripe and getting all documents reviewed took me one business day. Same with paymentwall integration and document approval took 1 business day. Support is amazing and even have a phone number that I can reach if urgent problems arise. Thats how it should be. Thats why I can pay percentage of my transactions with a smile for them.
Sorry for the typos since im typing on my shiet phone while driving.
Eat a bag of dicks g2apay. I hope you go bankrupt and shutdown.21 -
I am stuck with another Postman.
Attrition in my current org is way to high in product teams and we have only one designer shared between ~100 people (10 product lines).
My ex-lead (a genius) and my skip level manager (very smart chap), both keep saying that my manager is a very good manager.
However, in reality, I don't find so.
- Only responds to my questions
- Ignores any other form of communication
- No help on any front
- No support or validation on my tasks (hence, I have to actively keep asking for feedback)
- Regularly cancels 1:1
- Involves other team members in 1:1 and cancels theirs as well
- Says I am doing well but keeps nitpicking in my work
- Hardly reviews anything
My company is amazing, pay is good, perks and opportunities are wonderful, kickass learning but my direct manager isn't making me feel comfortable working here.
Maybe she is too cramped with responsibilities but again, I have never seen her deliver anything and all she does is a postman job of taking inputs from her manager and pass on to me and coordinates until me and her manager decide to jump on a call and figure things out ourselves.
It's just been 3 months and I feel more annoyed than worried about being here.4 -
Few years ago as a junior android dev with couple years of self taught experience of working in startups I submitted a simple android app assignment for a junior android dev role. Assignment had only like 8 requirements so I followed them to the letter. That didn't end well.
App was simple just 3 screens. Login screen with username and password input fields, login button.
Had to call a login endpoint after login button was clicked, redirecting to home screen, calling items endpoint, displaying a list of items and when an item was clicked passing item data and redirect to item details screen.
Needless to say big swinging dick senior was not impressed. UI was not perfect, I forgot to display a loading animation when fetching data, didnt handle back button properly.
I agreed with some points but other comments were clearly just nitpicking: his preferred variable naming conventions, his opinions on architecture that was not up to his standard (official google arch at the time was not up to his standard).
He also was mad that app wasn't prepared for release to googleplay (another out of the ass requirement). Like I would prepare a 3 screen app for prod release that he will forget ever existed after 20min of his review.
Lots more of nitpicking, encapsulation this encapsulation that, omg now hes shocked that there are a few warnings after the project is built.
Regardless my self confidence was destroyed at that point and after few more negative experiences I dropped android dev alltogether for a couple years and switched to game dev.
After game dev ran its course I went back to android dev and found a supportive place where I could grow.
Looking back, they were actually hiring atleast a mid level for a junior position but I was grilled as a senior. The guy literally didnt wrote any single positive thing in that review about my code even tho my senior peers said my project was decent back then, its just that I didnt handle a few edge cases and that's all.
I looked up the guy in linkedin, turns out hes a uni dropout who posts all books that he red about software dev in his education section of his linkedin profile. Found a bunch of other narcissistic stuff on his profile. Guy was a fucking idiot. Even if I worked under him it would have probably sucked.
Learned some important lessons I guess. Always get a second, 3rd and 4th opinion and dont take criticism too seriously. Always check what kind of person is providing feedback.4 -
Around 6 years ago I started at this company. I was really excited, I read all their docs then I started coding. At every code review, I noticed something was a little off. I seemed to get lots of weird nitpicking about code styling. It was strange, I was using a linter, I read their rules but basically every review was filled with random comments. About 3 months in I noticed, "oh! there aren't actually any rules, people are debating them in my code reviews!" A few more reviews went by and then I commented, "ya I'm not doing any of this, code review isn't a place to have philosophical debates." All hell broke loose! I got a few pissed off developers, and I said, listen I don't care what the rules are, you just need to clearly fucking articulate them and if you want to introduce one, I don't care about that either just don't do it in the middle of my review. I pissed off 1 dev real bad. Me and this dev were working together, the QA person on the team stood up and said "hey! you know what I love about your code reviews?!" The other dev and myself looked at each other kind of nervously, "I love that you're both right, these are all problems!"... 1 year later (and until now) me and the other dev are still friends. Leave it to QA to properly identify the bug.
-
I'm currently at a company where we have "performance reviews" every 2 weeks, and based on the outcome we get a percentage which then is used to calculate a performance bonus.
This is simply my manager (also a developer) who has his Excel spreadsheet, looking at tasks I did over the course of the past 2 weeks and almost nitpicking to find some fault. There is no code review or software demo to see what's been done either... I was there for the first 3 months and I don't think anyone had even open my code!
And when confronted, I get told that "You should also somehow be financially liable for the goings-on in the business", along with a 2 hour meeting to support that.
This is NOT how you motivate developers!
Apologies for the long rant...
</rant>7 -
This fucking company man. Implementing a simple feature (just a couple settings in the android app) is taking me 4 fucking weeks(feature was done long time ago, but not in the way that. they wanted, even though I followed existing implementations). I have like 60 comments in my code review from which half feels like it's just purely nitpicking. I already have 2.5 years experience and I just want to kill myself or quit the job if every code review here willl be like this.
-
Coding is like handwriting.
Code review is about having a common understanding of the big picture and ensure be features follow the general architecture and process flow.
Code review is not about nitpicking on FUCKING TRAILING WHITEFUCKINGSPACES , lower case vs upper case SQL statements, extra empty lines AND EVERY FUCKING MINOR DETAIL you can imagine18 -
Spent many more hours than my estimate to get a project out the door. Client is now nitpicking everything. I know the client is always (usually) right but this feels ridiculous. His site is 20x faster than it ever was before but just one page is a little off _after adding more content_ and it's a crisis.1
-
Why QA should never be left "in charge" of marking priorities on tasks before "demo day" deployment and client handover of a product.
New and refactored, key, features need to be deployed by "demo day", and most developers and the PM (not me) have already been re-allocated to new clients and projects. There's several things being done in paralell to get it done.
QA: We need to be able to download CSV files showing affected users if i do extremely rare action X, and this should pop up in the system for the first 24 hours after doing X.
Priority: High
New priority for feature Y: Medium
(Action X may never be used at all)
This is implemented, reviewed and deployed.
QA: I want a timestamp in the file naming, I'm experiencing duplicate files.
Priority: High
Feature Y: Medium
Develop, review and deploy timestamping for the CSV files.
QA: They are only marked with DD/MM/YYYY, I performed rare action X several times in one day, I can still get duplicate file names marked with numbers. This is #1 priority!
Priority: High
Feature Y: Medium
...Okay, this is nitpicking, this will never happen, but fine. Overtime to do the extra minor, minor adjustment, down to hours and minutes, get it reviewed and deployed at the end of the day.
QA: I managed to do rare action X 6 times in 1 minute, I have duplicate files. It needs to be down to seconds. This is top priority.
Priority: High
New priority for feature Y: Low
.........
Constant interruptions, moronic priorities and voicecalls throughout the entire day.
Dear QA, you can be fucking donkeys at times.4 -
when you don't know how to front end css and you get help from your tech leads and now you have to sit through the slow nitpicking of various dogshit mismatched overhangs and pixel jiggling that already exist in your product and may or may not be related to your ticket
well at least at the end of the call they helped you fix the shit for your ticket4 -
Just received code review from interview technical task. 50 percent of it was because of encapsulation (that 5-8 variables could have been private instead of public). 20 percent was about shit that was expected but missing (error validation, dependency injection). It was missing because it was not specified in app requirements and also noone said that I have to build a production level application for a simple interview here. 10 percent was nitpicking about formatting(I used default intellij formatter) and one ide error that appeared because of project importing. And only 20 percent of feedback was actually constructive and useful. Cool. Also developer said that he was shocked that I made loading animation but didnt call it in my app. However I made it, but if you have fast internet connection it doesnt show up. I mean if you run my app on a phone with gprs connection u will see that damn animation. What Im supposed to do slow down the app so u could see it? But we are building production level app here no? Shit. It feels like he applied double standards to me or something. Half of review nitpicking about useless details and another half about shit that is expected to be in the app but was not even communicated. Also I did not get developers contact so I could ask him what the fck he wanted from me.1
-
Git: "Your local changes to the following files would be overwritten by checkout. [...]
Please commit your changes or stash them before you switch branches.
Aborting"
Fucking nitpicking, that's not "Aborting", that's meant to be:
"Dear user, would you like to overwrite your current changes, even more so as you are currently in a so-called detached head state anyway, as you obviously just checked out an old tag to try a temporary rebuild of an old project state."
Yes, the build targets are checked in, as this can be very useful in some scenarios.
It's just! some! CSS! from the SCSS!
Stop "Aborting"!4 -
@dfox The feed button on web frontpage is sort of invisible up in the corner. Expected place for "read without the app" is below the app symbols (in my mind). Also "Get the app to +1, post and comment" seems like an outdated remark(?)
Is there a better place for suggestions and general nitpicking btw? :) -
I don't get it, why having more than one decorator looks "weird"? that's idiomatic Python AFAIK, that's sounds more like nitpicking on aesthetics :/1
-
Sometimes I don't do a proper review because I don't want to seem very nitpicking. However, now I have to maintain the code that was merged and it has some stuff which is not correct. Now I have to fix it.1