this post was submitted on 03 Dec 2025
192 points (98.5% liked)

196

4939 readers
1011 users here now

Community Rules

You must post before you leave

Be nice. Assume others have good intent (within reason).

Block or ignore posts, comments, and users that irritate you in some way rather than engaging. Report if they are actually breaking community rules.

Use content warnings and/or mark as NSFW when appropriate. Most posts with content warnings likely need to be marked NSFW.

Most 196 posts are memes, shitposts, cute images, or even just recent things that happened, etc. There is no real theme, but try to avoid posts that are very inflammatory, offensive, very low quality, or very "off topic".

Bigotry is not allowed, this includes (but is not limited to): Homophobia, Transphobia, Racism, Sexism, Abelism, Classism, or discrimination based on things like Ethnicity, Nationality, Language, or Religion.

Avoid shilling for corporations, posting advertisements, or promoting exploitation of workers.

Proselytization, support, or defense of authoritarianism is not welcome. This includes but is not limited to: imperialism, nationalism, genocide denial, ethnic or racial supremacy, fascism, Nazism, Marxism-Leninism, Maoism, etc.

Avoid AI generated content.

Avoid misinformation.

Avoid incomprehensible posts.

No threats or personal attacks.

No spam.

Moderator Guidelines

Moderator Guidelines

  • Don’t be mean to users. Be gentle or neutral.
  • Most moderator actions which have a modlog message should include your username.
  • When in doubt about whether or not a user is problematic, send them a DM.
  • Don’t waste time debating/arguing with problematic users.
  • Assume the best, but don’t tolerate sealioning/just asking questions/concern trolling.
  • Ask another mod to take over cases you struggle with, if you get tired, or when things get personal.
  • Ask the other mods for advice when things get complicated.
  • Share everything you do in the mod matrix, both so several mods aren't unknowingly handling the same issues, but also so you can receive feedback on what you intend to do.
  • Don't rush mod actions. If a case doesn't need to be handled right away, consider taking a short break before getting to it. This is to say, cool down and make room for feedback.
  • Don’t perform too much moderation in the comments, except if you want a verdict to be public or to ask people to dial a convo down/stop. Single comment warnings are okay.
  • Send users concise DMs about verdicts about them, such as bans etc, except in cases where it is clear we don’t want them at all, such as obvious transphobes. No need to notify someone they haven’t been banned of course.
  • Explain to a user why their behavior is problematic and how it is distressing others rather than engage with whatever they are saying. Ask them to avoid this in the future and send them packing if they do not comply.
  • First warn users, then temp ban them, then finally perma ban them when they break the rules or act inappropriately. Skip steps if necessary.
  • Use neutral statements like “this statement can be considered transphobic” rather than “you are being transphobic”.
  • No large decisions or actions without community input (polls or meta posts f.ex.).
  • Large internal decisions (such as ousting a mod) might require a vote, needing more than 50% of the votes to pass. Also consider asking the community for feedback.
  • Remember you are a voluntary moderator. You don’t get paid. Take a break when you need one. Perhaps ask another moderator to step in if necessary.

founded 10 months ago
MODERATORS
 
top 17 comments
sorted by: hot top controversial new old
[–] GraniteM@lemmy.world 2 points 1 day ago
[–] user224@lemmy.sdf.org 23 points 2 days ago* (last edited 2 days ago) (2 children)
[–] Brahvim@lemmy.kde.social 2 points 1 day ago (2 children)

Doing algorithms in year 2 of college and I use goto fearlessly. We have TOO MANY cults and stigmas in programming these days...!

Aaaaand I love writing C. ...Though it can be pretty painful.

[–] NigelFrobisher@aussie.zone 1 points 1 day ago

Goto Considered Awesome

[–] Buddahriffic@lemmy.world 1 points 1 day ago

Goto was risky and it was one big name on some BBS back in the day that pushed for a "never use goto" dogma, rather than figuring out rules for when it should or shouldn't be used. And a whole bunch of people just jumped on that bandwagon, but not everyone.

The main rule for using goto that I'm aware of is to never use it to jump into the middle of a scope. Jumping around in the same scope is fine, jumping out of a scope is fine (assuming you handle unwinding the stack correctly, which I think the C compiler tries to do, at least, but there are other constructs that can save/restore stack contexts to do the same thing as a goto but safer).

Though programming language contstructs can also help eliminate the cases where using goto gives better code. Breaking out of nested loops is the main good case for goto that I'm aware of. Without a goto, you need to set up an exit flag and check it before starting a new iteration for each loop level you want to escape from. Unless your language supports labelled breaks/continues, in which case the compiler knows which loop the break/continue refers to instead of needing to always assume it means the deepest level.

C/C++ is my favourite language, but I've used an enhanced C++ with labeled loops and it was nice.

[–] Cevilia@lemmy.blahaj.zone 8 points 2 days ago (2 children)

What I assume is a picture isn't loading for me

[–] Klear@quokk.au 9 points 2 days ago* (last edited 2 days ago)

You can't C it?

[–] user224@lemmy.sdf.org 4 points 2 days ago (1 children)
[–] Cevilia@lemmy.blahaj.zone 4 points 2 days ago (1 children)

Yep, that works!

Though I can't read C so I'm just gonna assume it's done wrong or something :P

[–] chaos@beehaw.org 6 points 1 day ago

explaining the jokeThe top one is fairly normal, the bottom one is the same program, still in C, but redone to be as BASIC-like as possible, complete with line number labels and using goto instead of any of the normal control flow structures like while and for loops.

>HELLO, MY NAME IS DR. SBAITSO. TELL ME ABOUT YOUR PROBLEMS.

[–] Thorry@feddit.org 10 points 2 days ago

Having your home built mini computer sputter and blink for 20 mins, only for the correct amount of memory free to come up as BASIC is loaded. Chefs kiss

[–] addie@feddit.uk 6 points 2 days ago (1 children)

Speaking as someone who does their development in Vim (with YouCompleteMe / NerdTree / CTags installed), that's pretty much exactly what it looks like when I'm coding to this day. OP recognises elegance when they see it.

A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away.

-- Antoine de Saint-Exupery

[–] Cevilia@lemmy.blahaj.zone 3 points 2 days ago

I barely even qualify as a dabbling coder, I write terrible Python code and even worse bash scripts, which I think barely counts as dabbling? But anyway, I do it in Kate because it highlights my syntax but otherwise just lets me work.

[–] DmMacniel@feddit.org 7 points 2 days ago (2 children)

Eeeh I liked TurboVision (e.g. the DOS IDEs by Borland) more than the UI Qbasic had.

[–] zod000@lemmy.dbzer0.com 1 points 1 day ago

The Turbo programs (C, Pascal, Assembler, etc) were all great. QBasic was nothing compared to them, but it was included for free with Dos, so I can give it credit there at least.

[–] SpaceNoodle@lemmy.world 4 points 2 days ago

Yeah but QB was free