A lot of this stuff is great for when you're churning through some new features or a project you are invested in. Say for instance you have to find an issue in a legacy code base that is incorrect business logic and now you have to reproduce it, grok through tons of code, make some updates, rinse and repeat for a day or more.
Just start? stop reading HN and go read the code.
Start small? Open up my editor?
Start sloppy? Dump some printlns?
Anyway, time to go read* through some old cold fusion code I've been ignoring all morning.
There is no magic to want to work which is why you are being paid to do it or there is some form of incentive. The only advice I'd give is pay attention when you drive under bridges and overpasses and remember you're only a few bad decisions away from meeting your new neighbors, drive home and remember you get paid to tinker on a computer, then get to tinkering.
Just start? stop reading HN and go read the code.
Start small? Open up my editor?
Start sloppy? Dump some printlns?
Anyway, time to go read* through some old cold fusion code I've been ignoring all morning.
There is no magic to want to work which is why you are being paid to do it or there is some form of incentive. The only advice I'd give is pay attention when you drive under bridges and overpasses and remember you're only a few bad decisions away from meeting your new neighbors, drive home and remember you get paid to tinker on a computer, then get to tinkering.