I have this one major pet peeve - getting interrupted on any messenger by "hey".

Q: Hey
A: Hey, what's up?

-minutes pass, I try to resume work-

Q: Do you have a second?
A: Sure, what's up?

-minutes pass, I try to resume work... Again-

Q: Do you know anything about #feature#?
A: Yeah, I wrote most of it, what do you need?

-minutes pass, I try to resume work... AGAIN-

(goes on same pattern, takes half an hour for a 10 second question/answer)

Like... Come on!!! Don't do this to me

I get it, I like to be cordial and friendly - but there is absolutely nothing stopping you from getting your message across without making me have to go back and forth (interrupting my work).

My biggest pet peeve at the moment is people without any development experience using version numbers.

Me: "Communicating a release date for the feature towards clients is dangerous, we have a developer shortage, and currently don't really have enough capacity to..."

Manager: "What we release next month doesn't have to be perfect, it is just a v1"

Me: "You mean it's a beta? If that's the case, could you maybe differentiate the requirements of the beta, let's call it a 0.1.0, versus the 1.0.0-rc, the release candidate?"

*Feature is eventually merged into production, barely in a beta state*

Manager: "So I have some ideas for the v2"

Me: "You mean 1.0.0"

Manager: "Let's compromise and call it v1.5"

Me: "Let's compromise, you stop communicating release dates, AND you stop using version numbers..."

Manager: "That's not a compromise..."

Me: "...I wasn't finished... And I won't respond to the recruiter who just offered me a better paying job"

it really grinds my gears when people name their files with spaces in them 😰

Online tutorial pet peeves
————————————

My top 10 points of unsolicited ranting/advice to those making video tutorials:

1. Avoid lots of pauses, saying “umm” too much, or other unnecessary redundancy in speech (listen to yourself in a recording)

2. If I can’t understand you at 1.5 - 2x playback speed and you don’t already speak relatively quickly and clearly, I’m probably not going to watch for long (mumbling, inconsistent microphone volume, and background noise/music are frequent culprits)

3. It’s ok to make mistakes in a tutorial, so long as you also fix them in the tutorial (e.g., the code that is missing a semicolon that all of a sudden has one after it compiles correctly — but no mention of fixing it or the compiler error that would have been received the first time). With that said, it’s fine to fix mistakes pertinent to the topic being taught, but don’t make me watch you troubleshoot your non-relevant computer issues or problems created by your specific preferences (e.g., IDE functionality not working as expected when no specific IDE was prescribed for the tutorial)

4. Don’t make me wait on your slow computer to do something in silence—either teach me something while it’s working or edit the video to remove the lull

5. You knew you were recording your screen. Close your email, chat, and other applications that create notifications before recording. Or at least please don’t check them and respond while recording and not edit it out of the video

6. Stay on topic. I’m watching your video to learn about something specific. A little personality is good, but excessive tangents are often a waste of my time

7. [Specific to YouTube] Don’t block my view of important content with annotations (and ads, if within your control)

8. If you aren’t uploading quality HD recordings, enlarge your font! Don’t make me have to guess what character you typed

9. Have a game plan (i.e., objectives) before hitting the record button

10. Remember that it’s easier to rant and complain than to do something constructive. Thank you for spending your time making tutorial videos. It’s better for you to make videos and commit all my pet peeves listed above than to not make videos at all—don’t let one guy’s rant stop you from sharing your knowledge and experience (but if it helps you, you’re welcome—and you just might gain a new viewer!)

Pet peeve:

Putting screen shots in Word documents, then attaching the doc to tickets.

Mucking forons.

Pet peeve #149:
Use Fibonacci sequence to indent your code.

Biggest pet peeve of languages are those that use single quotes for strings.

It's single quotes for characters, double quotes for strings. Suck my diiiick

Pet peeve: When people use "Jira" to mean story / task / sprint / epic.

*Real* pet peeve: When people use it with more than one of the above meanings in the same sentence.

"Will we finish this Jira (story) by the time we close the Jira (sprint) on Monday?"

