133
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 Jul 2023
133 points (97.2% liked)
Asklemmy
43760 readers
1212 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
If you're a developer, read the source code. People will tell you how they remember things working, or how they think they should work. The code is what it is.
I don't know if that's obvious for people entering this profession but mind that you don't read code like a book. Check how the functions you use are implemented. What's being called from where (call stack helps in the debugger). How are experience programmers managing their code etc. It's a good skill to learn how to navigate other people code and quickly find the parts that matter
Exactly! Always push for code pointers for everything people tell you about the codebase. Even if the code has a bug and isn't working as intended, it's so important to know the actual truth if what's happening.