Article section
Recent years, I've been writing some articles for mainly flipcode.com and gamedev.net, however, I will also host them here on my machine from now on to offer them to you directly without the need to browse another page, and also as a personal
reminder for me to what work I've done in the past. Not that it's too many to remember, just nice to have the collection :-)

Please, please, email me if you care about them. Feedback (good and bad) are always an inspiration and it's also fun to have some contact with my readers :-)


SQL in 60 Seconds   (featured at gamedev.net)
Quite obviously I was inspired musicly by the soundtrack to the movie gone in 60 seconds when I wrote this article, hence the name of course. It's a SQL beginner tutorial which takes you through the first steps of using a database. I will assume you are using Microsoft Access to create the database and run the queries, but you can of course create a database using any software you want and then just run the queries in the corresponding program. I have recieved quite a lot of feedback on this one. Keep it coming :-)

CVS Quick Start Guide   (featured at flipcode.com)
The second most popular artile is the one about using a version system to keep track of updates in your code base. This one is a really good read if you want to move from a single person developing team to multiple persons. CVS (Concurrent Version System) acts as a "smart ftp-server" and also logs messages to each change in each file currently uploaded in the system. Can effectivly be used as a backup solution if you're a lone coder.

My Coding Style   (featured at flipcode.com)
This one drawed most attention of all articles I've written. At least during the first month or so there was some heated discussions since I chosed to write about how to write code. Or how not to, but basicly I just wanted everyone to make up their own minds and also make up their own coding style, or adept to one that suited them best. I wrote about the importance of writing code in the same way throughout the deveopment team you're working in. But also when you write for yourself, going back a few years, or sometimes just a few months, in your code can be a very painful task if you change the way you write all the time. If not for other reasons, read it for fun. Also mentions documenting.