Ok, so it isn’t really week 11. I thought, however, that I need to get back to the weekly postings. The past few months have been exceptionally busy with my work, and unfortunately the thing that got cut out in the long weeks were my extra projects, like my coding. The good news is that while my coding in iOS has gone down, my experience with software development has gone up!
I have been working away on my application for the past couple weeks, and by working I mean banging my head against a keyboard hoping it would do what I would need it to do. Fortunately, today I had another breakthrough, albeit a minor one.
The best analogy I could use to explain it to people is that I am a child, learning a new language, and always learning more about the world, but I lack the necessary words to communicate. The analogy stands in that I am constantly understanding how the code should work, but having the right code is another matter. Oh well, here’s what I’ve been doing.
The title is slightly misleading, since it assumes I’ve finished the book, but I haven’t. Instead of finishing the book, I’ve made the decision to dive head first into development. I won’t leave the book behind entirely, since there is a chapter on SQLite that I think will help me, but I feel I have enough of a groundwork that I can working on my own things, and I’ll learn as I go. Beyond feeling like I have enough of a foundation, the other reason is that I needed to get serious and set a series deadline for myself.
Last weekend I was in Chicago, and since most of the rest of my week is busy working overtime, I didn’t get much done. However, in the time I did have I kept going back to the XML parser because most of what I want to do involves working with XML feeds that are already available.
Another week, another 2 chapters done!
The challenge now is applying what I learned. Programming is as much about doing as it is learning. So far, I’ve become an expert at copying text out of a book, but it is actually very helpful because you learn structure. This week was exciting because I started coding new animations. In previous chapters, I have had the chance to use pre-existing animations to remove, or move rows, but now I’m actually modifying objects to animate them. It reminds me why I wanted to start doing this in the first place; to make games
It was a shortened work week thanks to something called “Family Day,” which is a holiday giving another day to spend with the family. I spent it going through another 4 chapters. Sadly, since last Monday I haven’t had a chance to go back to the lessons. Work has been especially busy, so I have put my studies on hold.
Coincidentally enough, the work I finished was learning how to save the contents of my application, so that I could retrieve the list at a later time. Fitting.
No waxing philosophically this week; This week is all about what I learned.
Every year, millions of people set New Year’s resolutions for themselves, and shortly after completely giving up on them. My most recent learning initiative resembles one of those resolutions, and has encountered the same challenges that everyone trying to alter their lifestyle or improve their situation faces. I’ve had the long work hours, reduced sleep, home repairs, the list goes on and on. Justifying these daily requirements with my latest personal interest is something I have to do every day.
So, why bother?
A long time ago, I coded a simple, and it was fun. I stopped because it got hard and I didn’t like having to sift through lots of code to fix errors.
Now, after many years, I’m back to coding, and I realize I like the challenge and the puzzle. I have also learned that the hard things are the best things, and so now I start the learning process, but at least I appreciate it now.
Once a week I’ll check in with my progress.