An hour… well maybe you can fix a quick bug or two. But you won’t get anything hard done.
I work full time at a startup, and I have a 6 week old daughter at home, and I'm working solo on a proof-of-concept on nights and weekends. Since I've got my hands full with the baby at home, I've learned to be very efficient with my time. One decision that made things a lot easier was deciding to go with node.js. Since the entire app is written in JavaScript, I can quickly test out ideas on my phone or tablet browser using JSFiddle, and integrate it later when I have a laptop handy. Sometimes I only have an hour of uninterrupted time, but that's usually enough to write a function or two.
That approach might be fine for small projects/webapps, but I stuggle to see that approach working for anything more complex/hard. Sometimes the only way to make effective progress is a full day of uninterrupted progress where you can hold the relevent parts of the system in your head at the same time...
Sometimes you need several weeks of working on the problem in this way to make progress! (e.g. machine learning improvements, distributed system design).
I work full time at a startup, and I have a 6 week old daughter at home, and I'm working solo on a proof-of-concept on nights and weekends. Since I've got my hands full with the baby at home, I've learned to be very efficient with my time. One decision that made things a lot easier was deciding to go with node.js. Since the entire app is written in JavaScript, I can quickly test out ideas on my phone or tablet browser using JSFiddle, and integrate it later when I have a laptop handy. Sometimes I only have an hour of uninterrupted time, but that's usually enough to write a function or two.