Dude, wtf. I actually have to decode your sentences to figure out what you're on about. Just learn the right terminology. It's not hard.

Oh my God. New pet peeve:

People who answer questions on Amazon with an answer like "idk I just got this :(" or "idk man I bought it as a present."

Why the fuck do you feel the urge to answer a fucking question without actually answering it? Like are you that fucking stupid? Jesus Christ.

Pet peeve of the day: People littering code with comments that repeat already obvious method names.

// Submits public key password
SubmitPublicKeyPassword(string psw)
{
//...
}

I work with junior developers, guiding them and teaching them on a daily basis.. my biggest pet peeve?
When they finish typing code and without testing it ask: "Is this right?"

HOW THE FUCK DO I KNOW? Seriously! I don't know what all your specs are, maybe try running it before asking??

ffs.

Oh yeah that shouldn't take too long right? I mean it's just the front end.

No shut your fucking dumb ass mouth up. It will take long. The front end is very complicated, and your stupid fucking ass who couldn't learn to code is in no position to estimate how long it will take. Do us all a favor and stick to the "business" side. Fucking incompetent idiot.

If you're not a programmer, when it comes to estimating how long a task will take. Just shut the fuck up. Just cause you work in this industry does not qualify you to estimate a task. Just shut the fuck up.

Pet-peeve: fellow devs who think scoffing/dismissing/not-my-probleming before actually understanding the issue is a sign of intelligence; newsflash: you are being lazy, disagreeable and unprofessional.

Pet peeve #91847 - when your non technical manager routinely forwards you articles about technical subjects, usually written by non technical idiots, and says "please see if this is something we should be using".

Yeah, I get that your business manager friend has heard Blockchain is amazing, Rsocket is revolutionary, and everyone should now be using Kafka, but none of that makes any sense for our use case.

The clincher had to be telling me to look at AWS groundstation though. And no, we don't have anything to do with satellites...

Pet peeve of the week: code with "== true" at the end of boolean expressions.

if (coin.isSilver() == true) ...

which is just as sensible as

if ((coin.isSilver() == true) == true) ...

or

if (((coin.isSilver() == true) == true) == true) ...

Personal pet peeve.

I'm not a germophobe. But if your hands spend most of their time down your pants, or you've been eating food with them, or they're just generally disgusting, please wash before thinking of using my computer.

There is nothing I hate more than finding crusty fingerprints on my keyboard and mouse.

And if you're using my computer I likely know where you live. 🔪🔪

I have the bad habit of programming without initializing a Github repo or by the time I upload it to Github I’m either done or close to done with it.

It’s not necessarily a terrible thing it’s just a pet peeve of mine.

One of my biggest tech related peeves, someone shows a video as part of their presentation but doesn't use full screen or even worse leaves the cursor over the video.

My biggest pet peeve is whenever you're in the toilet, you know, doing a number 1, a lazy number 1, a number 2 or the combo. For most toilets, including in our workplace, its very clear that the door is locked. Usually it is either written or signified by the color red. Despite all this, you still have those people who will almost batter down the door despite being CLEARLY LOCKED.

Fucking hell, that grinds my nuts.

Subject: a rant for devRant

Hello,

Not entirely sure why or when exactly it happened, but after I joined mailing lists I have a pet peeve for people who don't use a proper subject line, or don't use email when I literally made a mail server for that purpose (some organizations really prefer calling apparently). Is it really that hard to summarize a message in one sentence? Hell half the time even the message itself is just a few sentences.

Also the greeting and salutation at the beginning and end of email messages. I find them so redundant. Has anyone ever gotten any meaningful information out of "Hello", "Greetings", "Dear", or something like that? Or "Best regards" or whatever. I get that it's just being polite but it's so meaningless! I really don't like using them anymore. Just a message block and who it came from, that's all it needs to me. Instead pour some effort into the damn subject, the title of whatever drivel you're putting out there! Or replying to an email *only* when the subject matter is still related! Or actually replying to the damn email if it's still that subject matter...

