I was explaining this to some junior programmers the other day and it’s worth repeating. Failure is fine in software engineering, in fact it is expected: I get nervous if something works first time these days as I know my limits and expect to make mistakes. However I think that new programmers don’t always realise [...]
Yesterday I wrote about optimisation work flow and in this post I will be discussing why you should not preemptively optimise your program’s source code. You may wonder what could possibly be wrong with preemptively optimising the source code, it just makes your program faster right? And that is the trap: while it does make [...]
I have moved my RSS feeds to feedburner.google.com so you may have to update your bookmark in your RSS reader, although there should be redirection in place to redirect the old feed URL to the new location.
I believe the key to optimising any program is measurement: not writing l33t code which seems to be what a lot of programmers think optimisation is! The optimisation process is all about finding the slow parts of your program and speeding those slow parts up by refactoring your source code to meet your target performance [...]
Jani Hartikainen has written an excellent post in reply to my earlier post about teaching software engineering students memory management, and his post is well worth a read. I started off writing a comment on his post as a reply but I ended up writing more than I expected as I refined my ideas.
I agree [...]