sarrowsmith

30 years of professional software engineering, but when it comes to games a hobby dev with experience best measured in months. Working in Unity for the ready availability of graphical assets, or Godot because the development environment is so much nicer, and experimenting with Ren'Py because I'm also a writer. Confident at turning my hand to any programming environment (I had no C# before picking up Unity, and obviously no GDScript before Godot) but utterly unskilled in graphics, rendering and animation.

My interests lie with games which don't require the player to engage in conflict or have lightning-fast reflexes to progress, and using randomised procedural generation to add replayability. While making better use of the power of modern platforms than simple puzzlers.

Lessons I have learned along the way:

1. Consoles may be underpowered in the CPU department, but they have disproportionately beefy GPUs, and game devs are _still_ in the business of wringing every last drop of performance out of limited hardware.
2. Water is difficult.
3. Don't be afraid to downscope your project. Something now is better than nothing ever. (See also the Zen of Python.)
4. Don't stick with a platform that's not working for you.
5. Be careful about being distracted, even if it looks like a relevant tangent.