I probably sound like an old man, but seriously.. email isn't a hard concept once you "get it". Anyone can write a halfway decent letter, why isn't that the case for email?

Best regards,
Condor

There's little irritations that happen when working with clients over time that let you know that they're stuck in the past and definitely not the kind of client you want to have long term.

My personal favorite example:

"Can we put an icon that shows the weather on the banner of the website?"

Note: I don't make "websites," information portals, content pieces, etc.

It doesn't to matter what type of application it is; time tracking, HR, mortgage application, industrial control system, etc. I don't know why, but every single client I've ever had where I've been saddled with one or more people who have no business being anywhere near the term "stakeholder" asked for this stupid, banal, 1995 web portal fuckery. Their shitty little mushroom stamp contribution wasting everyone's time.

What's worse, they want it be prominent in the screen real estate. It can't just be a responsibly sized waste of space like the screenshot's top example (from a company whose entire business is weather, nonetheless). No, it has to be the busiest fucking thing in the control space, as in the example inferior.

Or maybe I'm just wrong and people desperately want to know if the sky is going to piss on them if they leave the cave.

Anyone else have a pet peeve in regards to recurrent, pointless functionality?

In "Sprint Planning", the team is supposed to come up with stories, break those down into tasks, estimate those tasks as a team, then let devs choose what tasks they want to work on based on the stories pulled into that particular sprint.

Instead, our manager creates the stories. He assigns the stories to each developer and then has that developer announce his theoretical tasks (without any research on feature's or project's requirements!) in front of the entire team. So, when I say, "I think it will take me 6 hours to implement this feature", he says, "6 hours? I think it will take 3." and then types the estimate as 3. I have so much rage when that happens. Then we continue to sit in the room for 2.5 hours where we go through this long data entry mess of him typing out tasks and second guessing estimates. There is no team deliberation or collaboration, its whatever the manager says.

While there are many issues I take with this approach, my pet peeve would be the second guessing of the estimates. It would make sense for teams members to second guess estimates as long as they are the same teammates who have the ability and possibility to take on the tasks themselves.

But I disagree with a manager seconding guessing an implementation feature that "I" definitely have to do alone, and they do not possess the immediate knowledge to implement it themselves.

Pet Peeve... If you are a creator, you are largely doing technical content, and the channel is not about your personality. Then I don't want to see your stupid face. I want to see technical info like text, graphics and block diagrams. I don't exactly know why this bothers me, but it does.

Biggest pet peeve is when someone develops a shitty project using XYZ technology/language and a tutorial and they somehow think they know XYZ and all of it's intricacies and are an expert dev in XYZ. 😐😐😐. No you fucking know how to follow a tutorial and you have a small understanding of XYZ. End rant.

what the fuck is up with devs who always send screenshots of code and/or log files? In Slack, which has great functionality for formatting text snippets in a variety of languages and data types?! screenshots of code are really a pet peeve lately. You can't copy the text or click on any urls or do *anything* with a fucking screenshot. so dumb.

Recently thanks to Whatsapp I've discovered a new pet peeve:
People pressing "send" after finishing a sentence (at best) instead of making new lines, resulting in around 5 new messages received at lightning speed.
Not to mention, they keep on going while I am trying to reply, losing my concentration in the process! 😡

Pet peeve #1: those guys who iterate over a whole array with 'for' and 'break' on a condition. Have you ever heard of fckng 'while'??
Git source code will be the death of me.

My biggest programming pet peeve: The code throws a series of unchecked assignment errors and yet it compiles.

Go home Intellij you need some sleep.

Pet peeve: people who photograph their computer screen to show you what's on it.

Pet peeve of the day: Open source software that shouts about all the benefits of being freely available to everyone, open, loving the community, etc. - but the moment you install it you have to jump through a bunch of hoops to avoid making a hefty donation or buying a license.

If you're aiming to be a corporate overlord, at least admit to it and don't play all your marketing on the open source aspect.

"Hey guys, what's up?" 😡😡😡

Why do so many people on YouTube begin their fucking videos with a pointless question noone is able to answer and which no one would acknowledge even if they did somehow manage to answer? What's up is an automatic thumbs down and fuck you.

