I think of it in terms of levels building on top of each other, or circles enveloping each other; also how I evaluate interviewees and new hires:
Finishes the task, but needs handholding
Finishes the task, figuring it out from docs, guides, and internet
Finishes the task, proactively trying to make sure it doesn’t return again as a bug or failing QA
Finishes the task, designing things in a way so that devs don’t need to put in extra effort in the future
In short, learning how to do something right, but also alternative strategies, how to pick the best option, and finally make sure you always end up with the right choice, or automatically do so, by design.
It’s at core a matter of experience, but taking on new opportunities and reading up helps to accelerate that.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
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
I think of it in terms of levels building on top of each other, or circles enveloping each other; also how I evaluate interviewees and new hires:
In short, learning how to do something right, but also alternative strategies, how to pick the best option, and finally make sure you always end up with the right choice, or automatically do so, by design.
It’s at core a matter of experience, but taking on new opportunities and reading up helps to accelerate that.