Sure, leans a bit classical and not the least bit "wanky" (at least IMHO)
> but the term was around long before it.
Wanky? DJ? Classical? Term Of His Natural Life? .. Regardless of the specific etymological chronology you're thinking of, I feel there are non-wanky examples in the broad tent of "classical".
I came here to write a similar comment. To me it read more like: When driving, do you prefer to a) turn left, b) turn right, c) press the gas pedal, d) press the brake pedal, or e) execute a sequence of actions that get you safely to your destination? There's a good idea here, perhaps, but it's obscured by very weak questions.
Starting around the mid 2010s I think, I started seeing needless use of "Design Patterns" all over the place (mostly by CS graduates). Factories, adapters, observers in places where it was just plain overkill and needless extra lines of useless code.
I started referring to it as cargo-cult programming.
Personally after being allowed to be fully remote I found this to be a weird experience. I wasn't totally sure where to live. I no longer needed to be in the bay area, I could go back "home". Idk what I wanted to do, got pressure from family about what I "should" do. I didn't really know what I wanted in a place to live. And I think for most people for most of their lives no one had this freedom to just live anywhere. There isn't a lot of good advice.
I don't get all the hate for Teams. I work fully-remote on a medium sized team. We use Teams for one-one calls, team calls, presentations, screen-sharing, calls to external numbers and I've never had any problems. I run it on a Windows desktop and an Android phone. I've never had performance problems or crashes on either.
Some of the file-sharing/explorer stuff is a bit janky in terms of UI but I don't really use that. TBH it's all fairly seamless IMO.
About once every two to three days if I resize a teams window that has ongoing video call, it'll crash so hard that I have undock and redock my laptop to get my monitors to unfreeze.
Have you tried copy/pasting from teams to another application, or especially code snippets? If you're lucky you can copy what you highlight, otherwise you copy the entire text of the current message with timestamp and all.
Code snippets are a pain to get right. The tilde key is the shortcut to get monospace fonts or code blocks, and it feels like I roll the die everytime I try to convert text to a code block.
Teleconferencing is also a major pain, where devices are not remembered for some reason. It's mostly ok, but every now and then it forgets my mic. This might have been fixed recently since it doesn't happen as often but it still happens.
Not to mention the hangs that comes up when switching between conversations.
> Have you tried copy/pasting from teams to another application, or especially code snippets?
Pasting in teams is hilarious. I think when I last tried they were using contenteditable, as formatting that should not have carried over did so, along with the indentation going haywire on paste.
> The tilde key is the shortcut to get monospace fonts or code blocks, and it feels like I roll the die everytime I try to convert text to a code block.
Backticks are used for formatting code in Teams, not tildes. Surround in-line text in single backticks, or place three backticks on a new line to start a code block.
I regularly lose the ability to unmute or turn off my camera during Teams calls. In that case I have to hang up and rejoin to speak. It also regularly doesn't deliver notifications. At this point I just can't rely on it's primary functions.
In one company, I had strictly no problems with Teams, was working correctly, quality was great, with another, it was plagued with bugs. I suspect that it's highly configurable and highly dependent of windows policies that are set +network.
At client, windows itself was unusable and people were blaming Microsoft... No it's the package team who did a shit job.
Austraian/New Zealander detected lol