I agree! It wouldn't be my stack personally, but that's kind of the point.
I focus on the languages I'm good at because I want to build fast and efficiently. We get caught up in scalability and fancy new features way too early.
That being said I love learning new stacks, and then get over excited and think I'm going to rewrite my old projects in this sexy new framework. I spend a week doing that and then realize "what am I doing?", this is going to take twice as long because I'm still learning it and the end result is going to be even messier. π
Definitely my favorite approach. I take on a large-ish project and every time I get stuck I research it and learn something new. Been doing that for years.
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.
I agree! It wouldn't be my stack personally, but that's kind of the point.
I focus on the languages I'm good at because I want to build fast and efficiently. We get caught up in scalability and fancy new features way too early.
That being said I love learning new stacks, and then get over excited and think I'm going to rewrite my old projects in this sexy new framework. I spend a week doing that and then realize "what am I doing?", this is going to take twice as long because I'm still learning it and the end result is going to be even messier. π
I do the same thing with learning new frameworks! Itβs a good approach to learn, but the result is code I always feel like throwing away π
Definitely my favorite approach. I take on a large-ish project and every time I get stuck I research it and learn something new. Been doing that for years.