Live data from Hacker News

Ask HN: Haven't worked for a while, best guide/advice to start a hobby project?

news.ycombinator.com

101–110 of 147 posts

Re: Ask HN: Haven't worked for a while, best guide/advice to start a hobby project?

#105
Everyone starts with no knowledge.

A good developer is one who walked the road already.

Why not start as a junior in a real team, learn from better persons.

Learn the basics first ( eg.Clean Code).

Learn architecture after ( 4layer).

There will always be a nicer js stack, I have a lot of experience. But I also struggled how to set up the frontend stack upfront in Vue ( not single pages).

I would actually advice on . Net core, the documentation is great, visual studio community is great and a lot of work is done in c# + tutorials are widely available

Re: Ask HN: Haven't worked for a while, best guide/advice to start a hobby project?

#106
I wouldn’t try to Learn nuxt before Vue. Frontendmasters has a great variety of tutorials for Different js skill levels

But that aside, I would probably try to work through eloquentjs, the projects ramp up very quickly and are a great foundation

Re: Ask HN: Haven't worked for a while, best guide/advice to start a hobby project?

#107
The best advise I can give you is: "Do it with a friend"

It's the best formula to keep yourself accountable and keep going even in the less fun moment (because even in Greenfield hobby project there are shitty moment's)

If possible do it in pair programming, it's the best for sharing and learning from each other meanwhile

Re: Ask HN: Haven't worked for a while, best guide/advice to start a hobby project?

#108
You say you want to use python or nodejs, so just go with one of them and don't look back. It really doesn't matter what you choose, just start creating. Don't spend days upon days trying to predict issues that you might never ever have.

Re: Ask HN: Haven't worked for a while, best guide/advice to start a hobby project?

#109
My personal advise: don’t waste time dicking around with a tech stack. Just write the code for your application as directly as possible. Write what’s important first to make it work then incrementally add features.

A tech stack is like a cookbook. Commercial cooks don’t dick around with cookbooks because if they ever want to make money they must be able to ship a product fast and scale their effort across multiple orders simultaneously. Cookbooks are written for a home user to slowly slave over a single entree as a cooking passion. Likewise a tech stack is for a corporate developer who has more time to burn and would rather dicking around with configuring things than making tough product decisions.

Not investing in a tech stack will force you to question your basic assumptions of architecture so that you focus first on the areas most important to your application. That puts your product first. As the application grows refactor as necessary.

Re: Ask HN: Haven't worked for a while, best guide/advice to start a hobby project?

#110
Start with the smallest piece that gives you motivation, might not even need a backend component.

For example, a tiny widget that shows you an artist page or whatever, that can be embedded.

Then ship that, show it to HN and all around. This should boost your energy and motivation.

Tackle a slightly bigger project afterwards. Loop a few times and voila! You're over the hill.

Post reply on HN