I'm building inconsequential projects for fun and learning. The more inconsequential the better. -- lived intentional irreverence
What on earth is up with how you've titled the sections of this page???
From the Five Ws, or, taken loosely from the Seven Circumstances --
Therefore it is not a pointless endeavor to divide these circumstances by kind and number; (1) the Who, (2) the What, (3) around what place (Where) or (4) in which time something happens (When), and sometimes (5) with what, such as an instrument (With), (6) for the sake of what (Why), such as saving a life, and (7) the (How), such as gently or violently…And it seems that the most important circumstances are those just listed, including the Why.
| Circumstance | in other words... | is answered via |
|---|---|---|
| Who | Who you are? | whoami 🤷♂️ |
| What | What are you doing? | Projects 📂 Publications 🖨️ |
| Where | Where are you? | whoami 🤷♂️ |
| When | When are you? | whoami 🤷♂️ |
| With | With what instrument? | Tools 🛠️ Toolbox 🧰 |
| Why | For what purpose? Through what impetus? |
Ethos 🚎 Personal philosophy ⍟ Cults ⛧ |
| How | In what manner? Through what animus? |
Memes 💅 License 📄 |
It makes the most sense for me to answer these in order of who, why, with, what, and how.
Howdy. I'm Nathan, a.k.a. Skenvy (which started as my mid-2000's online gaming alias, and just stuck).
This is my "personal" GitHub account that I use to delineate from my "work" GitHub account.
Degreed in Computer Engineering, Maths and Geology; I've spent several years working across a range of technical roles: FPGA development, product support, Azure apps, "consulting", and data engineering. Since 2020, I've worked as a hybrid at the intersection of "DevOps" / "SRE" / "Cloud" / "Platforms" / "DevEx".
Caution
Likey, nothing better symbolises the curious, chaotic, cheeky, vibe of my approach to all things (through choosing "lived intentional irreverence") than this; the time when I was 15, stumbled upon a broken umbrella, and had no qualms asking, or answering: "Could you fit all the pieces of an umbrella in an apple?"
See the answer
Yes, you CAN fit all the pieces of an umbrella in an apple!
Have you ever wanted to start a cult?
In the software development space, there's already a variety of cults to choose from!
The Cult of Done
The "Cult of Done" is a nice set of quip-based motivationals, if those would help you. I first encountered it on NoBoilerplate @ yt.
The Cult of Done Manifesto
- There are three states of being. Not knowing, action and completion.
- Accept that everything is a draft. It helps to get it done.
- There is no editing stage.
- Pretending you know what you're doing is almost the same as knowing what you are doing, so just accept that you know what you're doing even if you don't and do it.
- Banish procrastination. If you wait more than a week to get an idea done, abandon it.
- The point of being done is not to finish but to get other things done.
- Once you're done you can throw it away.
- Laugh at perfection. It's boring and keeps you from being done.
- People without dirty hands are wrong. Doing something makes you right.
- Failure counts as done. So do mistakes.
- Destruction is a variant of done.
- If you have an idea and publish it on the internet, that counts as a ghost of done.
- Done is the engine of more.
These are supposedly licensed Creative Commons by Bre and Kio, but I can't find a link to the original license. If you're reading this and you know the source of the original license, please submit it in a PR.
Usually writing yaml in vsc out of wsl.
Languages / Ecosystems
- Python
- Bash
- Java
- Yaml
- Make
- Ruby
- TypeScript
- C#
- PowerShell
- VHDL
- Rust
- Go
- Julia
- R
- Kotlin+Android
- Erlang/Gleam
The JS, TS, Node ecosystem evolves so fast it feels like you're "always" learning it.
At least as important, if not more so, than the tools someone uses, is how they maintain their toolbox.
By which, of course, I mean, dotfiles! Take care of the tools you use, so they can take care of you!
Tip
My dotfiles are their own how-to, from main. home is my home. Or, make yourself at home, too.
I've put enough work in to the features and portability of my dotfiles, that I would count them as my 0th project.
They are also where I keep my own short guides on managing: git, ssh, and gpg.
Note
I maintain several niche packages that besides their respective typical hosts, also live in GitHub Packages.
My open source contributions to other repositories can be seen here. You can similarly see yours here.
There's also my gists.
- 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.
- dispatch-suggestor: A github action for commenting on PRs with a list of suggested
workflow_dispatchtriggered workflows to run based on what workflows it determines will run when the PR is merged. - 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. There's probably more collatz repositories on GitHub than you could poke a stick at. This is just one of them. I picked the topic to match the goal of "personal Rosetta Stone" rather than the other way round. The choice of topic came from having a bunch of python scripts written years ago that went down a rabbit-hole, so I made this to make myself stick to KISS.
- Sudoku: A java JFrame implementation of a sudoku solver I wrote circa 2013 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.
- dependabot-linguist
:archived: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.
- Honours Thesis (2017): ECDSA and ECDH in VHDL for FPGA
I communicate heavily through memes. See some here.
Note
Skenvy by Nathan Levett is licensed under CC-BY-SA-4.0
