🤠 G'day

Howdy, I'm Nathan, a.k.a. Skenvy, 29 year old Australian. I'm building inconsequential projects for fun and learning. The more inconsequential the better.

Degree'd in Computer Engineering, Maths and Geology, I've spent several years working across a range of technical roles, starting off with FPGA development, then product support, .Net/Azure desktop app design, consulting, "data", and for the last few years as something that is SRE-adjacent, "devops"-y cloud thangs.

I probably have more closed projects than those that I've continued to work on, although I do regularly go back through and question whether I want to revive any of my old project ideas. I've definitely had more consistency, and improving, over the last 2 or so years.

🚰 Projects

1. julia-release: A github action to release a julia project in a way that feels more ideologically alligned with how I'm familiar with releasing, as opposed to julia's officially recommended release pattern.
2. dependabot-linguist A ruby package that can be used to have a guess as to what sort of dependabot configuration is appropriate for a given repository, with the primary use case of automating the configuration across multiple repositories without the need to manually investigate their contents.
3. Collatz: An attempt at a personal Rosetta Stone and collation of language-fu-isms, all attempting to achieve sort of the same thing, along with various general repository health examples, and learning github actions.
4. Sudoku: A java JFrame implementation of a sudoku solver I wrote 8 or 9 years ago and have been sitting on with the desire to one day convert it into an android app. The distinction between this and other solvers is that this tries to catagorise the difficulty of the puzzle by which tactics it needed to solve it, that is to say, it tries to solve it using only specific techniques, in order, without resorting to heuristics / brute force that would be unobtainable for a person. It is more as a learning tool to put in a challenging sudoku and be prompted for which possible types of moves remain.
5. SeleniumNG: A project I started to try and make another project which required the use of Selenium and TestNG more consistent across all the people using those tools rather than have them all write their own. It was never made pretty, so it's not nice to look at, but it did what I needed it to do.
   • Localiser: It used to be a working example of using SeleniumNG, until google translate's page changed, and I haven't gone back to update it in years since.
   • FluentXPath: Similarly heavily unmaintained and essentially almost totally un developed, this was used in some SeleniumNG use cases briefly, to chain together devs.

Honestly, though, I mainly made this sponsors page to see what the process was like and test adding the FUNDING file in one repo.