If you are wanting to pick up Vue, choose node.js and start with the basic tutorial on setting up your project and project organization. Then do a tutorial on state management in Vue. At that point you should just get started on a project and stop doing tutorials until you run into something you don't understand. To get moving I like to pick a piece of functionality. In this case, login could be a good place to start. Whether you want to use third party auth or roll your own, it is a good place to start. Get login and state management working because once you have that running you can start implementing other functionality pretty fast.
The key is to pick a piece of functionality that does two things, one: simple but once completed is a component you'll need for your project, two: at the end of implementing that functionality there is something that works which you can build off. That's why I suggest doing those two tutorials and then starting with login and state management, it will help you move forward. Don't get ahead of yourself, pick small components of functionality and just start knocking them out. Don't think about the millions of options.
On your tech stack, pick whatever is most common for your stack, don't try to be complex when all you need is to get started. For example, node.js, postgresql or mongodb, Vue. That will give you the widest set of tutorials and help online and in the end it is extremely capable platform for nearly anything you want to build. And all of those are marketable skills.
Thanks Davis! That seems look a good start. Sometimes I just need someone to tell me what to do I feel to put things into perspective. I'll start with the basic Node/Vue tutorials and focus on getting something deployed, implementing login and then some basic api integration and move from there.
I guess I can always refactor the code when I start learning about more complicated stuff.
Awesome. And yep, that's the idea, just get it moving and as you go through the project and learn more you'll find things you can (or want to) refactor to make better. But at least you moved forward.
You aren't alone, we all need a little nudge in a specific direction sometimes. :)
the problem i have with this approach is it's reinventing the wheel.
continuous integration, testing infra, rolling upgrades, deployment, logging, analytics on that logging, should all get solved problems I get out of the box in 2019
not surprised on the downvotes. Many devs will choose reinventing the wheel over using existing solutions. Their competitors will be on to release 7.9 while they're still trying to figure out how to ship version 0.2 without losing all the data from 0.1
Batteries included systems are a force multiplier. Engineers like writing code more than shipping. Go to any game jam and watch the teams using Unreal or Unity. Their progress dwarfs those that start from zero. While the teams using the full engines are adding game play features the teams starting from scratch are trying to figure out how to load 3D data or debug why their graphics aren't on the screen yet.
It's no different with apps. A good app framework or web app framework gets you to a working state ready to just work on what makes your app different. Starting from scratch means you're still trying to figure out how to get your DB backed up while the other devs are adding features.
OP isn't trying to win a competition, it sounds like they're trying to learn to be a better developer. I know way too many devs (and have been one myself) who can use a batteries-included system until something goes wrong, but because they have no idea how such a system is constructed they can't debug it, or they don't understand why something isn't performing well.
It goes with the adage that every developer should implement a linked list exactly once—you should use the standard library from then on, but if you don't understand what's going on under the hood, you'll misuse it eventually.
> Go to any game jam and watch the teams using Unreal or Unity. Their progress dwarfs those that start from zero.
Pretty sure I would come out on top with my CoD:MW download then.
The point of game jam is having fun while challenging yourself doing what you like. If you can't animate a sprite or draw a wire mesh without game libs then by all means use Unity, Unreal or even Scratch. Nobody's judging. Just don't read too much into it.
The key is to pick a piece of functionality that does two things, one: simple but once completed is a component you'll need for your project, two: at the end of implementing that functionality there is something that works which you can build off. That's why I suggest doing those two tutorials and then starting with login and state management, it will help you move forward. Don't get ahead of yourself, pick small components of functionality and just start knocking them out. Don't think about the millions of options.
On your tech stack, pick whatever is most common for your stack, don't try to be complex when all you need is to get started. For example, node.js, postgresql or mongodb, Vue. That will give you the widest set of tutorials and help online and in the end it is extremely capable platform for nearly anything you want to build. And all of those are marketable skills.
edit: fixed a word