I’ve had more than one person I work with take screenshots of their desktop, paste them into a word document, then attach the word document to an email to get me to help them with their problem. This has the same energy.
I’ve always wished Markdown was better supported in email. I work with external companies’ APIs a lot where email is the medium, and typically I use a Windows monospace font for code snippets (I’m on macOS but there are a handful of monospaced fonts that work on both).
It’s very clunky, and I wish the backtick notation would work out of the box. Whoever decided HTML in email was the way to go should be shot.
Used to work in a place where, to get credentials, a used would need to simple send an email from their mail servers and would be enough… One of them would write a fancy Please add used x letter, print it, have the Head of Whatever sign it, scan it onto non-OCR pdf, then mail it… joy.
I’ve had more than one person I work with take screenshots of their desktop, paste them into a word document, then attach the word document to an email to get me to help them with their problem. This has the same energy.
I’ve always wished Markdown was better supported in email. I work with external companies’ APIs a lot where email is the medium, and typically I use a Windows monospace font for code snippets (I’m on macOS but there are a handful of monospaced fonts that work on both).
It’s very clunky, and I wish the backtick notation would work out of the box. Whoever decided HTML in email was the way to go should be shot.
I completely agree, and in general working with email programmatically sucks. MIME is a mimefield.
Used to work in a place where, to get credentials, a used would need to simple send an email from their mail servers and would be enough… One of them would write a fancy Please add used x letter, print it, have the Head of Whatever sign it, scan it onto non-OCR pdf, then mail it… joy.