this post was submitted on 24 May 2025
1480 points (98.9% liked)

Science Memes

20696 readers
1209 users here now

Welcome to c/science_memes @ Mander.xyz!

A place for majestic STEMLORD peacocking, as well as memes about the realities of working in a lab.



Meta Post Tags



Rules

  1. Don't throw mud. Behave like an intellectual and remember the human.
  2. Keep it rooted (on topic).
  3. No spam.
  4. Infographics welcome, get schooled.


If you are here asking: "Is this a science meme?"

Probably, yes. We use the Dawkins definition of meme: a replicating idea, not just an image macro with a fact on it. A good post here doesn't need to teach you something. It needs to make you ask something: who, what, where, when, and especially why or how.

Science isn't a filing cabinet of facts, it's a conversation. For example, a photo of an eel or other localized wildlife counts because most people never see one, and wonder is the first step of inquiry. A car meme counts if it makes you curious about what's under the bonnet. If you want to talk about something you noticed in the world, chances are someone else wants to talk about it too.

We moderate for vibe, not category. Pruning is light, especially where a post creates interesting discussion. Experimenting is encouraged, but keep it in good faith and never punch down.



Research Committee

Other Mander Communities

Science and Research

Biology and Life Sciences

Physical Sciences

Humanities and Social Sciences

Practical and Applied Sciences

Memes

Miscellaneous

founded 3 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Aux@feddit.uk 2 points 1 year ago (1 children)

What kind of code are you writing that your CPU goes to sleep? If you follow any good practices like TDD, atomic commits, etc, and your code base is larger than hello world, your PC will be running at its peak quite a lot.

Example: linting on every commit + TDD. You'll be making loads of commits every day, linting a decent code base will definitely push your CPU to 100% for a few seconds. Running tests, even with caches, will push CPU to 100% for a few minutes. Plus compilation for running the app, some apps take hours to compile.

In general, text editing is a small part of the developer workflow. Only junior devs spend a lot of time typing stuff.

[–] xthexder@l.sw0.com 0 points 1 year ago (1 children)

Anything that's per-commit is part of the "build" in my opinion.

But if you're running a language server and have stuff like format-on-save enabled, it's going to use a lot more power as you're coding.

But like you said, text editing is a small part of the workflow, and looking up docs and browsing code should barely require any CPU, a phone can do it with fractions of a Watt, and a PC should be underclocking when the CPU is underused.

[–] Aux@feddit.uk 1 points 1 year ago

What do you mean "build"? It's part of the development process.