I’ve lately been thinking deeply about how I interact with my computing environments; when working, I’ve a
- an unrooted snapdragon ARM Android with Termux and Tmux for ephemeral vimmin & sshing around when on the move
- an Intel x86 FreeBSD home lab for some asynchronous compute that I don’t need right away and some redundancy for my important files
- a personal ubuntu VPS with a couple of intel x86 vCPUs for my self hosting endeavours and overall context orchestration
- several compute clusters (avx enabled x86s, ARM, “the propietary GPU driver guy on the street” GPUs, “the other open source GPU driver guy on the steet” GPUs, k8s orchestrated production & development playgrounds) for work
- an AMD x86 Tumbleweed with emacs as the daily driver where I actually “work” : this is desk where I dissect, analyse, reconstruct and dispatch for usage across the above

This

you’ll need this to grasp that

Emacs Lisp is Tetris Complete

• did not mean Turing Complete
• really did not

I’m a Philosopher (etymologically speaking, I do love wisdom).

CognWare Industries was established on the 1st of May to philosophically channel my cognitive energies.

Explicitly addressing them allows me to separate out my identities of being technicality oriented (in here) and being too abstract (given the lisp aficionado that I am).

Of course, a fusion of being overtly-abstract and over-engineering my thoughts are fundamental to my operations and my personalit(y/ies).

As of today, am decommissioning my org roam notes builds : there used to be a notes section in the banner above.

The current UI is not apt anymore for the scale of nodes accumulated - build times are high (2+ mins) and the navigation capabilities are archaic : will engineer and publish another navigation experience soon. Will continue publishing my notes to the repository as usual.

Following a recent realization that jargons are fun, experimenting with prompts that inform LLMs to talk in outlines and jargons, assuming the reader is competent. Producitvity is up.

.dotfiles commit for linked context : https://github.com/rajp152k/.dotfiles/commit/28dd1385cc4370dd0b15774bb96a661b3cab628f

You respond exclusively in highly concise, jargon-rich org-mode only outlines, without any bold or italics formatting: the reader is a competent expert with polymathic knowledge and exceptional contextual comprehension. Do not provide explanations unless asked for further simplifications; instead, communicate with precision and expect the reader to grasp complex concepts and implicit connections immediately. Do not use any filler sentences and collabaratively contribute in constructing whatever topic is being expanded upon

During a recent surf, I chanced upon this beast.

The Information Manager from Hell
– Linus

Thinking about compiling more such landmarks – an itinerary for fellow cyber pilgrims

Reviewing older codebases is an underrated exercise for software engineers

It’s a journey through the evolution of code, revealing the engineering decisions that moulded what we deal with today

Tracing the history of a project – understanding what worked, what didn’t, and how technical components evolved – has been a joy lately

Context

been reading more papers
notes by jargony outlines
no unnecessary words

if can express
few words
you get it
get it?

concise, practical
flowy, comprehensible
jargon is fun

in org-roam
links when depth
more speed
good

all left
tech haikus
challenge
someday

until then

Enjoy instance for this

Nth Roam : An Emacs package to efficiently manage multiple roam instances

I’ve always maintained a philosophical appetite for the tooling that I use.

One of the core tenets of the Unix Philosophy¹ is that everything is a file…

Plan9² has caught my eye due to its more homogenous design than the usual unix you’re used to.

The footnoted-paper (~pre-mature book) is somewhat unhinged and doesn’t shy away from taking a jab at the Unix ecosystem and design.

Apart from the several points the author makes, what stands out the most for me is the idea of everything truly being a file: in hindsight, Unix only realizes a fraction of the principle.