A few of Stux's !dev pet peeves

1) People that walk slow as fuck in the middle of a side walk. Like hurry uppppp. I've gotta get 0.5 miles in like 8 minutes and you blocking the walkway doesn't help.

2) People that don't understand how side walks work. Treat it like the fucking road. ⬇️⬆️ Is the pattern in which you should walk. It's not rocket science.

3) People that start walking up the bus steps as I'm clearly walking forward to get off. Ffs let me off and THEN get on you stupid bitch

4) people that bike or ride their skateboard/longboard around campus but are moving slower than I am while walking. If you're gonna do that hop the fuck off and carry the damn thing.

5) people that don't try to solve an issue with their code on their own BEFORE they call the professor over. (There goes the !dev lol)

6) people that act like their favorite musician or athelete or actor or anyone fucking famous they play kiss ass with can't be criticized. Just bc they're famous and/or good at what they do sure asf doesn't make them perfection and I retain the right to voice my opinion.

My name is Stuxnet and you're watching Disney Channel.

Oh, you're 87% Web Design, are you? Get the fuck outta here.
Literally one of my biggest pet peeves for CVs/resumes/company website templates

Pet peeves as a programmer and ex hobbyist hacker:

1. People who press F12, change a colour and consider themself a hacker or/and programmer.

2. People who pick up someone's phone, guess their passcode and post shit saying 'hacked' at the end.

These people can kindly fuck off to the hellish dimension they came 👌

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!)

A list of Stux's !dev pet peeves.

1) Slow walking (elderly or visibly injured dont count most of the time) people in busy grocery stores. Like please move. I've got shit to do.
2) Thot bots on Instagram.
3) people who leave 2 or 3 car links between them and the car in front of them at a stoplight. I'm not saying you need to be touching their vehicle, but move closer damn.
4) People that say shit like "if you believe x, then unfollow me." Grow up and get over yourself. People are allowed opinions you asshat.

My name is Stuxnet and thank you for attending my TED talk.

If you type capital letters by hitting the caps-lock key twice, you don't deserve to use computers.

Why do people say "Well, I don't know about that" to voice disagreement?

If you admit your own naivety on a subject compared to your peers, if you admit that you do not have the required knowledge to have formed an opinion, how can you disagree?

So it can either be expressed with genuine innocence, like 'Well, I don't know about that, tell me more!', which is never the case.

Or it means "Well I don't know anything about that... and I'm ashamed of the fact that I can't find any counter argument, so I refuse to trust your fucking expertise, shut the fuck up until I give you the right to voice your knowledge"

Which is a bit rude.

Now that we're on the topic of annoying expressions and platitudes...

"It's not rocket science" -- Rocket science, understanding how a rocket works, is surprisingly simple. You fill a cylinder with fuel and oxygen, add a pump or two, put some sparks underneath. Chemical reaction equals energy, direct energetic particles using a nozzle, Newton's first law does the rest. It's so simple that people don't actually study rocket science. They study aerospace engineering, or astrodynamics, which are difficult topics.

So if someone says "Devops is not rocket science", they're right, but for the wrong reason. It's actually harder than rocket science. Maybe easier than developing thermal protection system materials or solving n-body orbital problems with a slide ruler though.

"Great minds think alike" -- No, great minds actually think creatively and generate unique thoughts, if two minds think alike, the solution was just fucking obvious.

"Don't reinvent the wheel" -- First of all, pretty much nothing in code looks or even remotely functions like a simple wheel. Even metaphorically, all existing code equates to oval or square wheels. If you said "Hey, don't bother making better wheels, I like my ride to be bumpy because it stimulates my asshole", say no more, who am I to come between a product manager and their anal stimulation.

Anyway, those were four coworkers who I would've strangled with an Ethernet cable if it weren't for a certain pandemic and the risk of infection which comes with choke-coughing.

What are your linguistic pet peeves you get homicidal over?

Some more of Stux's !dev pet peeves

1) Teenagers who comment shit like "I'm from the wrong generation" or "today's music is trash. This is real music" on songs from like the 70s and 80s. Like shut the fuck up. You can like whatever music you want, but your taste in music doesn't make you unique, so just shut the fuck up and listen to the music. I was jamming out to 70s and 80s when I was 9, so you aren't the first to enjoy older music at a young age
2) "Old heads" who comment shit like "this isn't real *genre*" on a new song that isnt like the older version of that genre. News flash: music fucking evolves. Just because that country song doesn't have a twangy guitar in it, that doesn't mean the song ain't country. Just because the rap song ain't some deep ass poetic shit, it doesn't make it any less of a rap song.
3) People who edit their comments on YouTube to say shit like "wow thanks for all the likes, I wasn't expecting this." Wooptie fucking doo. Your comment got a few thousand likes. Fun fact: those likes are meaningless.
4) Humidity. Fuck that shit man.
5) General education classes. They're a fucking pain in the ass man. Like im 98% confident I don't need art history in the real world. Or mythology. "tHeY tEaCh YoU tO lEaRn." Teach me to learn in degree specific classes then. At least their content will be interesting to me.

