Them: Root, you take too long to get tickets out. You only have a few simple ones. You really need to rebuild your reputation.

Also them: Hey, could you revisit this ticket? Could you help ____ with this other ticket? Hey Root, how do you do this? Root, someone had a suggestion on one of your tickets; could you implement that by EoD? Hey Root, i didn't read your ticket notes; how do you test it? Hey, could you revisit this ticket for the fourth time and remove some whitespace? Hey Root, someone has non-blocking code review comments you need to address before we can release the ticket. Hey Root, we want to expand that ticket scope by 5-6 times; still labeled a trivial feature though.

Also them: Super easy ticket for you. Make sure you talk with teams A, B, C, D, E and get their input on the ticket, talk with ____ and ____ and ____ about it, find a solution that makes them all happy and solves the problem too, then be sure to demo it with everyone afterward. Super easy; shouldn't take you more than a couple days. Oh, and half of them are on vacation.

Also them: Hey, that high-priority ticket you finished months ago that we ignored? Yeah, you need to rewrite it by tomorrow. Also, you need to demo it with our guy in India, who's also on vacation. Yes, tomorrow is the last day. (The next day:) You rewrote it, but weren't able to schedule the demo? Now you've missed the release! It's even later! This reflects very poorly on you.

Also them: Perfect is the enemy of good; be more like the seniors who release partially-broken code quickly.

Also them: Here's an non-trivial extreme edgecase you might not have covered. Oh, it would have taken too much time and that's why you didn't do it? Jeez, how can you release such incomplete code?

Also them: Yeah, that ticket sat in code review for five months because we didn't know it was high-priority, despite you telling us. It's still kinda your fault, though.

Also them: You need to analyze traffic data to find patterns and figure out why this problem is happening. I know you pushed the fix for it 8 months ago, and I said it was really solid, but the code is too complex so I won't release it. Yeah I know it's just a debounce with status polling and retrying. Too complex for me to understand. Figure out what the problem is, see if another company has this same problem, and how they fixed it.

-------------

Yep. I'm so terrible for not getting these tickets out, like wow. Worst dev ever. Much shame.

LF work, PST.

Remembering a university lecture

Prof: "What are some other downsides of using polling instead of interrupts?"

Student: "The process has to wait until it gets polled."

Prof: "Exactly. When you click Ctrl+W, you want that tab to be closed immediately. You don't want the system to wait a few seconds for those keys to get polled and risk your mom looking at that tab."

Managed a 97% reduction in bandwidth usage for our internal host monitoring tool by converting the dashboard from using AJAX polling to websocket events.

Completely unnecessary but wanted an excuse to do some development with websockets. (:

So I'm making a music game, and I've been struggling to fend off this large sound latency issue. There is like a ~80ms of latency, which is a total deal-breaker for music games.
So I've been polling everything using a profiler, but nothing came up... Until just now, I realized:
IS IT MY F*<KING KEYBOARD THAT IS LAGGING?

I pulled my iPhone out, opened the Notes app, and recorded the screen as I smacked the keyboard.

Whaddaya know, exactly after 5 frames (in 60fps) of the sound of me punching the keyboard, the letter shows up.

Now I need to take *this* lag into account :facepalm:

Dev: Sends weekly update email on Friday, as drudgingly required by management, outlining that stress level is high recently in the past two weeks and constant polling for feedback and updates is stressing him out, needs to slow down the pace

Management: (ON A FUCKING SATURDAY): "Received your email @fullStackChris"

WOW! THANKS FOR THAT INSIGHTFUL UPDATE! I BET YOU DID! I HAVE NO DOUBT GOOGLE'S SMTP SERVERS ARE RUNNING PROPERLY. AND AFTER READING IT, YOU HAVE THE AUDACITY TO @ ME IN A WHATSAPP MESSAGE. ON A FUCKING SATURDAY. I DON'T WANT TO HEAR FROM YOU, I DON'T WANT TO THINK ABOUT THE COMPANY OR ITS TASKS UNTIL MONDAY. PLEASE STOP.

I mean they must be fucking with me at this point, right guys? Maybe I should start writing stuff like "I need more tasks and more messages throughout the day" then I would probably receive less, I mean wtf is actually going on.

We find our hero, fullstackclown🤡, again harrowed by idiotic management.

Our backdrop and set: A Google calendar appointment was booked between the managers and fullstackclown. fullstackclown had created an all-day appointment for today which reads: "fullstackclown on site".

With the scene set, let us begin our tale..........

Manager: Are you going to be on site today?

fullstackclown🤡: Do you see the appointment I booked on our calendar stating that indeed I will be on site today?

Manager: ...

fullstackclown🤡: you are an absolute idiot

Manager: ...

I literally don't know what to do anymore. I mean it's RIGHT THERE IN YOUR CALENDAR. HOW MUCH MORE CLEAR DO YOU WANT IT TO BE?! DO YOU WANT A TWILIO APP THAT SENDS YOU A PRERECORDED VOICE MESSAGE IN MY VOICE, CONFIRMING MY CALENDAR APPOINTMENTS?!

What type of mindset causes this type of behavior of double or triple checking things as simple as a calendar booking? Honestly shows a complete breakdown of normal mental functioning in my opinion.

Apparently, mouse polling rate is limited to 130 Hz for Bluetooth mouse.

BUT WHY 🖱️📶🐁

because bluetooth isn't designed for ultra-high-gaming-inputs. and you don't need higher polling rates unless you're a very competetive gamer. in which case you're using wired, anyway, because latency.