A whole bunch of years ago I had to take a programming course as part of my degree program: C for Scientists and Engineers. I was intimidated at first. This was the late nineties. Computers were not as ubiquitous as they are today. I had touched computers a few times in my life before, but was hardly proficient with them. When my professor asked the class if there was anyone with no computer experience, I was the only one who raised a hand. He said not to worry about it - that he would guide those of us who are unfamiliar through it. I felt relieved.
I did my best to follow along and understand, but at the beginning of the semester I was so intimidated by taking a programming class, that in addition to my text book, I also bought C for Dummies, figuring it would be something I could relate to. It helped but it wasn't a life-saver.
I did better than I expected in the class. I still didn't know squat about computers but I kinda had a hang of this C-language-thing. Then, a couple years later, I was in a software store (fairly common things back then seeing as the majority of software at that time was sold in boxes with either CDs or floppy discs in them). A bright yellow box caught my eye. It was the C Programming Starter Kit. I looked at it. It was the same brand of compiler I had used in my programming class - Borland. I remember thinking it was kind of fun making my own programs. I thought it would be cool to be able to make them at home. Plus I was familiar with the compiler. So for thirty bucks I bought it.
The box contained two things: the installation CD, and a book - Sams Teach Yourself C in 24 Hours. That book was fucking awful. I would never recommend it to anyone. It was clearly concerned with making its time quota above anything else. It gave no in-depth information - just a brief description of the feature (structures, defines, etc.) a quick example, some exercises, then onto the next topic. ("Chop chop! 24 hours, remember?!")
Despite that book I really got into coding. When I had previously taken my programming class, we did not cover the entire book. I actually took it upon myself to pick up where we left off and finished it. I then started writing my own programs and enjoyed it a lot. I've been doing it on and off since then. As far as whether or not I'm any good - I don't know. Besides the one class, I'm largely self-taught with programming. Some things I know quite well. I know the C language well because it's the only language I code in. But real programmers know multiple languages.
But, it is what it is. I still enjoy it.
Because I code as a hobby instead of for a job, I'm not as advanced as real programmers. I like working on applications. I write little programs to take care of some calculations or data sorting for me. However, there's really no need for me to. For calculations and data I can use a spreadsheet. Or for just calculations, I can use any number of calculator apps.
That idea used to depress me a bit at first. Am I wasting my time? I had read on different coding forums that you shouldn't re-invent the wheel. But after thinking about it for a while, I decided "Fuck it." Just because others are advanced doesn't mean I should not develop. And maybe I'm curious as to how wheels are made, so I'd like to invent my own. I don't care if there's a thousand better versions of a program I'm working on. I get enjoyment out of working on it.
Oh, and here are a few programming books that I actually do like:
The C Programming Language - Not for beginners, but still a must-have. It's the book after all.
Deep C Secrets - Again, not for beginners, but easily the funniest programming book I've read.
C for Dummies - This one actually is for beginners
