moin!

this is Havu [they/dey/neutral]!
not familiar with neopronouns? see my pronouns page for examples.

for an overview of what i do / have done, see my curriculum vitae page.

see the public files page for a document file version of my curriculum vitae.
i would also heavily recommend taking a poke around my personal code forge as well;
that includes a bunch of additional information!
especially the fairly elaborate Vue.js project whose deployment has since broken of course.
but the development process should be more intriguing than the end result anyway, right?
there's also a Full Stack Open rewrite in Vue.js in there :3
in addition to the original Full Stack Open project written in React / Node.js but that's a bit scattered.
i'll try to dig through the archives for that Eventually. maybe one day.

Projects

Statistics dashboard application from scratch [Vue.js, Node.js, devops+]

A collectionary view of statistics dashboards via amazon quicksight [front && back end]

The most involved project I had while working there.
Overview of the project:

The vanillaforums side of it was especially fun, since we pretty much used entirely unrelated functionality to make it work. That is, default types for user roles were an entirely different topic, but we realized we could use that for our purposes so I ended up hacking on it a bit.

Getting to learn a ton more Python just by doing was really enjoyable too. Most of the Vue.js and Node.js stuff was kind of routine at that point, so i definitely liked having a chance to expand my knowledge throughout those ~4 years.

Sure, the work itself wasn't necessarily that interesting, but taking the whole thing as a learning experience was quite nice overall.

Tweaks && extensions && modifications to existing applications [Python, SQL, GNU/Linux, bash, PHP, Node.js]

Kitchen sink development!

I can't really remember if I made any actual new functionalities onto that platform backend, but certainly did implement plenty of new stuff onto other semirelated applications, ones that'd warrant changes onto said platform backend too.

New tests, modifications to existing tests, invisible upkeep work that keeps stuff running, that sort of thing.

So I do have a fair bit of exposure to such Node.js backends at a professional level too, and wouldn't mind working fullstackishly on such things on a daily basis, even though I'd certainly prefer a bit more of a frontendy approach, most of the time anyway. Especially if that means I get to fix modern web frontends' accessibility shortcomings =)

Also, just to properly stress this point again: I am by no means fluent in Python at all
- but! I'd say the same thing about bash, and PHP, and a bunch of other things too;
what'd be most important for you to take away from this, I think, is that I made it work :>

Really simple and affectionately stupid cookie banner [React]

A relatively simple cookie banner, built in React as part of a navigation bar

The cookie banner was designed to be as simple and get-out-of-your-way as possible;
something I thoroughly enjoyed working on, despite being a bit overblown due to react, but it did still mostly do its job despite the somewhat-misaligned tools for the job.
That is, it really could've been a raw HTML static thingy too.

I had had no prior experience of elasticsearch, so it took a while to figure out the endpoint calls, but it turned out to be relatively easy to understand to me, despite some of its wonky syntax, and it did serve as a bit of an introduction to more elaborate backend modifications later on too:

There's this huge platform backend monolith that handles all the auth{entic,oriz}ation, all the {elastic,open}search requests, cookies, amazon web services requests, vanillaforums and limesurvey integrations, and whathaveyou.
It's written in Node.js so it was quite familiar-looking to me despite the overblown objectorientation,
as in, everything was sugarcoated as “classes” despite JS not even having classes, but I digress
[I just happen to have mostly bad experiences of objectorientation with java]

Simple email template editor [Vue.js]

Implementation of a basic text editor to accompany a more advanced email template editor

Using CKEditor, to extend an existing Vue.js administration user interface
- Previously, the only option was ace editor; wholly unsuitable for regular users

The mail template editor is part of a larger administration user interface.
It used to not really be keyboardnavigable at all, so at first I had to tweak the elements a bit.
I made the card genericdivisorelements behave more button-like, as in, added tabindices and key{up,down} handlers to them.
And poked at the styles just a bit.
To keep them indistinguishable from how they used to be, for pointerdevice users, while simultaneously adding the keyboard support it should've had to begin with.
So exactly the kind of accessibility work i'd prefer to do much more of in the future.

The email template list view also had a bunch of race conditions and such;
if the user tried to use both the search and filter functionalities, the list'd get out of sync, so I tweaked at it but have unfortunately forgotten most of the details there.
I do remember other keyboardrelated fixes there too, though:
the context menu was also a generic divisor, so I made that into a dropdownish list instead, with buttonlike elements interactable with the keyboard, and added Escape handlers for them.

The email template editor view itself had some similar shortcomings too, like having to fix the template type dropdowns to actually be select-like dropdown elements instead, but the bigger topic was that new basic mode editor:
ace editor, the huge monolithic one, had at least two key issues I can immediately think of:

so I added CKEditor as an alternative:
Overview [süßadmin, devops, personal life, ideology && whatnot]

Most of the details within this Projects section were dug out from a couple elaborate job applications from around a year back [this disclaimer was written on ], and i've upcleant them a bit to hopefully be a bit more parseable.
Here's a couple more loose words about what i've been doing since leaving that job early last year, as well as some more details of stuff i didn't mention yet about the prior work.

Most recently, I've worked as a junior software developer, from month number 8 of 2021 until month number 2 [exclusive] of 2025.
Said job ended on request of the author, due to a variety of details;
most of those details are personal/mental/physiological/cultural, but the technical side of it would mostly boil down to this:
I am not a devops engineer, and I do not wish to work with junk such as amazon web services.
Things I enjoy most are related to user interfaces, especially in the context of the web, and I do secondarily like backendy stuff and databases and systemsadministration too, but I do not like docker or kubernetes or other such plumbing jobs, and I needed a break from it.

I've since mostly worked on things related to a fediverse instance of my own including, but not limited to: Here's a brief recap of my educational/professional background: A brief recap of some of the past work that i didn't yet elaborate on above:

Briefly on the topic of the personal projects:
I don't use a mouse,
and a proper explanation of why that is would probably require too much elaboration, so the context of most of these tweaks is this didn't work for me, so I fixed it;
most such fixes are available at my codeberg account and some of them are also backed up at the queer git

I started the enbyhacks fediverse instance project for a couple reasons:

It has been a ton of fun!
I still treat it as mostly an ephemeral thing that might just blow up at any point, but thus far it's looking like something I'll definitely want to keep around, for the foreseeable future anyway.

Meow.