Live data from Hacker News

Finishing a side project

hugozap.com

61–70 of 154 posts

Re: Finishing a side project

#61

I am always motivated to start a side-project to generate some extra income, but then I decide my time is better spent studying for job interviews. Eventually, I get sick of leetcode and go back to working on my side projects. It's a vicious cycle.

I think awesome side projects are at least just as valuable as leetcode, and so you should do side projects exclusively unless you have an interview next week.

Re: Finishing a side project

#62
Just like when studying or doing homework getting started and setting yourself up is the hardest part. Keep your IDE and relevant tabs open, if you're on Linux set up a workspace for it and just push the rest aside. Once you start tackling some code you'll be in the zone and will probably have to test yourself away from it.

Re: Finishing a side project

#63
> having a "context" log, where you write the current progress, and what to do next

yup critical. I do this and even if it gives me a 10-minute head start at the beginning of a work session, that means way more successful work sessions in a crazy week

I've started splitting my high-level todo list (tradeoffs + optimization) from my 'stream' todo list (next 5 linear things) -- the latter is useful for context + obstacles.

Writing down obstacles + setbacks also helps here.

Re: Finishing a side project

#64

> having a "context" log, where you write the current progress, and what to do next yup critical. I do this and even if it gives me a 10-minute head start at the beginning of a work session, that means way more successful work sessions in a crazy week I've started splitting my high-level todo list (tradeoffs + optimization) from my 'stream' todo list (next 5 linear things) -- the latter is useful for context + obstac…

We are used to put what we have done in git messages. But for WIP commits, it makes sense to also put what to do next. This way git log is your journal.

Re: Finishing a side project

#66

> having a "context" log, where you write the current progress, and what to do next yup critical. I do this and even if it gives me a 10-minute head start at the beginning of a work session, that means way more successful work sessions in a crazy week I've started splitting my high-level todo list (tradeoffs + optimization) from my 'stream' todo list (next 5 linear things) -- the latter is useful for context + obstac…

We are used to put what we have done in git messages. But for WIP commits, it makes sense to also put what to do next. This way git log is your journal.

totally

I've had people get mad at me for 'nextup' comments in commits, but at minimum, given how central git is to our workflow, the commit is the right time to track work

Re: Finishing a side project

#67
One of my tricks is to relax into it. I'm just gonna write some code and get something (anything) done. If it's shit I can "git checkout -- ." and walk away. If I don't get it done it doesn't matter. I need to depressurize it so it feels different to normal work. If something fucks up in prod, do the minimum to fix it, schedule the refactor for "mañana".

Re: Finishing a side project

#68
Re not sure why, but switching location works: in brain, these things are interconnected and clustered together after some time. Therefore switching the location (and your system user) is a great way to immediately switch your brain to the right context. Great recommendations!

Re: Finishing a side project

#69
post #28
post #4

>Unexpected life events. Like a world-changing pandemic and riots? I'll be honest, it is getting hard to focus on building my cute little software bullshit project when a voice in the back of my head is telling me to spend my time prepping for social collapse.

So much more is going on. Sand storms so large they are blocking the sun in the US. Radiation forest fires in Russia. Ufo's existance were confirmed by US navy. Stock market crash / rapid recovery What's next...

Can you share the link on the navy bit?

Re: Finishing a side project

#70
post #52

If you need to go to a café and create a new user for each new side project, you’re not gonna work a lot. I understand needing separate contexts for separate projects but this seems like overkill. The context is in your mind, not your environment. I have my share of past and ongoing side projects, including hobby websites [1], funny tutorials [2], an ebook [2], coding references [4] and a CSS framework [5]. Like the…

I would argue that switching the location is by far the most impactful of all those recommendations, based on how brain is clustering data. It comes with a rather big overhead for sure, but that might as well pay off quite quickly.
Post reply on HN