This is a sign of growth and it’s a great and normal thing. The fact that you’ve made it this far means you’ve cleared the most difficult hurdle.
To help you power through this, I would recommend not focusing on a specific technology (i.e. TypeScript) and instead focus on building something interesting to you. In doing that, you’ll be pushing through challenges you’d never even encounter when trying to find tutorials and build other people’s examples. This, of course, assumes you aren’t working for a company already building a production app.
I’d also note that refactoring code to add new feature is learning. It’s an important part and you shouldn’t run from it. You should pat yourself on the back for every refactor and every new thing you learn 😀
Agree! In fact, in my opinion every feature you add should involve some amount of refactoring, or you’ve been doing to much (potentially wasteful) work prematurely.
Besides: continuous refactoring is one of those good old practices that are all too often forgotten these days. As I see it, the only way to write maintainable code is to constantly maintain it.
“Getting it right the first time“ rarely happens. And when it does, it only means that in three years it will be seen as “that scary legacy code” no one dares touch with a ten foot pole because they have no idea how it works.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a sign of growth and it’s a great and normal thing. The fact that you’ve made it this far means you’ve cleared the most difficult hurdle.
To help you power through this, I would recommend not focusing on a specific technology (i.e. TypeScript) and instead focus on building something interesting to you. In doing that, you’ll be pushing through challenges you’d never even encounter when trying to find tutorials and build other people’s examples. This, of course, assumes you aren’t working for a company already building a production app.
I’d also note that refactoring code to add new feature is learning. It’s an important part and you shouldn’t run from it. You should pat yourself on the back for every refactor and every new thing you learn 😀
Thanks alot, Justin! 😃😃
Agree! In fact, in my opinion every feature you add should involve some amount of refactoring, or you’ve been doing to much (potentially wasteful) work prematurely.
Besides: continuous refactoring is one of those good old practices that are all too often forgotten these days. As I see it, the only way to write maintainable code is to constantly maintain it.
“Getting it right the first time“ rarely happens. And when it does, it only means that in three years it will be seen as “that scary legacy code” no one dares touch with a ten foot pole because they have no idea how it works.