How To Program: Introduction …
Monday, February 22nd, 2010I started my blog to capture solutions to development problems I encountered so I could get to them from anywhere, and to share them with others. I wanted a place to voice some opinions on software development, trumpet things I was doing, and to provide a place for people to learn. There have been a few posts in most all of the categories except maybe learning, until now.
Recently on twitter a person that I admire (Simon Harris) asked a question along the lines of “Who was taught programming in a way that didn’t start with writing code?” and I replied that I had. I remember my Year 10 teacher Mr Frank Van-Den-Boom (forgive me if that isn’t the right spelling) started teaching us not by writing code but logic and analysis, then code.
This is the start of a series of blog posts is about how to program, and how to be a programmer. It will rarely touch on programming code - but don’t let that turn you off. There will be code but first there will be more important things which I hope you will grasp and take on board to assist you in becoming a programmer; or maybe if you are a working programmer it may assist you in seeing things differently. Either way, I hope you follow this series and send me feedback.
I have received a lot of spam lately so if you want to email me comments you need to use my email and not this blog. The address is james underscore ladd at hotmail dot com and I’d be eager to get your comments.
Next instalment: Requirements
