As of today, am decommissioning my org roam notes builds : there used to be a notes section in 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.
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
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
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 Philosophy1 is that everything is a file…
Plan92 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.
I’ve started spending some time per day without the usual modern software engineering tooling (LLMs, the Internet, etc) to explicitly maintain my cyber-deduction skills (in the context of Unix-based systems (BSDs, Linux, yet to explore Plan9), mostly because they power the majority of the global compute infrastructure).
It’s fun: init your journey with a man man (I’m an info info guy myself) and be extremely skeptical of your usual modus operandi, ditching all assumptions and tumbling down the rabbit hole.
Fabric1 is a collection of crowd-sourced prompts, exposed via a CLI tool. I used it for a while some time ago but never fully exploited it because I prefer Emacs.
Eshell buffers are an option, but I am principled in my tool usage and prefer to delegate longer-running CLI tasks to a combination of Alacritty and Tmux.
Maintaining my Emacs shell usage to ephemeral popups feels natural.
Gptel2 is a versatile LLM client that integrates smoothly into my workflow (buffer/text manipulation and management) without disrupting my thought flow.
For a while, I’d limited my studying endeavours to be project oriented and not domain oriented. While I enjoy the pragmatism of the former, I also wish to build up my innate curiosity to get under the hood, disassemble the engine and be able to put it back together: no project (except the explicit choice of doing so) is going to help me fit that in my studies.
Consequently, I’m planning on getting started with a regulary habit of exploring domains with depth.
From time to time, I like to make minor tweaks to my blog based on the treasure trinklets I find around in different corners of the internet from blogs/works of personalities I follow/find interesting.
I got into the practice of logging updates in reverse chronological streams from one of my professors in my sophomore year.
I began personalized hex timestamps (today is 0x2360 for me) because I don’t intuitively gel well with the (Julian -> Gregorian) cycles. The combination of lunar, solar and planetary cycles is my most recent experimental initiative for calibrating long term efforts but that would be a little too chaotic for the part of the world wide web that I mostly interact with these days.