So I have a pet peeve to talk about here, I'm excited for the Atari box as I have some inside information that is officially confirmed about it (unfortunately am not allowed to talk about it :-C) and I see people out there saying it is "an underpowered Linux steam machine)...

How the fuck are people coming to this conclusion when the specs, OS or anything technical about it haven't even been released yet?!

Why must people immediately assume that because it's not a standard windows PC it must be a piece of shit?

Boggles my mind that so many people can be so defensive and go on the offence without knowing anything.

Just so I can clarify, I'm a console gamer, Linux lover yet still develop for windows and the like so this isn't a biased rant and I know people will look at this, see the word Linux and go on the attack... So... Just... Chill?

Something which is becoming a big pet bug peeve of mine... Chat bots being classed as AI...

Seriously?? Gives a response of context 2 or 3 levels deep?

Saw a news bulletin of a guy being questioned on the guidelines of putting AI in an app which builds quiz questions from Wikipedia - look out world, the robots know a lot of history!

The Google engineers building proper AI would be wetting themselves...

So this has been a pet peeve of mine since I started coding roughly 7-8 years ago, and I want to know if I'm alone on this.

When non programmers ask to, or do so without informing you, watch you work.

I cannot function whilst someone is watching me, it just doesn't work.

Pet peeve: the claim that static typing prevents errors.

Today I worked on a C# project that's a mess of nulls, side-effects, inferences, and race conditions. Then I went back to a JS project that's twice the size but written in a clean, well-tested, FP style and currently has fewer than 10 issues logged.

Look, I get that there are upsides to static typing, and I'm open to introducing typescript or flow for our JS code.

I just can't stand the faux-concern from the static typing dingleberries when they are the ones who produce these horrendous lumps of unmaintainable shit, and the JS/Python/Ruby/etc people are over here quietly reinventing functional programming and code modularity.

My pet peeve with LinkedIn: messages from recruiters on another continent offering me a job because I live in the same country as the job offer. Just because the Netherlands are a small country doesn't mean I will take any job anywhere in the country! Open Google Maps and check the driving distance, then you'll find that the job is 150km away from where I live, and it would take me 90 minutes to get there in good conditions, not to mention rush-hour traffic! Thanks but no thanks!

Pet peeve #3984 - when managers / salespeople anyone else pretends it's just appropriate to "add up" years of experience.

"I'm sure we can solve this, the team have over 100 years of coding experience between them"

...yeah, that's not how experience works, doofus. Unless you'd really trust 20 people with 6 month's experience over a single person with 10 year's experience.

I learned how to use the MacOS and Linux command lines first, so it's been a constant pet peeve of mine that I had to use dir for the purpose of ls on Windows. Today I tried to make ls an alias for dir, but noooooo... Windows uses the doskey command instead. I can't even make alias a macro for doskey either so I'm stuck at least with that shortcut that only Windows uses. #FuckWindows

I still can't understand why people put 2 stickers of the same thing/product (devRant) on a single item (laptop, etc.).

"I would say my biggest pet peeve related to the industry would be people focusing on technology instead of design, standards instead of users, and validation rather than innovation. Web standards and best practices are noble goals, but all too often in our community people forget they are a means to an end, not the end itself." - Jeff Croft

My pet peeve is IMs that start wtth hi or GM. Please people. Can you write what you want from me. Why don't you ask about how my dog is doing as well?

Sry, music / perfectpitch rant, !dev

My biggest (non-dev) pet peeve out there right now is this wave of "oohh look I did a transcription" Youtube videos that comes out whenever someone famous for complex harmony (such as Collier) releases a song. I mean that'd be fantastic, but they're OBVIOUSLY NEARLY ALL DAMN WRONG IN SO MANY PLACES.

More frustrating is that no-one seems to actually realise, the video skyrockets with wowed casual viewers amazed they're looking at sheet music that looks vaguely convincing, and everyone treats them as some musical genius. Dahh. Wake up people.

