4 ms·
Firstly. > 5. You also would like to ship it ASAP too. Take that away from your mindset immediately! You can't do anything ASAP. I am a firm dis-believer of
by no1youknowz 8y ago
Firstly.
> 5. You also would like to ship it ASAP too.
Take that away from your mindset immediately! You can't do anything ASAP. I am a firm dis-believer of, "I can build it in a weekend".
Take a bit of paper and actually map out the project. Break it down into small pieces. Now start to work on the first piece, then take a break if needed. When you start again, work on the next.
Doing things this way, gives you multiple benefits:
1) allows your brain to focus on the task at hand. Otherwise it starts to focus on the entire project and thats when you short-circuit.
2) gives you a sense of accomplishment and you see your project go from start to finish.
3) allows you to easily come back to the project if you decide to take a long break from it.
It's also important that if you see things that you want to change. STOP! Take out another piece of paper and write down things for version 2. Now carry on with the work.
It's also worth mentioning, perhaps to keep some kind of journal with notes. So you can tell yourself things to investigate should you come across them in dealing with a problem.
Once you have finished and shipped version 1. You can then decide if you want to start again or wait until other things happen. Such as a community forming, you get stars on github, do a show HN. Whatever the ultimate goal is for the project.
Or you can decide to write another side project.
Ultimately, it's your time. Learn to use it well.
Btw, this is coming from someone who has built 40 side projects that easily could be their own SaaS start-ups thus far.
- faitswulff 8y ago> You can't do anything ASAP. I am a firm dis-believer of, "I can build it in a weekend". I'm in that camp as well, so consider this an endorsement of your post. However, I do think you can ship in a weekend...but do you want to? I slapped together a quick web app for my own personal use a while ago, not knowing I would end up using it every day, and set myself up for some extremely painful refactors later on that were totally avoidable.
- budhajeewa 8y agoReally helpful thoughts. Just to clarify, I didn't mean ship in a weekend, when I said ASAP. Just that I'd like to ship it sooner than later. I specially liked the advice about not working on things you think you should change, and saving them for v2. That mindset will be really helpful avoiding over-engineering.
- Casman 8y agoGreat advice! Have found GitHub issues are a great way to take notes on coding projects. Can the setup Milestones for stuff your currently working on and further iterations!
- davelnewton 8y agoASAP doesn't mean "immediately", it means "as soon as possible". What's "possible" depends on what's being done and expectations. Managing expectations is key.
- vfulco2 8y agoThe meticulousness of this process was awesome.
- kyo3 8y agoThis is really great advice, I just started a project like this and there's a lot I need to go back and map-out. I feel better when I'm just coding, but I get that's part of the process, I just haven't seen anyone explaining it.