Welcome! These are personal notes that intend to not only educate, but entertain as well.
I am hardwired to rewrite notes, and I enjoy doing so as if I am teaching it myself. Thus, this repository of ASCII and intellect was born.
⛆⛆⛆⛆⛆⛆⛆⛆⛆⛆⛆⛆⛆⛆⛆⛆⛆⛆⛆⛆⛆⛆⛆
⛆⛆⛆⛆⛆ˏ___ˎ⛆⛆⛆⛆⛆⛆⛆ˏ_______________ˎ⛆⛆
⛆⛆⛆⛆/⧸🖳⍾┚⧹\⛆⛆⛆⛆⛆⛆⎸⸨☏⸩ - 𝌰𝍁𝌡⎹⛆⛆
"It is a shame that the ASCII looks... scuffed."
###
PLEASE READ THE FOLLOWING NOTICES!
-
Firstly, I highly recommend you read the "Array of Rules" (ArrayOfRules.html), where indicators, phrasing, content division, and anything requiring context will be named. This is a seperate file to declutter this file alongside allowing for later additions/amends.
-
This README file is a markdown file to catch the eye. This file type will be the only other file type in this repository that is not one of the few (three) I will teach. The HTML lesson files will also use markdown to simplify their file structure for even the least perspicacious beginners. Because of this fact, heed no mind to the contents of raw markdown files; in fact, I advise to not look at any raw files for the purpose of learning (without prior knowledge of the inner workings). I cannot fathom the fact that I learned markdown for this alone.
-
Let it be said that while these notes are seemingly worded with the expectation of public availability, these notes were solely meant for my own use at the end of the day. Even so, amnesia is always a possibility, so these notes are written under the assumption that the reader possesses minimal understanding of the covered languages.
-
As none can stop the flow of time, these notes might become less accurate if WHATWG/W3C/TC39 decides to update (i.e. screw over via syntax depreciation) HTML/CSS/JS syntax/formatting respectively. If some huge change occurs with one of the languages after 2026, anticipate the ommision of any features or fixes that might have come with that update; similarly, it is best to verify which updates removed functionality for revamped syntax/function rules. (The rest is a rant.) As seen from Unity's breaking changes with each update, any programming company will induce an upheaval for the following reasons:
- The thought that it would be an excellent move for company stocks/profits
- It will cut costs either through sunsetting a server (like an unpopular service/feature), or by simplifying/shortening a way to arrive at/achieve a specific result
- The desire to promote or emphasize another service or feature
- As a preventive measure from any exploitation of with the content in question, whether that risks legal or security issue
- "Because we hate our community lmao"
- (Insert shaky CEO excuse here)
For a reference on how far tech companies are willing to cause inconvenience for foolish reasons, please see Fumo YouTuber PsuedoDistant's rant as well (might have to open in new tab, markdown files can straight up ignore styling within nested attribute tags).
-
The ASCII art will not work for some users, and ASCII from the raw code might appear closer to modern abstract art than ASCII. The majority of the "masterpieces" I penned were made with Windows OS characters, so any operating system that have a slight difference between ASCII symbols will cause misalignment (and no, Markdown files cannot detect user device). Also, I do not use ASCII that have or are emojis, so that should hopefully create consistency. This is hardly important, as the art will never contain important information that cannot be sourced elsewhere within the notes. The ASCII art has also been adjusted to not interfere with information flow, so ignore it if anything may look like visual a(expletive).
Most of the info here came from O-C-A's Computer Science III course from 2025-2026, but I have added additional info because a course never covers everything that a coder might use. This will not either, just more than a course would ordinarily cover. I created the original in GitHub, but that version had my instructor's name displayed in the commits before permission was obtained. Incidentally, this repository was also created in GitHub, and can be found here.