![](https://programming.dev/pictrs/image/f1cc9607-837e-47cd-a2ab-8a7f16d321da.jpeg)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
Did it work? How do you know that? A consumer of your package sends a int when your package expects a string.
What now?
The reason you “git blame”
Did it work? How do you know that? A consumer of your package sends a int when your package expects a string.
What now?
Use whatever is most enjoyable to you. You’ll be most productive working in a framework you like as opposed to one people online convinced you was “right”.
Take an hour or two with each. Use whatever is clicking best with you.
All these options are perfectly sound.
BUILD SOMETHING.
Learning concepts without the ability to apply them are essentially useless.
Get your hands dirty and build something that would be valuable to you and solve a problem for yourself.
Don’t get hung up on doing it “right”. Focus on making it work. Don’t worry about how it’ll work for a million users. Right now your focus is on making it work for one user.
As you go you’ll hit walls. Research how to get past them and keep going. Again, you’re going to make mistakes. DO NOT GET HUNG UP ON THIS.
Making mistakes is part of the journey. Even the best software engineers in the world rarely get things right their first try. It’s part of the process.
I’m really good at searching Google. I’m a “prompt engineer” too