Caution
Likey, nothing better symbolises the chaotic vibe of my approach to coding 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?"
Important
Howdy, I'm Nathan, a.k.a. Skenvy, "30's"-year-old Australian 'devops' human.
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: FPGA development, product support, Azure apps, "consulting", "data", and for the last few years as something that is 'SRE-adjacent', "devops"-y cloud thangs.
Tip
My dotfiles are their own how-to, from main. home is my home. Or, make yourself at home, too. Home Is Where the Dotfile Is.
Have you ever wanted to start a cult? Thankfully in the software dev space, there's already a variety of cults to choose from!
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 licensed Creative Commons by Bre and Kio, but I can't find a link to the original license.
Of course, the value of anything like this is in the self-determination of adopting it. This doesn't need to be a serious thing, and it's best when it isn't. These aren't hard and fast rules, anymore than you choose for them to be! A preface that only feels necessary after seeing several tirade-esque posts admonishing the use of any motivational tools while trying to find the original source for the CoD manifesto.
My take?
Generic
- vsc
- vim
- AWS (via CFN/CDK/TF)
- GCP (via TF)
- GitHub Actions
- BuildKite
- Docker
- Docker-Compose
- K8s
- Helm
- K9s
- PostgreSQL
- BigQuery
- RedShift
- dabbled in Cassandra
- Git
- Mercurial
- Agile
- Kanban
- Scrum
Languages
- Python
- Bash
- Java
- Yaml (lol)
- Make (lol).
- C#
- Go
- Ruby
- PowerShell
- Julia
- R
- VHDL
- Rust
- Kotlin+Android
- Erlang/Gleam
- JS
- TS
- Node
Note
I maintain several niche packages that besides their respective typical hosts, also live in GitHub Packages.
There's also my gists. One that I have favourited because I regularly access it is SSH for multiple GH accounts.
- 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.
- 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.
- 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.
- Honours Thesis (2017): ECDSA and ECDH in VHDL for FPGA
Note
Skenvy by Nathan Levett is licensed under CC-BY-SA-4.0
