4/4/2023 0 Comments Tumult whisk![]() I chose to work in Tumult Whisk – I reckoned it wouldn't work straight away. I let the idea brew for a couple of days, then put a swift demo of my own together. I wanted to integrate it with this site, too. I felt that it would be a better exercise if the image was less well-known, and better still if it was a random image. I thought that I could use the demo to help people get a swift feel for discovering something. A part of my mind is – unconsciously and constantly – on the look out for things which might help me to explain something. The division raster example was interesting because it was nice to do, and because that pleasure came from revealing something. The exercise turned up as I was looking at charting tools. Let's acknowledge that, and talk about how we can do it. None the less, testers do it, coders do it, and we seem to spend ages on it, whether we're building a new thing from the ground up, or integrating some massive collection of legacy kit. I seem to spend ages wrangling and debugging, yet I don't find much about it in testing or coding literature. I've called this work wrangling and debugging (link will take you to the series I wrote on it in late 2021). I think it's about the same, though the work is perhaps more transferrable in this case. ![]() For this, when most of the tech is taken from / written by another, you might imagine that I do more configuration and diagnostic work (because I don't know the thing I'm using) or less (because my code is built by one gadfly mind over years). This is an example of what I do when making an exercise. ![]() A roughly-chronological story of how I ended up with the RasterReveal exercise. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |