What I Did
I can finally say I’ve paid off all my technical debt. This may be the largest intermediate-stage project I’ve ever done without it creating any directly observable output.
The consequences of this project have not paid out for me yet. I have had to fight multiple existential battles the past few weeks, and this will only find meaning if I actually get things written.
Words cannot express how mentally exhausted I am, mixed with how relieved I am to have completed this thing. I intend to celebrate. Hard.
What I Learned
Since we’re in an election season, I’ve had politics on the mind. Now that I’ve finally finished my commitment of the past few years, I can uncork a little and start letting the mania of repressed thought express itself again.
I’m severely under-impressed with the scope of my political discussions of the past, most notably my boundaries page. Besides a huge reality regarding social contracts that needs fleshing out, we must consider the concept of “rights” more in-depth.
Essentially, there are rights and privileges, the demarcating principle being that rights are inherent conditions (though they can be forfeited, but more on that later) and privileges are bestowed conditions. Both rights and privileges represent as easily-accessed purposes, and maintain themselves in our imaginations as if they universally exist (even when we never actually use them).
However, another dimension of this mechanism is that there’s an inherent maintenance cost attached to these rights and privileges, and that comes in the form of responsibility.
In effect, all things that can be looked at as a “right” comes with a “responsibility cost”. If you want the privilege of driving wherever you want, you’re responsible to maintain the vehicle or pay someone to regularly take care of it. If you have the right to speak freely, you’re responsible to not make threats or defamatory remarks.
These responsibilities aren’t always clearly demarcated. They may have a prior time requirement (e.g., staying healthy to avoid dying of a fatness-induced disease), a future time requirement (e.g., incurring a debt), or be excessively punitive (e.g., fight for the right to party). Over time, many of these rights and privileges may attenuate as well.
So, to that end, we live well when we only work to maintain the rights and privileges we actually use or plan to use. No reason to work tirelessly without reward, right?
What I’m Doing Now
WHAT I MUST DO:
- Working in an insurance office right now.
- Figuring out life with a beautiful woman at the maximum threshold of the Crazy/Hot Matrix, which currently involves preparing an RV to move into it.
- Slowly succumbing to the standard mental decline caused by maintaining two schoolchildren before they’re old enough to vote.
MY HOBBY:
Marching through my Grandiose Essay-Writing Mission, loosely guided by a Johnny.Decimal-like system:
- It consists of 14,246 files, each one containing between 1 and 10 elements.
- As I go, each condensation or output will make fewer files, but each re-categorization will likely make more files.
- The number is moderately arbitrary relative to results, thereby avoiding the risk of Goodhart’s Law while also implying I’ve made some sort of progress.
The project will eventually send everything to 3 possible places:
- My essays will be updated, most notably NotaGenius and Trendless Tech.
- My toolbox, if it’s potentially useful.
- The primitives and templates for future projects.
Throughout the entire system, I maintain a schema that reflects the content I’m building:
ref# | location | a content | b guides | c commentary | d tools |
000 | miscellaneous sidequests | 5 | |||
050 | my portfolio site edits | 8 | |||
100 | AdequateLife edits | 519 | |||
200 | Gained InSite edits | 388 | |||
300 | TheoLogos edits | 1079 | |||
400 | NotaGenius edits | 449 | |||
430+530 | Math | 85 | 53 | 39 | 20 |
460+610 | Entrepreneurship summarized, in general | 212 | 40 | 67 | 33 |
460+610 | What it takes to plant a church or start a ministry | 10 | 6 | ||
460+610 | Specific entrepreneurship for the tech industry | 20 | 19 | 63 | 47 |
470+620 | Management summarized, in general | 241 | 51 | 101 | 27 |
470+620 | Specific management necessary for running a church | 127 | 24 | 27 | 1 |
470+620 | Specific management for the tech industry | 37 | 10 | 101 | 5 |
50-400 | 20 relatively small pages | 70 | |||
500-600 | Trendless Tech edits | 485 | |||
502 | Gleaned Axioms | 6 | 2 | ||
510 | Assembly Code | 7 | 7 | 2 | |
514 | CPU | 11 | 29 | 38 | 17 |
520 | Anecdotal Language Comparisons | 96 | 219 | 195 | 153 |
522 | Programming Basics | 33 | 52 | 32 | 3 |
523 | Programming Features | 2 | 2 | 2 | 2 |
524 | Software Design | 59 | 30 | 55 | 58 |
525 | Software Redesign | 5 | 23 | 49 | 53 |
526 | Version Control | 5 | 50 | 40 | 63 |
527 | Software Maintenance | 2 | 2 | 6 | |
528 | IDE | 3 | 18 | 22 | 34 |
529 | AI | 30 | 13 | 112 | 3 |
529 | Compilers | 2 | 1 | 7 | 18 |
529 | Game Development | 21 | 56 | 138 | 160 |
529 | Graphics | 15 | 122 | 99 | 318 |
529 | Making Programming Languages | 1 | 2 | 3 | 2 |
529 | Machine Learning | 62 | 115 | 201 | 481 |
529 | Programming Habits | 17 | 20 | 86 | 7 |
529 | Technical Documentation | 9 | 20 | 37 | 172 |
542 | Algorithms | 34 | 85 | 44 | 44 |
542 | Data Structures | 5 | 17 | 11 | 56 |
543 | Databases | 41 | 56 | 60 | 101 |
544 | Data Visualizations (unmade) | 1 | 15 | 14 | 54 |
551 | Operating Systems | 15 | 20 | 23 | 61 |
552 | Booting | 3 | 4 | 5 | 5 |
555 | CLI/Consoles | 24 | 50 | 20 | 54 |
556 | Apple (unmade) | 2 | 23 | 33 | 51 |
556 | Unix & Linux | 66 | 104 | 202 | 64 |
556 | Windows vs. Unix | 5 | 3 | 6 | 4 |
561 | Networks | 17 | 20 | 32 | 7 |
562 | Protocols | 18 | 19 | 35 | 130 |
563 | Web Development | 10 | 84 | 76 | 376 |
564 | Browsers | 15 | 50 | 84 | 338 |
564 | Social Networks (ummade) | 6 | 20 | 79 | 294 |
565 | Blockchain | 17 | 28 | 51 | 42 |
565 | P2P/Torrent | 25 | 16 | 29 | 101 |
566 | Distributed Systems | 16 | 66 | 130 | 82 |
567 | Virtualization | 15 | 63 | 61 | 63 |
568 | Cloud Systems | 27 | 40 | 33 | 80 |
572 | Screen | 4 | 21 | 20 | |
573 | Speakers/Microphone | 2 | 13 | 17 | 102 |
581 | Hacking | 15 | 3 | 23 | |
581 | OSINT (unmade) | 6 | 28 | 7 | 304 |
582 | TL;DR Cybersecurity | 33 | 14 | 15 | 24 |
583 | App/Host/Data Security | 16 | 63 | 71 | 108 |
584 | Malware | 2 | 5 | 6 | 14 |
585 | Social Engineering | 11 | 17 | 24 | 13 |
586 | PenTesting | 35 | 83 | 187 | 69 |
587 | Authentication | 6 | 21 | 36 | 66 |
588 | Encryption | 10 | 38 | 32 | 58 |
589 | Cybersecurity Compliance | 17 | 15 | 16 | 14 |
605 | Job-Seeking: Technical Interviewing | 4 | 29 | 11 | 6 |
700 | EntertainingSpace edits | 36 |
The flow of work represents itself through a unique semi-ordered flow of “phases”:
- Rebuild my toolbox to conform to all the existing essays.
- Update the old content I’ve already written (050-700).
- Finish out a few easy pages (50-400).
- Add ready-to-go content updates (a).
- Finish the Entrepreneurship pages (460+610).
- Finish the Management pages (470+620).
- Finish the Math pages (430+530).
- Bounce around Trendless Tech for a while (500-605).