One cannot rely on objective standardized tests to gauge how good one is at the act of being.

They’re good to indicate a specific aspect of where you wish to affirm your competence in, but have exhibit numerous fallacies when you’re trying to optimize a probabilistic, unstructured, instinct based behaviour over longer spans of durations, ranging from weeks to decades.

Such a gauge is probably only exhaustively captured in how the complexities of life unroll around you based on your behaviours.

I like studying and exploring new things in the spirit of science. The science that happens today in institutions is more than just science and involves a lot of ancillary efforts directed towards the formalized production of research.

I respect formalized scientific efforts but feel like humanity as whole is losing out on the idea of having personalized problem statements to work on without worrying about applications, citations or what the next big thing is going to be.

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.

This is how I time my workblocks these days…

Prerequisites

• ALSA : https://wiki.archlinux.org/title/Advanced_Linux_Sound_Architecture

Functions

single_beep() {
( \speaker-test --frequency $1 --test sine )&
pid=$!
\sleep  0.${2}s
\kill -9 $pid
}

morse(){
for i in {1..3};
do
        single_beep 400 $1
        \sleep 0.${2}s
done
}

sos() {
    morse 200 500
    morse 400 500
    morse 200 500
}

timer() {
    \sleep $1 && sos &
}

Usage

The above can be sourced in your shell rc.
I store it in a .bash_funcs where I have all my functions and source them in the end of my rc as source ~/.bash_funcs.

EDIT : 0x22D2 : Fri Sep 27 03:51:30 PM IST 2024

• I’m thinking I’ll proceed in common lisp
• do read on for amusement though

As of 0x22CE (Mon Sep 23 06:48:40 AM IST 2024), These are the operating systems I’ve used:

• Open Suse TumbleWeed
• Fedora, CentOs, Rocky
• Debian, Ubuntu, Kali
• Arch
• Windows XP,Vista,7,10,11

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))…

If you’re new to the concept of polymathy (I personally ventured into the idea when I read Da Vinci’s biography by Walter Isaacson), a lot of counter-intuitive traps await you when trying to build competence in multiple areas.

You don’t need to be a generalist at all times during your journey into polymathy. I mentally grasped this fairly recently that you don’t need to shun specializing for smaller durations. Something like a day is obvious as a candidate but, in the past, I would shy away from even periods of a month to actually focus on a singular thing. I’m fairly comfortable doing that for upto three months now but would recommend touching a large span of domains over the span of six months for you don’t want to start losing out on the humility that interdisciplinary pursuits enforce on you.

Alter your doom block in init.el:

(doom! 
    ...
    :lang 
    (python +lsp +pyright +conda)
    ...)

I recommend pyright, is snappier than pyls..

you’ll also need lsp enabled in your tools, I also have +peek

(doom! 
    ...
    :tools
    (lsp +peek)
    ...)

for more info, hit <space> h d m lsp<CR>

Alter your config.el (I use miniforge to get mamba and conda):

                                        ; Conda
(use-package! conda
  :config
  (setq conda-anaconda-home (expand-file-name  "~/mambaforge"))
  (conda-env-initialize-interactive-shells)
  (conda-env-initialize-eshell)
  (conda-env-autoactivate-mode t)
  (add-hook 'find-file-hook (lambda () (when (bound-and-true-p conda-project-env-path)
                                    (conda-env-activate-for-buffer)))))

Once that’s done, hit <space> h r r and your ready to go.

People have been responding to emacs and my beard.

For a while I thought I did not have a lot to say. Turns out a lot of other humans are quite interested in the much of the same things that I’m into: my hatred for the mouse, and the consequent love for efficient workflows being some of them.

I’ll give the people what they want: I get to enjoy esoteric tech and spread the word, growing a cult, while other humans have enlightened experiences (believe me I do talk like this in person) and continue propogating the techno-propaganda about enjoying computer science.

From time to time, I do encounter ideas that intrigue my intellect for quite some time.
I do maintain the ideation buffer to index these ideas into the larger context of my past musings, but I would also like a conveniently accessible chronological search available for cross-domain ideas.
I’ll hence be increasing the frequency of premature technical thoughts being packaged into a micro-blogs.

I might not elaborate a whole lot in terms of the theoretical aspects of the tooling but I’ll be conceptually outlining my current thoughts over the same.

Emacs has been a trustworthy companion of mine for around 4+ years now. We’ve shared some highs and lows. I owe a major fraction of whatever conceptual depth I maintain in computer science to messing around with my tools.

Emacs is also the core of my first major youtube breakthrough.

I haven’t yet explored the emacs niche completely and will be investing more time into honing my repertoire and understanding what sort of mindset the tooling expects from you rather than just fitting emacs into my thoughts.