Meme Monday!
Today's cover image comes from last week's thread.
DEV is an inclusive space! Humor in poor taste will be downvoted by mods.
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (74)
π€£π€£π€£
π€£π€£π€£π€£π€£
Are you copy pasting these emojis on all Monday meme pages? π
Needs to be asked π
I had to π«
That's exactly how I imagine US work culture :)
US work culture would probably be having the laptop on hand typing one handedly while at the altar between βDo you take ... as your wife/husbandβΒ and βYes, I doβ π
That'd be true
When I was still in a BPO company, I remember my leave request for my wedding day got declined. I tried to ask to have at least just a few days, but nope. TLDR, they require me to call operations to notify them of my absence.
π€£π€£π€£π€£π€£
frrrr
this is fantastic
Reduced from 4 steps to 2 ...
π€£π€£π€£π€£π€£
If you always go to the throne with your cell phone then leave a like.
I donβt get it.
switch caseis just a crap version ofmatchthough πI hate waiting in long lines.
Switch-case has fallthrough, which can be a useful feature. Well it's useful in system languages anyway where an assembly jump table can be generated (i.e. where performance matters).
Switch-case is also my goto for designing state engines.
Ah, but goto is considered harmful π
(sorry)
Computed goto has notable, proven performance benefits in VM engines on modern hardware. Actually less harmful than previously thought. Although we probably should still not run out and start plastering our code with goto statements.
ππ
π€£π€£π€£π€£π€£
Not if you are using Redux or Reducers! :P
π€£π€£π€£π€£π€£
Me, last week π€‘
Source
π€£π€£π€£π€£π€£
Can't it be both?
π€£π€£π€£π€£π€£
I've read the introductory paragraph on wikipedia so I am now qualified to give my expert opinion on the topic and if you disagree your'e wrong even if you've spent 20 years researching the topic.
I am exceptionally frustrated because I know 0 about AI. 0 as in how to make something useful. :(
π€£π€£π€£π€£π€£
I have never used Teams? Is it that bad?
Given that "Slack for Work" is a litteral contradiction in terms...
From the worst to the best:
Zoom - Slack - Teams - Meet - Discord
As far as I can tell checking them across multiple devices (win, mac, android, ios).
Considering UI / UX I find them all quite awful, but Discord and Slack are the worst for me. Those just randomly scatter all kinds of buttons, message windows, text boxes all over the place without any coherence. π©
Try to see it this way:
Zoom
It does few things and none of them are good enough IMHO.
For some reasons the web client refused to work last time I tried (the link to open in web client consistently downloaded the Zoom client App every time I hit it).
I don't know why but I always end up with three windows of zoom:
and if I'm about to see those three and seeing them all properly, I almost need all screen space available on my two 2560x1440 monitors to fit everything in.
Even in recurrent meetings, chat messages are not stored anywhere they just live as long as the meeting is alive, which is annoying (e.g. if you cannot attend one time on a recurrent meeting you lost not just the spoken conversation but all related-messages as well, which could give you context to ask later on if necessary).
For the features it offers, I'd rather use Telegram App, in which you can video-call and screen share as well, everything on a well-designed interface (similar to that of MS Teams).
G Meet
Maybe the simpler of all, you have Google Chat on one side, and Google Meet on the other one, which is just for that, to run meetings. Multi-screen-sharing is present.
It lacks basic features though, like sharing images or files through the chat included in Meet, plus the text message max-chars is lower enough to be annoying (e.g. you can't share a piece of code, it will break at its max-chars and you'll need to check where it broke, to select and paste the next chunk).
The overall experience is fast, straight to the point and with few features, which can be good to certain niches (online psychology, advocacy/law-related stuff, tax consultants and so on, basically whether you will send files and big texts through email anyway or you don't need to send files or big texts at all).
Slack
It's complicated, more than it needs to be. Threads get lost in side-conversations and I had issues with one thing or another each time I used it. It may be me, but... can't provide further details, I get frustrated twice, won't get frustrated with it again unless it's extremely necessary π
MS Teams
In MS Teams, the default is 1-to-1 conversations (from now on DM, as acronym of Direct Messages), while you can create groups, which get mixed in between DMs in the list, then you have "teams", which are groups, but not groups like the ones we speak about before, just another kind of groups.
When you do a meeting, it creates yet another group chat with that meeting's members, that also gets lost between DMs in the same chats list.
Screen sharing feature is the most basic. Just one individual can share screen at a time.
It has (had?) a nice feature which is the ability to control other's computer, but as far as I can tell it woks only if both devices are windows, and even in this situation I couldn't get it to work in my personal computer when calling a friend, I searched it, still I don't know when is this feature available and for who (license) and what restrictions it has (OS? App client?).
Discord
Teams and Slack use the approach of "this is a real time chat tool" and we've built everything at the top of that (that's what the UX tells us, not necessarily the approach they used to build the tool from the ground up).
In Discord, on the other side, the approach is "those are servers to which people can connect to speak and chat" and we've built everything else at the top of that.
If you've used any service of this kind (e.g. TeamSpeak) you'll easily grasp the gist of it and see it as a natural evolution that lasted too long to materialize, if you didn't, you'll need to get used to it.
You can call/chat with individuals (DMs), though the default workaround relies on having "Servers" which contain "Channels", that's effectively a way of dealing with groups and scopes.
You can create one server for each purpose (client, project, department...).
Maybe your company is not so big and you prefer to have a single server with different channels on it, completely fine! roles and permissions allow adding specific users to each channel, and inside each channel you can find a voice chat (real time, quick to join/leave) with a text chat attached to it.
Multi-screen sharing is also available -that is, I can see your screen and you can see mine, we can also watch other's screens, your screen space is the limit! π - which is quite useful in certain situations; brainstormings, peer programming, trying to gather information around a given tech with the team, checking UX diagrams and journeys etc.
You can also share files of any kind (as far as I know) and huge texts, no issues on that.
That's my vague analysis through what I experienced with those tools, it may be similar or way different to yours, share them as well! π
Too long didn't read, on the other hand your comment looks like it could be a fine article :)
It could but I'd need to elaborate more, analyze things further.... and it's something I don't really want to do right now π
No pressure.
But also it's good sometimes to stop overthinking thing.
You don't need to write the ultimate absolutely objective comparaison between all chart clients.
You can copy paste your text with a small introduction
I could but... I won't π
if you want to make it a post you can copy-paste it, mention me somewhere if you feel like and call it a day π
Teams is awful. It is a huge resource hog that takes at least two minutes to start at boot and it is impossible to find anything in it (bad UI/UX). Probably one of the worst team chat/collaboration programs ever created. It takes almost 15 seconds to display a basic chat window when someone messages anyone else.
The only good thing about Teams is that it integrates seamlessly into ADFS enterprise environments running Exchange and Outlook for scheduling meetings. When creating a meeting in Outlook, clicking a single button converts the meeting into a Teams meeting and joining the meeting in Teams from Outlook is also a matter of clicking a single button. But that's it for positives and probably the only reason that managers like Teams (i.e. easy meeting scheduling via Outlook). Everything else about Teams is terrible.