Obviously, the paralysis and anxiety is something to look at.
Also: I wouldn't so recommend Vue. Focus on rendering boring, server-rendered HTML first. Add vue later.
I'm a big fan of rails for the unique focus on developer happiness and velocity it places on the stack. There are similar stacks "technically" but it's the difference between a modern OS and windows 3.1. To which I say, the stack DOES matter; they are not interchangeable because they each have different philosophies and priorities. If rails wasn't free I'd paid for it.
But it depends on your priorities and what you're trying to do. I want to be effective at, and enjoy building, web applications. But if you're trying to just learn X technology or language vs building an MVP, those priorities can shape what you work with.
My best advice is aim to succeed even if you fail. Do things the RIGHT way, use the tools / technologies you've always wanted to. Even if the project goes nowhere, at least you got to play with something, and be professional about doing it.
Lastly, think of small problems you COULD solve, or explore. then build off those.
Also: I wouldn't so recommend Vue. Focus on rendering boring, server-rendered HTML first. Add vue later.
I'm a big fan of rails for the unique focus on developer happiness and velocity it places on the stack. There are similar stacks "technically" but it's the difference between a modern OS and windows 3.1. To which I say, the stack DOES matter; they are not interchangeable because they each have different philosophies and priorities. If rails wasn't free I'd paid for it.
But it depends on your priorities and what you're trying to do. I want to be effective at, and enjoy building, web applications. But if you're trying to just learn X technology or language vs building an MVP, those priorities can shape what you work with.
My best advice is aim to succeed even if you fail. Do things the RIGHT way, use the tools / technologies you've always wanted to. Even if the project goes nowhere, at least you got to play with something, and be professional about doing it.
Lastly, think of small problems you COULD solve, or explore. then build off those.