Security: "You need to download and install this RPM stat!"
Me: "Hmm… Seems like it's not available on the yum server"
Security: "No. It's on this file share"
Me: "Hmm... looks like that file share is on a network that the server you want me to update can't actually talk to
Security: "Just download it to your system and then push it up to the server"
Me: "Ok, so, we're considering this desktop system part of the trust-chain, then?"
Security: …
Me: "Ok, I'll get on it when I've got a spare few minutes to babysit the transfers.
(time passes)
Me: (having downloaded the RPM from their Windows-share and pushed it to the server, am now attempting to install it) "Um... Your RPM isn't signed and it doesn't have any accompanying SELinux policy-modules. If you want me to install it, I can, but it will require turning off some other security-controls that I'd highly advise against turning off"
Security: "Just do your best"
Me: "Ok. Bear in mind that I'm keeping this email thread in case something inevitably blows up because of this"
I love when we do our daily scrums and one of the PMs (we have three: one – who actually functions as the PM – employed by my company; one employed by the prime-contractor and one employed by the end-customer) decides to pull up the burn-down chart. Invariably, instead of the line sloping downwards, it's either flat or rising because they keep adding tasks to the active spring.
I mean, great that you're keeping us busy. And, I'm sorry that several of us are fast enough that we burn through our initial assignments, but if you're not going to task appropriately at the beginning of each sprint, it really doesn't make a ton of sense to keep looking at the burn-down chart, neh?
15 minutes allocated for a scrum. Since extending the meeting invite to include other groups' PMs, the meetings have never been less than twice that …and others have been trying to engage in on-the-phone spitballing/solutions-engineering.
What I love about being remote and/or being on a geographically-distributed team is when someone sets up a (usually) #MSTeams meeting and fails to ensure that the meeting has a dial-in number. It's like, "cool: I can hear the call and I can see the video presentation, but, since my laptop's microphone (and camera) is disabled, I can't actually provide spoken responses to questions directed at me".
Two meetings in a row where the call was set up with no dial-in.
Also, why the fuck does #Teams not offer the option to turn off the freaking gallery?? I so don't need to see the other people on the call if they ain't talking. And, if you must show call participants, how about showing only those that enabled sharing from their cameras. It provides zero value and sucks up useful screen realestate showing me participants' initials especially if they aren't talking.
Every time I use Teams, I'm reminded of why Microsoft is able to include it free with their O365 accounts.