This is one of those boring general posts designed to introduce you to this
website, or "blog". Rather than read this, I hope you're just reading the
articles as I publish them. If you're really curious about me, and why I do
this site, and where I'm getting the content, you can read on.
I've been professionally programing for iOS for 9 months, and doing so as a
hobby for a little over 2 years. Before then I'd had years of experience doing
C programming for some interesting enterprise things. And even farther back I
dabbled with Python, Django, Perl, and a whole bunch of other things.
Now, what I've noticed is that while I work on various projects in iOS, I often
run into interesting problems; problems that do not seem to be well documented
online. I spend a lot of time reading Apple's documentation, and
also searching around on Stack Overflow. Sometimes I solve the
problems just by banging my head against things.
So to prevent me from forgetting the things I've learned, and to share with the
rest of the world, I decided to start documenting them. I'm treating this site
as an "engineering journal" and taking the time to document problems,
solutions, and other things I find interesting.
Posts will come in a few varieties:
- Guides/How-To's/Tutorials: These will talk about some facet of iOS
programming, with the goal of explaining the little details that are
actually really important.
- Quirks and Problems: This will be single entries describing a problem, and
how I solved it.
- Useful Stack Overflow Questions: Answers and questions that
I find as I dig through Stack Overflow. They'll have some context, and I
might take the time to string a few together to solve a problem. I imagine
I'll end up doing more than this, but that's the start.
In the end I hope to be a useful resource for people trying to solve problems
in their projects.
Oh, and there are no comments. I'm just not dealing with it. Questions? I'm on
twitter and app.net as _spr_. My email for this site is spr (at) iosdevelopmentjournal.com. Let me know if you've started some sort of
discussion on another site. I'd love to join in.
Engineering journals are something I found in some Electrical Engineering classes I took in college. The idea is that you document everything you do, so you have a record. This lets you find mistakes, refer back to how you fixed a problem before, and mainly be accountable for all the work you've done. Old-school programmers often kept them as well. It's not common now, but there are some good things that come of it. ↩︎