Writing up an updated version of my C++ coding guidelines.

I’ve written C++ and C coding guidelines for a number of teams that I’ve been part of. In general, those documents are owned by my employers at the time I created them. I’m working through a list (just getting started at the moment) of things I think should be included in current day C++ guidelines and posting them under my ‘information’ tab here on my career blog. This is a work in progress and depending on how busy I become may stall for extended periods of time…

If time permits I may also write up some commentary on java and C# (and perhaps others).

2 thoughts on “Writing up an updated version of my C++ coding guidelines.”

  1. Hi Kyle,

    I recently read a book I liked a lot on good coding practices, called Code Complete, by Steve Mcconnell. Wondering if you have seen it. As long as you are putting together C++ coding practices, you might find this book stimulating.

    1. I have a copy on my bookshelf above me right now 🙂 I’m looking at writing a new version of my coding practices document that isn’t owned by GE or Tektronix or similar. I’ve gone through this quite a few times over the years, but always for work and thus the result is owned by work. It is an interesting exercise though as every time I do it, the result evolves.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.