Why and when coding is fun
Posted by matt, Wed Jan 09 06:27:00 UTC 2008
For me, work should always be fun. If it isn't fun, it just doesn't get done.
So with a total of $0 raised so far, many people would call it crazy that I still sit in front of my mac each day and code. So in order to clear up any perceived misconceptions about what Reformed Software is all about I will reveal how spending time working on the projects such as TheUnboundWord is fun.
When solving a problem: this is the joy of any engineer or programmer. When an engineer is solved with a problem, they don't rest easy until that problem is solved. I don't just mean a quick hack to solve the problem, I mean a proper solution that involves design, testing and investigation.
When the software has a purpose: many times, developers work on projects that they simply don't want to use or will never use themselves. At Reformed Software, the software developed is actively used by the developers. TheUnboundWord started as a need that I had whilst listening to podcasts, and though it is in the early stages of development I actively use it.
When the software is well designed: A good design is always needed and this is pivotal to creating a solution. The design allows for problems to be mitigated before they occur and results in coding being about implementing features rather than fixing bugs.
When the software is documented: When working in a group, documentation always seems tedious, yet when it comes to working with code written by other developers if it isn't documented then all fun gets taken away as you have to figure out their mindset.
So, just a couple of thoughts about why and when it is fun coding at/for Reformed Software.
In more general news, testers are still required particularly if you live in Melbourne Australia. Contact Matt at ReformedSoftware dot com for details.
God bless,
Matthew Delves.