96
SICP rule (files.catbox.moe)
top 4 comments
sorted by: hot top controversial new old
[-] Pencilnoob@lemmy.world 18 points 1 day ago* (last edited 1 day ago)

Ugh I love that book but also completely accurate.

It's an absolute trip that that SICP was used as an introductory text to computer science. What a bunch of absolute legends.

Fun fact, there's about 350 homework problems in the book, so if you do one a day you'll finish the book in a year. Trust me, it's absolutely worth it! After that year it felt like I truly understood all this programming stuff (and this was after a 4 year degree and working as a software engineer for 4 years). The difference before and after was like turning on a light switch in my brain. I improved 5x in that year alone.

It's hard though, don't be ashamed to look up other answers if you get stuck. There's dozens of blogs where people explain every single answer in detail. I had to look up at least 25% of them. Still worth it, best learning investment ever for my career. I seriously think if I'd not done that I'd have left the industry long ago.

Also don't forget to check out the lectures on YouTube. Although to be honest I've not finished them, video lectures bore me too much. They are still really cool to watch.

I still think back to how it felt doing that book and finishing it. I wish I could go back and do it again for the first time. Just so immensely satisfying and empowering. I've tried to find other books like it, nothing quite does the trick. Sigh.

[-] Ashelyn 15 points 1 day ago

Bootstrapping! Using your non-native compiler to compile a compiler written in the language your compiler parses!

[-] jabathekek@sopuli.xyz 4 points 1 day ago

Yo dawg! We heard you like compilers. So, we put a compiler in your compiler so you can compile while your compiling!

[-] Metostopholes@midwest.social 9 points 1 day ago
this post was submitted on 20 Feb 2025
96 points (100.0% liked)

196

2183 readers
1835 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 1 month ago
MODERATORS