this post was submitted on 29 Sep 2024
72 points (97.4% liked)
Programming
17511 readers
169 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
It's a lot of work. I'm in a similar boat. I've been self teaching myself how to program in various languages and working as a Fullstack developer at a very small startup.
While I've learned alot, there's always more to learn and finding direction is a challenge you'll hit many times over if you stick with it.
Right now I'm reviewing various Open Source Projects I could contribute to as I know ultimately this will make me a much better developer. There are so many CLI and web development tools I use that I'd like to expand on but will require a marginal jump in my skills. Here are a few examples:
I also am slowly working out plans to learn enough about Rust and browsers to recreate the terminal based browser Links in Rust.
But these are all just me spitballing. In truth, my skills aren't quite there yet and the amount of time to get there for each one of these is a lot. So I have to choose wisely and dive in deep on the project's codebase, probably for at least a year or more to make headway. But this is the mindset I think might help you. Look into the software you use a lot or like the concept of. Figure out how you'd like to improve it or add to it. Reach out to the developers of said software however you can, either make your case for the improvements you want to make or just help out on something they want to do with the software. Learn, listen. Rinse and repeat.
Hope this helps a bit.