this post was submitted on 07 Jul 2025
1493 points (99.1% liked)

Microblog Memes

10827 readers
1105 users here now

A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.

Created as an evolution of White People Twitter and other tweet-capture subreddits.

RULES:

  1. Your post must be a screen capture of a microblog-type post that includes the UI of the site it came from, preferably also including the avatar and username of the original poster. Including relevant comments made to the original post is encouraged.
  2. Your post, included comments, or your title/comment should include some kind of commentary or remark on the subject of the screen capture. Your title must include at least one word relevant to your post.
  3. You are encouraged to provide a link back to the source of your screen capture in the body of your post.
  4. Current politics and news are allowed, but discouraged. There MUST be some kind of human commentary/reaction included (either by the original poster or you). Just news articles or headlines will be deleted.
  5. Doctored posts/images and AI are allowed, but discouraged. You MUST indicate this in your post (even if you didn't originally know). If an image is found to be fabricated or edited in any way and it is not properly labeled, it will be deleted.
  6. Absolutely no NSFL content.
  7. Be nice. Don't take anything personally. Take political debates to the appropriate communities. Take personal disagreements & arguments to private messages.
  8. No advertising, brand promotion, or guerrilla marketing.

RELATED COMMUNITIES:

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] chimp@sh.itjust.works 13 points 7 months ago

Currently in the industry - it's exactly this. It's a communication issue between the programming team and other teams, where designers freely speak for design, artists freely speak for art, etc. but it's much harder for programmers to speak for implementation since it's usually in reference to somebody else's work, and when designers get offended or defensive or dismissive of the non-designer requesting 256 be changed to 255, then it stops being worth it.

For example, we made an absolutely mint UI backend, it was data driven with editors so anyone could whip up a new UI for the next feature without needing programmers. The design team were like "damn, I hear how complicated this thing was to build, so let's make the programmers lives easier by not using it and only asking for simple bespoke stuff". Telling them "the investment has already been paid for so please use it" was tantamount to telling them how to do their job while being ungrateful they had considered us, furthering the communication breakdown.

Yes I'm bitter and tired. It's easier to use a short for 256 instead of arguing to have my opinion considered