Live data from Hacker News

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

news.ycombinator.com

31–40 of 147 posts

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

#31
I would strongly advise that you pick a stack, and then build a library or repository that you can clone in order to easily make new projects and push them to Heroku.

You're probably going to think of dozens of things it would be neat to work on. If you have to spend a week each time you start a new project before you get to the interesting part, then you're much more likely to just give up. If you can have a new website online in 5 minutes with free hosting, https, user auth, a database, and a basic frontend, then you get to have fun doing the interesting parts.

I did this with my current stack of choice (.NET Core/VueJS), and left myself directions for getting a new project going: https://github.com/caseymarquis/QApp

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

#32
Help someone. Remove indecisiveness by putting into their hands what you'll use by following their need (and their lead!), that way you can structure your hobby time around building it for them, and not have to worry so much about tutorials and stacks, you'll have a goal.

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

#33
I suffered from the same paralysis when attempting to do my own projects, and it had less to do with the tech than it did the problem I wanted to solve.

Eventually, to get started, I settled on doing a small command line app in Python/Click. It was a utility I actually needed (even if someone else didn't really need it), and it's the kind of thing I could iterate on without too much trouble.

It's usually much easier to start small.

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

#34
I have a colleague like you. Your problem is this: you say you want to build something cool, but then you follow up with "but every tutorial I read..."

There is NO guide to building something new and cool. Yeah, you will build upon existing stuff, but you need to come up with your own plan and then research specifics to fill in the blanks. You may have to repeat work, so just accept that.

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

#35
I've been there before. After getting burnt out on my startup, I spent about half a year traveling and trying out other hobbies not doing any coding at all.

When I got back to it I felt a little bit lost as to what to do, but doing these things helped me get back into the habit:

- Find a good project-oriented book and just follow along. In my case this was "Elements of Computing Systems: Building a Modern Computer from First Principles", but according to your interests and skill-levels there's plenty of good project-oriented books out there. I think this is good to do in parallel with your own side projects, because it gives you structure that the writers gave some pedagogical thought towards, and will thus help you gain confidence by solving problems and building something substantial over several weeks or months. This confidence will then put you in a better headspace for your self-directed work.

Don't engage in the online tutorials, where the author maybe wrote in a couple hours over a weekend. Instead, find well-respected books and courses that the authors poured serious effort into and that people consistently cite as having been influential to them.

- Read and engage with activities besides programming. I think one problem beginning programmers have is that they get so obsessed with just consuming programming related content. While the concentrated education you'll get out of this is great, from my experience reading about programming and tech doesn't lead to interesting ideas about things to make. What I think does lead to interesting ideas is cultivating curiosity about the world, and feeding it through reading and exploring.

- Study good software. In most creative disciplines there's a huge emphasis on studying the works of the masters of the art. This is so students can 1) understand the discipline's history and 2) develop good taste. The creation of software, whether you view it from a coding angle or from a UI angle, is mostly a design discipline. So taste matters a lot. I recommend studying the history of computing and finding good old artifacts to study(history is good because the excitement the pioneers felt might rub off on you, and help you see the field from a fresh perspective). Any software that you personally enjoy using is worth studying like this, but I think paying attention to the classics helps too.

- Learn how to design. This might seem like a distraction, but improving your design skills even just a bit can really help with making your ideas more engaging. The design community also has a lot of practices and advice on how to come up with good ideas that are worth seeking out.

- Find creators whose work you enjoy, follow them, and study their work. The most creative and prolific people I know all have one or more creators who were massive inspirations for them, and that they obsessed over and often spent a ridiculous amount of time trying to emulate. Too much focus on the copying part can be a hindrance in the short term, but being sensitive to these chains of inspiration, and seeking out who inspired the people who inspired you, can lead you down interesting paths. Find networks of creatives locally, on Twitter, slack groups, wherever, and engage with them, and contextualize your work in their framework(whether it's startups, art, or anything).

- Read up on creativity! IMO while self-help and pop-psychology books/ can be counterproductive if you spend too much time in them, in small doses they can be useful for analyzing your habits and practices. I recommend reading visakanv's threads about these topics: https://www.notion.so/a-list-of-visakanv-s-threads-1a6ed25cf...

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

#36

Forget tech stacks. Just pick the simplest idea you can think of that you would actually use yourself , that seems to not be a complex software product. And do it! I can assure you that the simplest of products will not result in the simplest code / stack. It is important that you also personally want to use this thing, because when the going gets tough, you will stick with it.

Agreed. My personal recommendation is to not worry about which stack is good but getting really really good at any one of the stacks. Mastery counts a lot.

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

#37
Every cool thing that I've ever built has started with an idea becoming a basic ( and I mean really basic ) proof of concept... just enough to see all the concepts and moving parts working together... start there, forget about all the tech stacks and just sit down and code something in whatever language you're comfortable writing in... the rest will follow.

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

#39

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…

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

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

#40
You could plan some small steps if you’re feeling overwhelmed. After reading some of the other replies, I came up with a few steps, tailor as needed:

1. Write down your goals or ideas for features. If you want to learn a specific framework, write that down as a /constraint/

2. (Optional depending on your style and background) Write down 10 or so requirements, if it feels natural to do so

3. Draw some block diagrams and flow charts. Keep it simple and think about which major components you need

4. Now you can survey frameworks. If you had one in mind as a constraint, does it still make sense? Pick whatever frameworks, libraries and development tools you need to solve your problems. If you don’t know what you need for a component, write down TBD.

5. Find a peer, and justify 1-4 to them. You will likely find most of your decisions make sense, but now you’ll have confidence and maybe make a few changes.

6. Now you can set up your development environment. You might find a few pain points already here and make a few more changes to your plan.

Post reply on HN