1. Isabel

    Sarah, thank you so much for this article.

    It’s a little more complicated for families who like to eat and wear clean clothes. :) The “10 minutes here & 15 minutes there” have to be used for laundry, cooking, dishes, and cleaning. That leaves zero time.

    Realistically, I find that I can only level up if i allocate time from sleep, between 1am and breakfast, while everyone sleeps.

    It’s easier to do with babies who stay home all day, but this becomes harder and dangerous if you have teens with extra curricular activities who need lots of involvement and chauffeuring. Driving on no sleep is dangerous, and so is chopping vegetables.

    In then end, you just end up programming at a much slower pace than say a college-aged programmer. A college-aged programmer can make an app in a few nights, say 20 hours. A mom with 3 teens can take 1-2 months to fit in 20 hours of coding. At least that’s been my experience.


  2. Joan

    That happened to me last month during my talk in WordCamp Alicante.

    I went there with one of my sons (he’s 3). In the middle of the talk, he stood up from his seat and came up on the stage to tell me that he had to pee. Hilarious. The audience was quite amused, some of them even tweeted a pic :)

    No child care in that WordCamp, I finished my talk with my little assistant. XD


  3. Edward Alexander

    #1 best method hands down to optimize physical coding time: “Learning to code in my head…”.

    I personally write “rough” code in my head and do the possible user/environment problem scenarios debugging in my head too. Then jot down notes about possible problems if I mentally come across any. It’s not like you are going to be writing the exact code in your head, but it sure speeds up the process when you do find the time to actually write the code. ;)

    Overall this is the most important method that I have incorporated. It serves another very valuable purpose and that is there are always many different ways to do something with code. So working through all the different possible coding approaches in your head before actually writing any code will typically save you time when you do the actual code writing. ie you have worked out the best coding approach/method beforehand.

    Awesome Tip: “A solid dev. environment where you can walk up, crank an iteration, and walk away. (Like in the time it takes a kettle to boil)”

    To me this translates to creating automated systems and environments. It is well worth the time it takes to build automated systems when you are doing certain coding tasks over and over. It could be as simple as building a template to “plug data into” to API server automation. ;)


  4. Jeffrey

    This is very inspirational. Thank you so much Sarah.


Comments are closed.

%d bloggers like this: