this post was submitted on 14 May 2024
154 points (99.4% liked)
Programming
17509 readers
8 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 [email protected]
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
This is always the question that trips me up.
I'm 5 years younger than OP. I work in a municipal transportation power system job (we maintain and control the grid for trains, trolleys, etc.). I'm sure I'm wasting all sorts of effort in my professional life. I have time. I got a lot out of learning Power Automate. However, if you ask me to pick one specific project, I get overwhelmed because I don't know what's reasonable.
I don't know enough to know if my ideas are achievable, or if I'd just be bashing my head against the wall. I don't know if they're laughably simple tasks, multimillion-dollar propositions, or Goldilocks ideas that would be perfect to learn a coding language.
List out some ideas you're thinking of. While it may not be obvious to you, someone who is seasoned (me or someone else) might notice at least a general theme or idea to point you in the right direction for where you should go and what you should learn, regardless of if the projects are reasonable.
Note - Most projects take teams to realize, so if your ideas are too large, they might not generally be feasible alone.
Feel free to comment some ideas
Achievable is subjective, and even if you progress a ways and learn something that makes you realize that that particular project can't be achieved how you envisioned it, you still have the knowledge to either a) figure out new ways to achieve the same effect, or b) take to a new project.
Knowledge builds on knowledge builds on knowledge. If factor in not starting a project is not knowing enough to know if it's achievable or not, you'll never actually get the necessary knowledge to figure that out. You can't know how to do something until you try to do it...fundamentally.