Skip to content

Commit

Permalink
updates
Browse files Browse the repository at this point in the history
  • Loading branch information
rajp152k committed Mar 31, 2024
1 parent a80f573 commit ede4825
Show file tree
Hide file tree
Showing 5 changed files with 22 additions and 3 deletions.
6 changes: 4 additions & 2 deletions Content/20230712223044-lisp.org
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,8 @@ Maxwell's equations of Software (~Alan Kay in some Interview~)
(#t (apply (car e) (evlis (cdr e) a) a))))
#+end_src
* Comment Stream
** 0x2211
- getting into "On Lisp" Now
** 0x21F4
- Researching deeper into lisp being a universal representation of compute.
- the core boils down to abstract syntax trees being an intermediate for any compiled/interpreted languages
Expand Down Expand Up @@ -301,8 +303,8 @@ I'm still a novice and haven't built anything of consequence in lisp: I wish to
* Literature Queue
- [x] Structure and Interpretation of Computer Programs
- [x] Common Lisp: An introduction to symbolic computation -> book review
- [ ... ] Practical Common Lisp
- [ ] On Lisp
- [x] Practical Common Lisp
- [ ... ] On Lisp
- [ ] Let over Lambda
- [ ] The Art of the MetaObject Protocol
- [ ] Professional Automated Trading : Theory and Practice
Expand Down
1 change: 1 addition & 0 deletions Content/20231207111339-mind_ai.org
Original file line number Diff line number Diff line change
Expand Up @@ -163,3 +163,4 @@ All generic knowledge goes into their respective nodes and this one only serves




2 changes: 1 addition & 1 deletion Content/20231212081635-programming.org
Original file line number Diff line number Diff line change
Expand Up @@ -28,4 +28,4 @@ I'll be exploring both, high and low level, ends of this spectrum in this node c
* Stream
** 0x21F1
- programming can really be boiled down into how instructions (computing) and data (memory) communicate with each other (networking) to achieve and objective.
- thinking this serves to be a good blanket statement that helps cover the notion of programming
- thinking this serves to be a good blanket statement that helps cover the notion of
7 changes: 7 additions & 0 deletions Content/20240216104908-operating_system.org
Original file line number Diff line number Diff line change
Expand Up @@ -5,3 +5,10 @@
#+filetags: :programming:

Diving into the depths pedagogically by studying the [[https://elixir.bootlin.com/linux/latest/source][Linux Kernel]]. To be more specific when discussing concepts, I'll be linking to a particular part of the kernel [[https://elixir.bootlin.com/linux/v6.8-rc4/source/rust/kernel/init.rs#L412][with the line numbers]].

* Plans
- https://www.kernel.org/doc/html/v4.10/process/howto.html

* Misc Resources
- Booting up: https://docs.rockylinux.org/books/admin_guide/10-boot/
- the linux kernel: https://www.kernel.org/
9 changes: 9 additions & 0 deletions Content/index.org
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,14 @@ I also consider deliberately intellectually [[id:f3347380-f482-4077-a89b-a3ff059
- log of all videos along with plans and indices into drafts
** [[id:44ba44d8-4ea9-4656-b367-bafffafe61f6][Batman]]
* Stream
** 0x2211
- starting out a block of hyperlearning
- emphasis on precision and the exact differences between the concepts under discussion
- pausing the creativity for the while
- will be focusing completely on understanding first initially : there's quite a lot that I am not yet completely aware about the workings of
- trivial knowledge is pre-cursor to pushing boundaries with ingenuity
- lofi classical is going to be the go to auditory nootropic strat this cycle
- have tried techno previously and expect this to help me loose myself somewhat quicker and a more stable manner
** 0x21F1
- beginning to dive deeper to build repositories that represent true insight and don't just mimic a micro-wikipedia.
- will be focusing on condensing abstractions into descriptions that are just enough : terseness is key
Expand Down Expand Up @@ -159,3 +167,4 @@ Here are some conventions that I follow to organize my work:
- each major node has its own idea buffer to keep note of specific ideas that I haven't organized yet.
- at any given point of time, several emtpy nodes may exist : I'm not trying to be exhaustive right away when exploring a domain. This is supposed to be an eternal work in progress. However, to indicate that I intend to work on a node later on and it's not just an empty atom, I've placed ~:tbp:~ (to be populated) tags on such nodes.


0 comments on commit ede4825

Please sign in to comment.