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
-
If a teamviewer sessions counts as "screenshare", I've got a good one.
The company I'm working for also got an internal video player in the webfrontend of it's product. A customer called in, because the player "stays black", instead of playing his videos. It's a player for a media library of the customer, so it can be any content. A collegue did some trouble shooting, but since the customer was not very experienced in IT they arranged a teamviewer session. At the appointed time, my collegue called the customer and asked him to reproduce the issue, while watching via teamviewer.
When opening the media player, it stayed black indeed, so my collegue asked the customer to try another video. From my desk I heard my collegue say "Oh god, no" (phone muted) pretty loudy and he asked us to come to his place quickly. The customer decided, it would be a good idea to try the video player with gay porn. So we stood there around my collegues desk, watching a hairy man, getting his asshole licked by another an even hairier man for a few secs.
The customer stopped the playback, said "ok, maybe the other file was just broken.", thanked my collegue and the call was over.
We had a few similar cases.5 -
In the last project i worked in, the product owner wouldn't treat people as people but as resources.
The problem with that is you just look at people and their work in terms of a checklist and remain blind about real humans face.
She wouldn't understand the challenges of building something with an absolutely new stack which people needed to learn from scratch and put pieces together. She wouldn't be supportive of people trying out things and fail.
One fine day I told her that I was spending too much time on meetings and i should be excluding that time from available sprint timings.. she made me open my calendar in a screenshare session with all team members. Made me go through go through every meeting invite i had on calender and ordered which ones should i be attending from then and which ones i wont. That was insulting. It broke the trust.
I decided to not work with the project. Stopped putting my heart and soul into it and eventually got out of it in a month time.
Don't put your team into a position like this ever. You have to trust them with the problems they face and try to find a solution. Scrutinizing and micro management will always kill the team.1 -
procrastinating by getting drunk since 11:00 AM, and writing specs for my (hypothetical) language/os/platform.
feeling righteous retribution because the client made me be stressed for 3 hours due to an issue that THEY caused but for 3 hours the only info I had was "there's a critical blocker issue and we're convinced YOU caused it"
well... no... i did NOT cause the fact that you UPGRADED PHP DURING THE WEEKEND BEFORE MONDAY'S PRESENTATION TO CLIENT (while waiting for an urgent commit from me).
seriously.
also, germans. i've heard many times from other people that they're... basically racist towards us (slavic nations), thinking of us as untermensch, coal-miner peons, but I didn't realize their passive-aggressive covertly smug demanding attitude is due to this, I just assumed it's a reaction to me being incompetent.
so yesterday when we finished the call (in preparation for which I tried to switch to their "client demonstration" branch since that's where the error was, and I wanted a headstart on fixing it, ended up in a place that my today's whole-day task should be "rebuilding the DB into working condition", because there's about 10 "core" sql scripts in two different folders, which need to be run (in a very specific order, of course, which readme tells you, but what it tells you has been outdated at least for 3 months, of course), and
...THE MAIN CORE SCRIPT THAT IS THE FIRST TO RUN, THAT CREATES THE DB schema, HAS THREE SYNTAX-LEVEL typos which fail it mid-way...
...the joys of continuous deployment via scripts, I guess? I would love to challenge any person from them to screenshare to me, manual deployment of the current version from zero, and I would be willing to give the person 20% of my monthly salary if they would be able to do it within 20 minutes.
but... well...
the point is, i should be doing not entirely bullshit stuff.
but yesterday's 6 hours of being in "at full attention because it seems we fucked up" totally convinced me, that today I'm taking a break.
So I'm gonna go buy another 3 beers and continue writing the specs of my dream language/os/platform.19 -
Embarrassing screenshare story? Yeah, I've got couple of those.
- Showing one client a VSCode workspace of another client's. I was lucky they didn't escalate or anything.
- YouTube open in PIP mode and accidentally showing that to the higher-ups in company. What made it more embarrassing is that they informed me about it, I thought I was sharing a window not Entire screen.
- WhatsApp open in one window and I accidentally shared it on screen, thinking I wasn't sharing my screen, but I was, and everyone saw my texts with a girl I was "dating" at the time.
- Presenting my entire screen to a client and out of nowhere Epic Games pop up with a notification saying ""Your buddy sent you a message - Ready to start playing?". But that was 11pm so I got off easy.
- Opening sentry to show one thing to the client but they notice many new bugs and I got slammed by my boss for it.2 -
Me: *randomly streaming myself code just because*
Friend: "So what are you doing"
Me: "I'm trying to parse a file. The specs are here - oh"
Friend: "Oh?"
Me: "I set screenshare to vs code only, so you can't see it"
Friend: "It's alright, just pass me the link"
Me: "Well, this is vs code, so I might as well check if it can display websites"
Friend: "No way you'd need that,"
>browser
* simple browser
Friend: "Please no"
"Enter url here"
Friend: "Stop!"
*loads website*
Friend: *dies of bloat*
Me: "All hail the bloat"
Friend in heaven: "Stop, your bloat will drag me down to hell"
So yeah, bloat can be useful sometimes4 -
Everyone is hyped on Flutter so I got a new idea.
I'm so distasted of Discord's official mobile clients, and this popped off my head:
Why not we implement it on Flutter?
After all, Flutter has these all nice things, and its certainly better than React Native.
I've laid out some of the things that needs to be done and one thing I've noted and remembered was:
- AFAIR According to b1nzy, former Discord employee, you're gonna need to know the WebRTC packets for Screenshare.
- VC is gonna be easy, and its probably the thing I can support without being too hacky.
hmu if you're up, I'm gonna call it Fluttercord, it won't be big or anything - just a experiment I want to show to Discord since they seem to struggle with the mobile clients4 -
A junior Dev was assigned a particular task where he is expected to come up with the command to run inside the system. He came up with the commands. I being a senior Dev and who has access to run the command on the pod did it after verifying it. I ran the command with screen sharing it to the junior Dev for him to learn. Now manager asked him to document the steps. I found that the doc contains screenshots from our call. My screens exactly.
Now my question is, I'm feeling that he should have asked or informed before taking a screenshot of my screen? Is this feeling normal?6 -
Boss tells me: "It doesn't work. I tried yesterday." I screenshare with him. He performs the action. All works good. My migraine intensifies... -.-2
Top Tags
Weekly Rant
View