TM354 · Software Engineering · September 2026
What Makes Good Software? Lessons from TM354
I've also started TM354, Software Engineering. One of the first things I've been thinking about is that writing software isn't simply about making something that works. The way software is designed and maintained matters too.
Software has to meet people's needs
A software system is built to meet requirements, but those requirements are ultimately connected to the people who use the system.
A successful system therefore needs to do more than simply run without producing errors. It needs to fulfil the needs of its users, meet their expectations and be delivered within reasonable time and cost constraints.
It also needs to be able to cope with change. User requirements, technology and the environment in which software operates can all change over time.
What does software quality mean?
One thing I found interesting was the idea that software quality includes several different characteristics.
- Usefulness: does the software actually help its users?
- Usability: can users understand and use it effectively?
- Reliability: does it behave consistently?
- Availability: is the system available when users need it?
- Maintainability: can the software be changed without excessive difficulty or cost?
The last of these has particularly stood out to me because it is easy to think about software as something that is finished once it works.
Why maintainability matters
Software rarely stays exactly the same throughout its lifetime. Bugs need to be fixed, requirements change and new functionality may need to be added.
If the code is difficult to understand or changes in one part of the program regularly cause problems somewhere else, maintaining the system can become expensive.
This has made me think differently about some of my own programming projects. Getting a program to work is one thing. Writing it in a way that makes future changes easier is another.
Extreme Programming and its values
Another part of my study has introduced me to Extreme Programming (XP). XP uses five values to guide software development:
- Communication
- Simplicity
- Feedback
- Courage
- Respect
I'm particularly interested in the relationship between communication, simplicity and feedback.
Communication
Software development is a team activity, so knowledge needs to move between people. A technical solution isn't particularly useful if the people who need that information don't know about it.
This also made me think about problems differently. If something goes wrong, it can be useful to ask not only "How do we fix this?" but also "Was there a communication problem that contributed to it?"
Simplicity
One idea from XP that I found particularly memorable was the question:
What is the simplest thing that could possibly work?
This doesn't mean that software development is always easy or that every system should be extremely simple. Instead, it encourages us to avoid adding unnecessary complexity when we don't need it.
This seems especially relevant to small personal projects. It can be tempting to add another feature simply because it would be interesting to build, even when it isn't necessary for the current problem.
Feedback and change
The other idea that stood out to me was feedback. It is very difficult to know in advance exactly what the best solution will be, particularly when working on a new or unfamiliar problem.
Feedback can come from many places: other people's opinions, testing, the code itself and what happens after software has been deployed.
This means that development doesn't necessarily have to be about finding a perfect solution immediately. Small improvements followed by feedback can help us discover what actually works.
What I'm taking away from this
TM354 is changing the way I think about programming. I'm beginning to see software development as more than writing code that produces the correct output.
Good software also needs to be understandable, maintainable, usable and capable of changing when its requirements change.
That's something I want to keep in mind as I continue working on my own projects, including KanjiFall.
← Back to Learning & Development