“For years, I’ve defended lisp in pragmatism oriented SWE back and forths with ’they’re all an AST underneath, anyway..”
Now that I’m writing lisp on the job, I’m in a “gotta catch’em all” kinda mood and thinking of elaborating upon the eccentricities in my upcoming blogs and videos.
There’s a lot of questions I have:
- when do you deploy which one?
- are there any bad ones?
- why does that one exist?
- ..
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
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 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.
There’s this saying :
If you’re stuck on an island and have the opportunity to build all of the software landscape again, the programming language you should choose is C. But the first thing you should write is a lisp interpreter.
I’m going to do that with Go.
As for the saying, I’ve heavily paraphrased (aka butchered) that and don’t quite recall the source so do excuse me for that.
As of 0x22CE (Mon Sep 23 06:48:40 AM IST 2024), These are the operating systems I’ve used:
I recently moved away from Fedora 40 to Tumbleweed (I deleted some core python libraries that are essential for yum and dnf (I know, I’m an idiot))…
check out what an IKN0x means here
Understanding different languages can open up one’s mind towards different cultures.
The evolution of languages over centuries and common ancestors there-of over millenia indicates the evolution of cultural complexity.
I grew up actively conversing in 4 languages: English, Hindi, Marathi and Gujrati. French was my first romance language I was exposed to for over 8 years (I say exposed as was learning this academically as a third language and didn’t use this as a “natural” language as much as the others).
