Programming
Table of Contents
Reference Collating Node
1. Abstract
Computer Science is Physics to the Math that Programming is. Algorithms are represented by programs. Representing programs is domains in itself and roots from byte representations in assmembly to high level programming languages (modern stack, punch cards in the old days). Building useful Abstractions is a core tenet of a notion of a useful program. This facilitates (already enabled by low level languages) interactions with high level programming notions, their analysis and manipulation/composition for further abstractions.
I'll be exploring both, high and low level, ends of this spectrum in this node cluster and will be documenting the purpose of their existence for the concerned context.
On a more epistemologically polymathic treatment of the notion of programming, checkout Polyglotism
2. Major Forks/Flavors
3. Minor Forks/Flavors
5. Stream
5.1. 0x223F
- reading up on local development practices with docker :
5.2. 0x2221
- reading the ultimate go notebook and not missing out on any of the reading assignments : have been reading a whole lot more than I've been writing when it comes to technical domains lately : plan on bridging down the gap over time.
- domain specific streams seem like the ideal generic dumps for my readings : like the data lakes of the whole operations.
- https://stroustrup.com/Software-for-infrastructure.pdf : reading about writing good software for infrastructure i.e. being efficient, reliable and doing justice to the hardware that one has.
- the way types are handled indicates the nature of a programming langauge
5.3. 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