this post was submitted on 03 Jul 2023
24 points (96.2% liked)
Ask Experienced Devs
1231 readers
3 users here now
Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient
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
One thing i undervalued for most of my career was just reading code.
Get into the habit of digging into open source repos that catch your curiousity, and try to grok the way the project is layed out, what namespaces/files exist, what some of the core functions are, where the complexity is housed.
It’s all about getting exposure to patterns, especially if there aren’t other people to work with in your day to day.
i think it’s all good for growth, good or bad - learning to evaluate it can start any time. Even if you don’t know whether it’s good or bad, you’re learning to recognize patterns, evaluate quality and build up opinions. If it’s bad, why, what would you change? If you don’t know it’s bad, you’re just noting a new pattern to try/compare to the others.
You’ve got to develop your own opinions about things anyway, might as well get better at reading/evaluating code sooner than later