The programmers at Velan write a fair amount of code. Recently we have been thinking about how we write code, and what we want our code to look like. After some discussion, we have distilled our thinking down to three high level points:
Changeable code is rooted in the idea that no code we write will be perfect, nor do we want it to be (because perfection is context-specific and the context is always changing). Code should be written assuming it will be added to, subtracted from, modified, and deleted.
This does not mean we just write poor quality code as fast as possible. Writing changeable code requires good judgement, clean architecture, and constant attention.
Our studio values the unconventional and the curious. Both require constant learning.
Write enough code, and some code can be neglected. Accumulating hacks and workarounds, passed between programmers, the clarity of its original purpose lost, the code has become ownerless. It is not enough that code is changeable, we must actually change it. We believe this derives from a sense of ownership.
The concept of ownership applies to external code we use as well. In order to feel comfortable using some external code we must:
At Velan, we have a two-pronged technology strategy:
We believe this approach gives us the best opportunity to create systems that align with our values, and to make the kind of games we want to make.
We have already been working on Viper for several months now. As we create systems that we think could potentially be useful to the wider community, we will be releasing them to the community under an MIT license and announcing it on this blog.
So keep an eye out! Until next time.
You can reach the technology team at Velan by emailing email@example.com.