Do note that this is an old post (from my last archived blog) that I’m refactoring : more on that here

The Unaltered Entry

[2022-02-01 Tue 10:11] - 7946

I, hitherto, have been reading books as a single unit of intellectual conveyance. However, that strategy doesn’t work for all the works. Some authors have their writings crisply intertwined with their other writings.

Approaching a single book as a part of a larger intellectual conveyance is more efficient in the longer term if one intends to read all the work of a particular author. Consequently, grouping these reads together has also been somewhat interesting lately.

I’d managed to produce some fairly original essays on my last blog and I’ll soon be incorporating them into posts here. I had a habit of writing in streams in the main blog itself and there is a lot of insight stored in the chronology of some such logs.

The old blog is archived in the repository here and I could benefit from repurposing old works into the present setup.

I’ll mainly be focusing on editing the fluff out, finding what good stylistic knacks I’ve accumulated over the years, and rejecting the questionable habits that don’t serve me so well.

Books play a pivotal role in the life of any aspiring and existing intellectual. I began reading diversely and seriously when I was 19 and immediately regretted not starting sooner.

Reading sets you up for an involved existence. If you read vastly, you’ll be a force to be reckoned with.

Over the span of 3 years (2019 - 2022), I read around a 100 books ranging from the classics, biographies, auto-biographies, physics, computer science, anthropology, data science, etymology, theology, game theory, mathematics, history, how-to-books, nutrition, physiology , fitness, health, psychology, neuroscience, linguistics, business (okay, don’t judge - we all do this), economics, writing, self help (guilty as charged), spirituality, humor (guides to being funny and similar stuff), young adult (only 1 - please don’t chastise me - I could not handle the cringe), philosophy (a lot - please don’t chastise me) and meta books (speed reading, how to consume books, taking notes, etc).

I took this up when I had to setup a bunch of NLP pipelines for work and this does stand true to its name - it is a quick and practical index into approaches, introductory theory and useful libraries for the same.

I don’t like reading text books at a stretch due to several reasons:- “cross a bridge, when you get to it” is something that has stood the test of time for me when it comes to reading practical books. I don’t find it useful to read stuff without the doing if that is what the book is intended for.

What makes lisp so unique is the way its code is structured - you definitely can’t miss all those parentheses. In this section of the series, I discuss the cause for such a representation and how that makes lisp unique in terms of how it views its code as data as code (aka homo-iconicity).

Further reading

• Python disassembler
• Homoiconity
• Byte Code
• S-expressions
• Common Operator Notation
• Abstract Syntax Tree
• The Blub Paradox

Call to collaborate

If you’re someone who shares the dream of making lisp popular and mainstream so that we can use it for our jobs and don’t have to switch to blubs to make a living (without denting its charm of course) , consider contributing to the notes and hit me up via mail or any of the other media I’m present on.

This is an auxilliary post collating resources for the recent video I posted …

The Pipeline

1. All the ideas, resources that I want to process, any miscellaneous questions I have, are fed into the input-queue in the buffer
2. All the manipulation takes place in these buffers - they’re org-files and I use org-roam to maintain the connections
3. whenever a node set ripens and is worth sharing, I write a post or publish a video.
4. It can go both ways : I can force a set into maturity if I wish to publish something specific or I may chance upon a concept when observing connections.

Observations

I use org-roam-ui to visualize the buffer and check for linkages that might result in something useful. I also want to publish this graph (demonstrated in video) but there’s no explicit solution for that yet and I’m planning to build one myself with rust and webassembly as a compilation target.

This is the first in a series of blog posts that follow the educational common lisp series on my youtube channel as an auxilliary.

I’ll be summarizing the videos in these blogs and be using these to point to references and additional resources that further elaborate the matter.

In memory of the author of vim, arguably the most influential programming utility ever…

Here is a paper : “ Seven habits of effective text editing ” by him that I hope continues to inspire programmers, as it did me when I was a novice.

[As of 0x213B : 2023-08-17 Thu]

I use emacs for a lot of my daily tasks and spend majority of my time in it. This is a review of some significant components of my init.el

;keyboard all the way
(menu-bar-mode -1)
(tool-bar-mode -1)
(scroll-bar-mode -1)

;I don't like distractions
(setq byte-compile-warnings '(cl-functions))
(setq ring-bell-function 'ignore)
(setq visible-bell t)

I chose the most recently engineered package-management solution when I began with emacs, haven’t switched since and don’t think I’ll need to. Migrating from vim, I preferred a configuration file rather than installations via melpa interface. Also, freezing and thawing is cool : exact reproducibility is guaranteed.

Given I’ve passed through SICP once, quickly grasping common lisp to build stuff and explore the traditional and industrial aspects of lisp (I know clojure exists but traditional…) was my next objective: with decent speed and only solving the somewhat involved exercises, it took me two weeks to complete this book.

The exercises aren’t meant to be a challenge but to adapt to the environment and the topics introduced. The book does not explore concepts with depth (CLOS, macros, etc…) but that shouldn’t be the objective of an introduction anyway.