this post was submitted on 17 Jan 2024
40 points (93.5% liked)
Programming
17492 readers
47 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You'll get faster over time, until reading code is faster than reading documentation, as code will always represent what's truly happening, while docs are frequently outdated.
If you're not that familiar with the language, it's likely you won't be contributing to the project. Open source projects usually to have quite limited resources, so they tend to optimize docs and dev UX for people who are likely to contribute.
You can still borrow and implement features developed by project x into project y , but I do understand the time limitation.
because I am more of a visual learner I wondered whether developers don't use diagrams and flow charts, or just don't include them in the docs.
Personally I will jot some loose notes down if I'm implementing something thats sufficiently difficult, but formalizing the design patterns/algorithms is very time consuming so I don't.