4 ms·
I had the same issue and here's what worked for me: Stop trying to force yourself to code at home. Look at it like music creation, spend your time trying to fi
by kayman 10y ago
I had the same issue and here's what worked for me:
Stop trying to force yourself to code at home.
Look at it like music creation, spend your time trying to find inspiration, problems to solve.
Don't follow major development rules like you do at work which are designed for coordination and management amongst groups.
Be okay with crappy incomplete code.
Feel free to abandon it and return to it later...months later.
As PG says...don't code. Hack. It's way more fun.
- khedoros1 10y agoThis is me. I specifically make the decision to get something working, but not worry about how, so much (essentially opposite to my attitude in a professional context). If it's a project that I stick with for a long time, it usually ends up rewritten a half-dozen times anyhow. Still, the code's usually not in a state that I'd want to brag about. Big parts that I don't care about at the moment will be stubbed out, to be filled in when I do care about them later. If it feels like work, that's because it's work (in some way or another). If you don't want it to feel like work, find something to do that doesn't feel that way.
- bbcbasic 10y agoI am reading a book about programming language design and I often feel like backburning it and hacking out a compiler and see what happens. I can already write parser so I just need to so something with the tree ... innit. :-)