Abstraction's End
home page
original site
twitter
thoughts
about
Linked TOC

About Me

Identity/Contact

Mariven is a pseudonym, but as faithful and consistent a pointer to the identity of the person who created this site and wrote everything on it as you'll find anywhere elseI have a government-standardized 'real' name that goes on my government-standardized documents, but it is not something I identify with and actively use, and I don't share such information except with people who need it for government-standardized reasons (whether the government is playing the role of facilitator as in mailing/shipping or that of supervisor as in hiring/funding). If you have a good reason to want such information, contact me directly.. You can contact me at this username through Discord, (Libera) IRC, or email mariven at !c{proton.me}{(equiv. protonmail.com, pm.me; I just use proton.me as a matter of idiosyncrasy)}; the Twitter handle was taken, so there I go by @psychiel. Preferred order is Twitter = email > Discord > IRC (which I only sporadically use).

Mentality

Two things fill the mind with ever new and increasing admiration and reverence, the more frequently and persistently one's meditation deals with them: the starry sky above me and the moral law within me.
Immanuel Kant's Critique of Practical Reason (tr. Pluhar), Conclusion.

Statistics

(Purple items are unambiguously true—at time of writing, at least).

For Cybersleuths

If you're browsing around this website trying to figure out who I am and what I/my work can offer you, or generally trying to piece together a mental image of me, consider looking at the poorly named thoughts page, which is just where I put all sorts of long-form writings that don't feel complete or thorough enough to stand under their own weight(and my home page should make clear how unreasonably high this bar is); it contains nearly a hundred thousand words covering all sorts of topics. If you're browsing my Twitter account, make sure to check out the replies tab, where most interesting, in-depth exchanges happen. And, if you have any questions or uncertainties, you can literally just ask. (If you don't want to read, or don't want me to write, several thousand words in response to a basic question about why I think X or seem to assume Y or whatever, just say as much, and I'll shorten my reply).

About this site

Logistics

If you're actually interested in the construction of anything here, just go to Inspect Element; excepting a few common libraries, I wrote the JS, (S)CSS, and, with the exception of a few macros like $!$c{abcd}{efgh} for the contextual !c{abcd}{efgh} which are regex-replaced by the aforementioned JS, write the raw HTML for each page in VS CodeThat's right, like an animal. It's what works for me, though, allowing me to create things like this sidenote in a clear, non-finicky way that WYSIWYG editors fail to provide. It also allows me to do things like turning an 800-page book into a single continuous webpage with a freely navigable table of contents. I feel like doing this in a "modern" content management system would result in a page that hangs for a whole second every time you try to scroll.. The site is served by nginx on a DigitalOcean server that costs like a few dollars a month, and the domain is managed by a blood oath with Cloudflare that costs like a few dollars a year.

Note: None of the code is written with the intention of impressing, or even being amenable to working with, other people. That means no tests, no coding conventions save my idiosyncratic preferences, little documentation save what is necessary for me and only me to understand what I was thinking earlier (let alone "self-documenting code"), and so on. It's not scalable or flexible except in the ways I personally want it to be scalable or flexible—there are definitely several smelly code patterns that any seasoned developer looking at this code would immediately notice and start fuming over, but they work for my style of thinking, for this website in particular, and that's what I care about. (Though, even then, there are some problematic issues that I want to fix, but have never really found the motivation or time to go back and rewrite my old code—so it's a palimpsest of novice oddities and later workarounds).
!tab For instance, I would never use a meta-meta-regex-parser in a production codebase, if only for the sake of whoever else has to maintain it, but I'm happy to write one here because I'm inclined towards solutions involving regex parsing and meta-meta-anything; they come naturally to me, and I'll readily explain what I'm doing to any curious person who wants to write one themselves or modify/extend mine. But if I ever have to make the functionality it performs more widely accessible (or someone pays me to do it), I know it'll have to be redesigned from scratch.

Cruxes