When I was first learning Cocoa/CocoaTouch I found it hard to jump from the books I was studying to my own apps. Creating a TabBarViewController, fine. Retrieving location, simple. Creating views and sub-views, there are 100's of tutorials and books with step-by-step code examples. However, when it came time to bring all those pieces together into a real app there was (and still is) a huge gap in available resources.
App architecture, memory utilization, debugging/unit testing and code style are areas that I'd love to have Ash cover.
I agree more with Tip #2 then with #1, but both hold water. I have a 2 year old and I'm more motivated now then ever when it comes to building my side projects. However, I have ONE son and yes, he is a full-time job. Tip #2 is really important...build and blog, build again and blog, keep building and keep blogging.
I agree - I'm not going to argue that children aren't a lot of work or take a tremendous amount of (what used to be) free time. However, I've found that it really makes me evaluate what I do, put it into the perspective, and maintain focus through to the end. Obviously, I don't have as much time to dilly-dally as I used to, but I can still be very productive with the time I do have (rather - I take much more advantage of that time).
Totally. I'm about to add a newborn to a 2 year old. Getting up early is an unrealistic option because I'm already up early with the kids. Working on side projects after 9p works best for me. Kids are in bed at 7p or so, hang out with the wife for a couple hours and wind down, then start on some projects. I wonder if other fathers who work on side projects have similar schedules.
My schedule is similar, except our four year old is now totally in bed asleep around 8 - 8:30. Given that we wake up with the newborn around 4-6am that doesn't leave a big time window for getting sleep and hanging out with the wife and doing side projects.
Things will calm down in a few months I'm sure -- once the new one is sleeping through the night.
App architecture, memory utilization, debugging/unit testing and code style are areas that I'd love to have Ash cover.