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
43944 readers
644 users here now
A loosely moderated place to ask open-ended questions
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
Read the damn code
So many problems can be solved by just reading the code. A corollary to this: make sure the code you write is readable.
Another correlary: learn lots of languages, even if you’ll never use them. I never want to fall into a codebase that I’ve never even learned the paradigms. One procedural, one functional, one OOP, one interpreted, one compiled, one byte code compiled, one or two command line scripts, regex, all the structured data text languages: XML, CSV, JSON, YAML, TOML, … A JavaScript framework. HTML. A relational database, a non relational db. REST.
Should be enough to get started lol. But you learn something from each, about code architecture at least.
Always learn the languages preferred directory and repo layout structure, never invent your own.