this post was submitted on 10 Feb 2024
1392 points (98.1% liked)
Microblog Memes
5863 readers
3851 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:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Idk as long as you can communicate exclusively in flow charts you can communicate with software engineers pretty efficiently
Let me share my point of view as a programmer: The average person has no clue how detailed a computer program needs to be. You may think, “this process has only three steps, yadda, flubber and diddly”, but when you sit down and try to program this, you start asking questions like “if the user removes the program during the yadda process, should we add zero flubberees into the diddlydoo and send it off or should we not send the diddlydoo, and should the user be notified? Or should we maybe try to reinstall the program and start again from the yadda? Does it make sense to keep the inputs from the flubber, or is this likely a new process that’s independent from the first attempt? Is it sensible to enter a non-integer number of flubberees? A negative number? No number at all? Do we need to tell other users that a user is concurrently doing this process?