The Book I Plan to Read While My Computer Loads

My 2012 Macbook Pro is riding to its ends. Starting Photoshop has become a fifteen minute affair; Sketch, iMessenger, Spotify, and three chrome windows are all competing on my hard drive in a turtle’s race. The last CD I used in the ever-convenient disc drive was Logic Pro in 2014 as a six-disc set — and I’m convinced by computer’s internal fan was put under an unending anxiety that has only become more intense each time I start Adobe Cloud.

Recognizing the mundane hours I’ve spent at the mercy of the buffering wheel as a partial explanation for my own exhaustion, I’ve decided there are three approaches to tackle my tech problem: 1) Buy a new computer (most expensive option/not really in the budget as a grad student), 2) let the buffer rule my life, continuing on in my disgruntled state, or 3) make use of the time I spend waiting for my now-dated technology to slowly resolve itself.

As a designer I largely rely on my technology to be able to complete my work, so alternatives to this waiting time may seem sparse. But on the opposite end of my computer deficit, I have been auditing my packed schedule for more time to read. In a previous blog post about making more time to read in the morning, I sadly find that this allowance has become slimmer and less often. So in an effort to still read when I get the chance, I plan to read my first book during the time it takes my computer to load.

Strategically and somewhat ironically, I plan to read Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days.

The read, as I have been briefed on, describes the crucial framework of building and testing a prototype in a short period of time. Made aware of the Sprint process by my graduate program — and recommended to me countless times by my peers as I endure the journey of building an app — I understand the methodology to be a useful way of collaborating to design effective solutions in a short period of time so not to waste before delving into too much research or cash.

I look forward to better understanding the Sprint process to apply to my own work methodology and future product prototyping. I also look forward to the new laptop I will be purchasing in six months or so. Until then, I am complacent with utilizing my slow technology to my advantage of better educating myself.

I will note in following posts about my new learnings and varying level of patience I achieve by reading during these staggered periods of tech failure.