Nit: there's a link to cue.dev at the very end of the article, I would put that up top, along with a brief description of what it provides either at the very beginning or when cue is first mentioned.
Ahh yeah I forgot these two things! I've now added them when CUE is first mentioned in "The system architecture" section, although not at the very beginning as I was trying to give an overview of the project and why I started building my custom solution first
That's a really nice article, thanks. And I can see how separating the validation logic from processing code is useful.
What's not clear to me is why you chose this approach over existing OOP techniques, such as GoF Adapter Pattern, or even just interface implementation (as Go looses a lot of the ceremony of Java/C#).
What's not clear to me is why you chose this approach over existing OOP techniques, such as GoF Adapter Pattern, or even just interface implementation (as Go looses a lot of the ceremony of Java/C#).