(Exceptions made for June Lee. He's awesome.)

biggest pet peeve is when a client renames things, wtf is a 'hover and click"

Canadian PetPeeve #1337 when frameworks/languages use American spelling, goddamn it's colour not color

My biggest pet peeve is everyone who says Java is shit when they've likely never used it before.

Also...are you trying to start a war :P?

A really big pet peeve of mine is that we don't get teached coding in schools. Right now I'm about to finish middle school and wander of to high school. I am really surprised that my country's school system doesn't teach coding! The only way to get teached coding in our schools is in 11th grade by picking exact sciences and going to learn IT. It's really stupid when coding should start in the start of high school, in, at least, 9th grade. Really pissed me of...

Pet peeve: when I search for Java related jobs and got JavaScript jobs in return

My biggest pet peeve is that too many developers don't realize that "regex != regular expressions", probably because of bad naming and bad documentation. It's easy to assume that they're the same, but most regex syntaxes today are actually at least context-free grammars, since they support backreferences.

Whoever worked on the speak-to-chat feature for Sony XM4 headphones deserves to have a bunch of angry orangutans pull on their nipples for 1 minute.

Why the fuck do they get activated out of the blue when I'm simply talking? It feels like I'm under the water.

And the damn feature can't be turned off permanently. You can go into the app to turn it off, but it'll get activated again. You can use the two finger gesture on the sensor to toggle it off but it will still come back. It never stays off.

These are amazing headphones, but this is my biggest pet peeve. Almost ruined them for me.

Pet peeve? People in the toilet stall talking to someone on their cell while they are downloading yesterday's meals to the repository. Really, it can wait until you've done your business.

I think my biggest pet peeve right now is production being different from our test environments.

That moment you need to change something near the top of a docker file and now it needs to completely rebuild

Is anybody else bothered by Slack? The way they handle account management and channels bothers me. It solved a problem that didn't exist, and now it has become this ecosystem so many people/organizations are over reliant on.

I feel like AIM had better features in the early 00's.

Pet peeve: unnecessary null checks.

My pet peeve (for non-anglicanized saxons, essentially something that bothers you a lot): when people get really upset or freaked out for you in order to outdo your own sense of shock or anger at the circumstance you just told them about.

Today i had a rock hit my windshield. Later i told my brother about it and he was EXTRAORDINARILY concerned, and although its just him looking out for me, i cant help but feel noided by it.

Am i an asshole for this or do you guys feel this way sometimes?

My workflow pet peeve is the length of time my PRs get merged into master
I have to create new features, but sometimes I have to work off current HEAD, which is technically old since I need stuff off a new branch.

Ideally we merge into master, then create a new branch off that. It's nothing major and there's loads of ways to get around it, but I'm used to the flow!

Power BI: wonderful tool, pretty graphics, and can do a lot of powerful stuff.

But it’s also quite frustrating when you want to do advanced things, as it’s such a closed platform.

* No way to run powerquery scripts in a command line
* Unit testing is a major pain, and doesn’t really test all the data munging capabilities
* The various layers (offline/online, visualisation, DAX, Powerquery, Dataset, Dataflow) are a bit too seamless: locating where an issue is happening when debugging can be pain, especially as filtering works differently in Query Editing mode than Query Visualisation mode.

And my number 1 pet peeve:
* No version control

It’s seriously disconcerting to go back to a no version control system, especially as you need to modify “live code” sometimes in order to debug a visual.

At best, I’ve been looking into extracting the code from the file, and then checking that into git, but it’s still a one-way street that means a lot of copying and pasting back into the program in order to roll back, and makes forking quite difficult.

It’s rewarding to work with the system, but these frustrations can really get to me sometimes

So let's do a "community building" exercise.

What was your biggest tech pet peeve?

I'll start:
I hate it when people (especially teachers) give us a printout with a link to a website (like a good docs link) without shorting it.

I mean, we have to type out that 100+ character string of random numbers and letters. Then you make a mistake and have to retype it. (I.k,. First world problems)

Let's here yours. It can be about employers, teachers, or anyone else you can think of.