6 ms·

What would I ever do without my software engineering team collaboration tool that can't send a fucking code snippet without burning half the screen on whitespac

What would I ever do without my software engineering team collaboration tool that can't send a fucking code snippet without burning half the screen on whitespace and a 400px font size title lol

initplus 2y ago
And that’s the upgraded version. Previously it just… wasn’t possible at all?
- bornfreddy 2y ago
  We should not mock MS though. This is a really difficult feature to get it right the first time around. /s
phito 2y ago
My god yes. It's so, so bad...
daemonologist 2y ago
I've taken to sending code snippets as regular message text with the monospaced font, because the code snippets feature is so awkward and slow (and sometimes won't load for the recipient at all).
Phelinofist 2y ago
I mostly use "> " for this, but that might hit the message length restriction, then you are forced to use the snippet thing.
stefan_ 2y ago
My favorite Teams bug and it took me a moment to understand the stupidity of what was happening: you copy a message you have received from someone and send it back to them. It is invisible on their screen. You have dark mode so what you copied was white text, which ends up being white on their light mode Teams. Nowadays I just get irrationally angry at the utter imbecile that decided you want to copy an abbreviated date and the sender name whenever you copy a message.
- irusensei 2y ago
  Copy and paste retaining style is one of the most annoying things in normie computing. Just why? And on teams it basically infects any other text you right afterwards.
kyriakos 2y ago
Haha I've faced this issue for years but it seems like they fixed it. You now can also set the code highlighting option directly from the editor without going into options. Took them years unfortunately.
a_e_k 2y ago
I've often wondered about that. I feel like it says something about the development team behind Teams if either, (a) it doesn't bother them, or (b) they don't dog-food their own product this way. (Just give me fenced code blocks, please!)
marcosdumay 2y ago
I hope your code doesn't use colons anyway, :parameter for example is a forbidden word. Oh, and line breaks get replaced by something that breaks some editors¹, and quotes obviously get mangled. 1 - I mean, look at their name! Teams is right here!

What would I ever do without my software engineering team collaboration tool that can't send a fucking code snippet without burning half the screen on whitespace and a 400px font size title lol

initplus 2y ago

And that’s the upgraded version. Previously it just… wasn’t possible at all?

bornfreddy 2y ago
We should not mock MS though. This is a really difficult feature to get it right the first time around. /s

phito 2y ago

My god yes. It's so, so bad...

daemonologist 2y ago

I've taken to sending code snippets as regular message text with the monospaced font, because the code snippets feature is so awkward and slow (and sometimes won't load for the recipient at all).

Phelinofist 2y ago

I mostly use "> " for this, but that might hit the message length restriction, then you are forced to use the snippet thing.

stefan_ 2y ago

My favorite Teams bug and it took me a moment to understand the stupidity of what was happening: you copy a message you have received from someone and send it back to them. It is invisible on their screen. You have dark mode so what you copied was white text, which ends up being white on their light mode Teams. Nowadays I just get irrationally angry at the utter imbecile that decided you want to copy an abbreviated date and the sender name whenever you copy a message.

irusensei 2y ago
Copy and paste retaining style is one of the most annoying things in normie computing. Just why? And on teams it basically infects any other text you right afterwards.

kyriakos 2y ago

Haha I've faced this issue for years but it seems like they fixed it. You now can also set the code highlighting option directly from the editor without going into options. Took them years unfortunately.

a_e_k 2y ago

I've often wondered about that. I feel like it says something about the development team behind Teams if either, (a) it doesn't bother them, or (b) they don't dog-food their own product this way. (Just give me fenced code blocks, please!)

marcosdumay 2y ago

I hope your code doesn't use colons anyway, :parameter for example is a forbidden word. Oh, and line breaks get replaced by something that breaks some editors¹, and quotes obviously get mangled. 1 - I mean, look at their name! Teams is right here!