this post was submitted on 05 Sep 2024
701 points (98.9% liked)

Science Memes

11068 readers
2792 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.



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.

This is a science community. We use the Dawkins definition of meme.



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 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Cold_Brew_Enema@lemmy.world 23 points 2 months ago (1 children)

That's how I feel during code review sometimes. Looking over someone's code who is clearly way more experienced than me is interesting

[–] Landless2029@lemmy.world 3 points 2 months ago (1 children)

Same. I've been on both ends though.

Where my peer is either above or below my skill level.

So low they can't read it. So high thier shit would be 3x longer than mine...

[–] Aurenkin@sh.itjust.works 3 points 2 months ago (1 children)

In a similar sense to another comment on here having a more junior person read your code can be quite valuable too. If they can't understand it, it could be a risk and it might be worth thinking about ways to simplify it. Not that it's always going to be possible but still helpful to know that it's a maintainability risk.

[–] Landless2029@lemmy.world 2 points 2 months ago

Yeah what I've done with a junior is basically read through the logic of my code to ensure I didn't miss any steps.