This is another "I do this a lot so am blogging about it for future me" article. There is a lot of info about this out there, but doesn't tend to be in a single place, so I'm summarizing the wisdom of others.
I've seen testing, especially acceptance testing, done horribly wrongly over the years, and sadly I often see the same anti-patterns repeated over and over; so I thought it'd be worth talking about my perspectives on this thorny subject...
So, last significant update was 2014 - and most of the posts before that were about clojure. (I used to have a personal blog as well at blog.sietsma.com but it's a bit of a fiction separating tech from life from people stuff! Besides, I almost never...
I'm moving everything to Google Domains as I don't see the value in paying
for complex hosting. I'm using github pages for hosting static sites like
this one - I'll see how it scales, it doesn't have unlimited scale but I don't
think I get that many hits!
I'm planning to build a proper clojure snippets/cheat-sheet page, for all the things I do regularly, or want to encourage team members to do regularly. But it's easier to blog these to get them out rapidly, I'll try to format them nicely later.
This is a bit of an addendum on my previous post. - I wanted to convert some FreeMind mind-maps into other formats. FreeMind is pretty cool, especially as it's file format is fairly straightforward XML, so lots of other mind mapping programs, like XMind, will read and write FreeMind files.
"XML is like violence - if it doesn't work, use more"
Clojure is awesome for parsing and processing structured data. It has a wide range of functions for handling lists, maps (associative arrays), sets, and (if you really need them) objects.
One great example of the power of clojure for this sort of thing is processing xml. You may hate xml, you may use json or edn or yaml or anything else you can - but ultimately, xml is still all over the place, and if you need to handle complex xml or large xml, you might want to look at clojure.