Balance Programming
-
Data-oriented design
I read Data-Oriented Design by Richard Fabian but will mostly cover the methodology (DoD) not the book. Let’s get it out of the way and I’ll try not to belabour it: It’s about all the data Data-oriented design concentrates on the underlying data in any given system. Data tends to be stored in a very…
-
Searching for design
This Problem Changes Your Perspective On Game Dev looks at game design as though it’s a search algorithm touching on: Jonas Tyroller talks quickly and makes an argument for discovery rather than one off design. While I’m interested in game design are there lessons to be learned beyond that? Is game dev different? Jonas is…
-
Retrospective 1-26
One of my original goals with this blog was to manage 26 posts in 6 months. Here I am in 3 months. Well done me. This one is both a retrospective of that achievement and my thoughts about retrospectives themselves. I think they’re a good idea but… I’m not entirely sure they work. Retrospectives Maybe…
-
Less can be more
I was listening to the podcast series Cautionary Tales and their episode Do nothing, Then Do Less. By all means listen to the whole thing but I’d like to highlight the crossover with The Happiness Lab starting 12 minutes 30 in. Bias for adding People are apparently biased towards adding things in order to solve…
-
When to warn
If the software you’re developing has a problem then you want to know about it. We use log messages at runtime, build messages at compile time and we can run extra tools to tell us even more about our code. However there can be so many messages they you don’t end up reading them, at…
-
Algorithms are great, minimax
There are problems that are hard to solve. There are problems that are easy to solve if you don’t care about speed. At university the algorithms course was one of my favourites. Finding the right algorithm can mean being able to solve the problem much faster. Maybe you’ll have to discover it yourself but there…
-
Benchmarking tool
I’ve written before about when and how to optimise code. I think there are often more important aspects to a project than code performance. Servers, desktops, laptops and even new mobile phones are many times more powerful than an old computer. Instead you need to decide whether the performance is good enough. That could be…
-
Clean Code
I’ve heard of some people following the Clean Code methodology and some people reacting against it. It’s not been on my reading list before so I got hold of Clean Code by Robert C. Martin. I think it has some good ideas and a few bad ideas. My biggest problem is that these are often…
-
How often?
Don’t Repeat Yourself (DRY) is, ironically, said quite a lot. I think in general this is uncontroversial. If you have a choice between writing a lot of very similar code: Or something smaller that does the same job: You are probably going to choose the later. Maybe you think this is an overly simple example…
-
AI assistance
We now have access to new powerful tools like ChatGPT that can help us write code. There are a number of potential issues with this: So far I haven’t found this useful for situations at work. Every time I had asked for some source there were fundamental flaws with the code. It did sometimes give…