Lately I've been thinking a lot about coding practices and coding style. I have a lot of personal opinions on this type of stuff, but I've never been really gung-ho on forcing or sharing my opinion (or preferences) on these types of things with others before. I've been more in the camp of "what works for me, works for me. And it doesn't have to work for anyone else".
But this mantra was put into my brain long before I was a published author (note I didn't say I was a GOOD published author, just a published one), and certainly long before I started bloging.
So while I think that I'll continue to honor my mantra in my real day-to-day developer life, around this blog I think I'm going to start sharing more of "how I *think* it should be". But it's important to me that everyone understands that just because it's my preference for doing something a certain way doesn't mean that I'm saying it HAS to be done my way.
I'm just going to talk about how I would do something, how I would approach something, or why I'm doing something the way I'm doing it (which I try to do in my code examples around here already anyway).
Additionally, I have a number of friends who have expressed an interest in learning programming for one reason or another.
As such, I think I'm going to attempt to write from time to time about how I would go about getting started as a developer. What steps I would take, what things I think they should try to learn, and in what order I think they should approach the material.
I'm not sure how all of that will work out, but it's good to have an idea (share my brain) and a goal (help friends learn to program) and then just start working.
So hold on because here we go...(starting with some future posts of course!)