My name is Stuxnet. Thanks for coming to my TED talk again.

One of my biggest pet peeves is when I see people say shit like "fix it now" when a bug pops up.

Like bitch go fix it since you're such a fucking intelligent individual. You can't? Well then, shut the fuck up and let them fix it. They're human too, ya know

Small pet peeves is when people **use** `formatting` on _sites_ they KNOW DONT SUPPORT IT.

- Favourite pastime while waiting for your code to compile
- Most heroic/ingenuous bug fix
- Hardest to track down bug
- Worst legacy code you wrote and left behind leaving a job
- Weirdest project
- Last side project you actually finished
- Explain your job like I'm five/the way you do it for non-tech people
- That time your past self (almost) got you in trouble
- Software pet peeves
- Story about how you freaked someone out
- Feature that most certainly was a bug once
- Post something for your favourite previous weekly tag!

One of my pet peeves is coming across a post on stackoverflow with an awesome answer and even a comment from the OP saying this is exactly what I needed but it's not marked as the answer. Really? It's longer to write the comment.

A new team member joined us today. After introduction, he grabbed a chair. F*** YOU, IT'S JUST YOUR FIRST DAY BUT YOU'D GRAB KATE'S CHAIR WHO JUST TOOK A COFFEE BREAK?! PET PEEVES I HATE CHAIR GRABBERS

One of my biggest pet peeves with C++ are the number of ways to do things that, I personally, don't think their should be. Is that int* really an int pointer? Or is it an int array? Int vector? I am really regretting the refactoring approach I took.

So the android app has been updated, i'd seen that the review was pretty favourable.
One of my biggest pet peeves is people rating an app low because they have no idea what has changed in the app or that they are complaining about inane stuff.
What annoys you folks about people who don't understand our work?

As we are all aware, no two programmers are identical with regard to personal preferences, pet peeves, coding style, indenting with spaces or tabs, etc.

Confession:
I have a somewhat strong fascination with SVG files/elements. Particularly icons, logos, illustrations, animations, etc. The main points of intrigue for me are the most obvious: lossless quality when scaling and usage versatility, however, it goes beyond simply appreciating the format and using it frequently. I will sit at my PC for a few hours sometimes, just "harvesting" SVG elements from websites that are rich with vector icons, et al. There is just something about SVG that gets my blood and creativity flowing. I have thousands of various SVG files from all over the web and I thoroughly enjoy using Figma to inspect and/or modify them, and to create my own designs, icons, mockups, etc.

Unrelated to SVG, but I also find myself formatting code by hand every now and then. Not like massive, obfuscated WordPress bundle/chunk files and whatnot, but just a smaller HTML page I'm working on, JSON export data, etc. I only do it until it becomes more consciously tedious, but up to that point, I find it quite therapeutic.

Question:
So, I'm just curious if there are others out there who have any similar interests, fascinations or urges, behaviours, etc.

*** NOTE: I am not a professional programmer/developer, as I do not do it for a living, but because it is my primary hobby and I am very passionate about it. So, for those who may be speculating on just what kind of a shitty abomination of a coworker I must be, fret not. Haha.

Also, if anyone happens to have knowledge of more "bare-bones" methods of scraping SVG elements from web pages, apps, etc. and feels inclined to share said knowledge, I would love to hear your thoughts about it. Thank you! :)

There are periods when my intolerance level is increased, my pet peeves are more present than they were. During this time every fucking thing pisses me off, especially noise. It's the bane of my focus and concentration. Got a couple of loud ass colleagues and let me tell you, I've killed them many times over in my head. Always going off topic and talking about random shit that doesn't even matter.

i can't explain why, but hearing the term 'zeroth' in english really fucks with my head.

like, yeah, i'm quite used to 0-based indexing in my line of work obviously. but stuffs[0] == "the first element of stuffs" and that's what I would say when communicating verbally to the person looking at the code with me.

but like, take a use case where you are actually referring to something that precedes the first in a series, such as the number of updates on an original thing. then zeroth is indeed an accurate description, but still just rings such discord in my ear upon hearing it.

kinda like they say about 'moist' describing anything but a cake.

Honestly my biggest rant in the past month hasn't been about code, It's about Windows 10 changing my desktop password to my Microsoft Account. I have certain security pet peeves and it just screams "telemetry"...