What I Did
I went on vacation, so not much done relative to other updates. However, there’s still value in basic maintenance throughout each day. More on that in the next section.
More technical debt payments. I did use the time to divide-and-conquer the worst part of the pile.
What I Learned
Vacations are overrated, and I can’t say I like the concept anymore. Even though I wrote a guide on how to enjoy vacations and trips, I’m not sure if it’s healthy to take protracted vacations that surpass a week.
Since this status update blog post here is not catering to the largest possible demographic for a particular guide (and therefore omitting the daily dose of tinfoil that consumes my mind at least twice each day), I’ll give a dose of tinfoil that has consumed my mind a few times.
This is probably the most anti-American thing I’ll ever say, but I’m convinced that we are designed from a core phenomenology to rest every week. We don’t really know what made a “week” become a 7-day affair (and refuse to achieve scientific consensus that it had anything to do with ancient Jews), but we have always taken to the idea of 5–6 days of toil mixed with 1–2 days of recreation.
This is not a coincidence. Scientific studies have shown that one day off work every week makes us 150% more productive, which would make the guy who takes a solid weekend 7.1% more productive than the 7-day guy and the 6-day guy 28.5% more efficient than the 7-day guy. This also isn’t counting the quality-of-life improvements of not working (such as having actual fun).
Beyond thinking of The Twilight Zone’s A Game of Pool, this mechanism means that we ought to structure our lives around a type of rhythm: work lots and rest a bit to celebrate that work.
There are certainly times and places to work on weekends (e.g., moving), but the over-implementation of nonstop effort gets in the way of being able to sufficiently recover. It also stifles the creativity that could magnify our efforts even further (or, in some cases, clarify if our actions still reflect our purposes). From a mechanical perspective, its opportunity cost comes through pushing the system so far that it impedes the ability to assume more domains of influence. You can’t work more on Saturdays if you already work all day on Saturdays, after all.
This principle can be easily violated by pushing just a bit too far. For example, you may feel compelled to work because it can pay more money, or have a side hustle, or feel like you must take care of your kids.
Since we are creatures of habit, this week-by-week situation will follow us once we’ve curated it, irrespective of it being intentional or non-.
In light of that, the vacation is a violation of that weekly schedule. Instead of developing a routine in a new place to experience it as the motivation (and weekend) leads, the idea is that you go visit a place and drop shedloads of money on the local economy to be entertained.
The economic reality of the tourist town speaks for itself:
- That locale gets a rhythmic rush of people flocking there to see things, then they’ll head home after a set number of weeks with far less money than they had before. If you ask them, they’ll say it was “worth the experience”, but they’ll often return home with very little to show for that experience in relation to many other forms of self-improvement (e.g., fitness bootcamp, educational curriculum).
- In their wake, the town slowly conforms itself to rendering few services that don’t accommodate a seasonal rush of trivial purchases. The vendors sell overpriced products, to oblivious customers, who ransack the local region for baubles, and leave the vendors who win in the free market of chintzy knick-knacks with more money to scale the cycle.
Now, this isn’t to condemn visiting new places or exploring new regions: my complaint comes through the mechanism of blind abdication of all responsibility for the purpose of self-gratification. The I’ll-work-to-make-my-retirement-huge mindset has other issues, which I may touch on when the tinfoil strikes.
Instead, I propose a different mindset: the sabbatical.
We all travel through seasons, and taking a hiatus to travel or seclude yourself is a wonderful way to live for a time. Thoreau’s “Walden” arose from two years in that domain, and a shift in cadence is utterly critical for finding your own happy medium to live the good life that works for you.
The primary difference between a vacation and sabbatical is far less about what you do than how you do it and why:
- A vacation is driven by the desire to “escape”, while a sabbatical is driven by a broader range of desires: to “grow” or “learn”, or maybe to “relax” or “redefine oneself”.
- While a vacation is a fixed interval of spending and consumption, sabbaticals can often require working to earn a living, and may simply be an internship in something you’ve wanted to do.
The beauty of the sabbatical is that it’s also more cost-effective. Instead of toiling to save, with the hope of visiting a far-off land to escape the toil, you take a mini-version of the toil with you, and get some freedom to wander for a time.
This obviously isn’t for everyone, and I don’t even think I’m certain enough for this to be advice, but I know I’ve found something antithetical to mainstream Americana, so it’s still something I’ve learned.
The funny thing is that when you have children, the extra maintenance requirements almost make every vacation a type of sabbatical.
What I’m Doing Now
Marching through my Grandiose De-Hoarding Mission, loosely guided by a Johnny.Decimal-like system:
- It consists of 10,917 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 | 0 re-sort | a content | b guides | c commentary | d tools |
8540 | Math | 83 | 51 | 28 | 14 | |
8580 | Entrepreneurship summarized, in general | 53 | 202 | 34 | 54 | 17 |
What it takes to plant a church or start a ministry | 10 | 6 | ||||
Specific entrepreneurship for the tech industry | 20 | 17 | 51 | 46 | ||
8590 | Management summarized, in general | 108 | 203 | 51 | 78 | 17 |
Specific management necessary for running a church | 2 | 124 | 23 | 25 | ||
Specific management for the tech industry | 36 | 9 | 77 | 1 | ||
86013 | CPU | 11 | 23 | 26 | 8 | |
86014 | Assembly Code | 6 | 5 | |||
86021 | Programming Basics | 32 | 36 | 15 | 2 | |
86022 | Programming Features | 2 | 1 | |||
86023 | Software Design | 81 | 57 | 15 | 13 | 12 |
86024 | Software Redesign | 5 | 18 | 23 | 45 | |
86025 | Version Control | 3 | 37 | 21 | 47 | |
86026 | Software Maintenance | 1 | 2 | 6 | ||
86027 | IDE | 2 | 16 | 16 | 27 | |
86028 | Anecdotal Language Comparisons | 67 | 189 | 163 | 131 | |
86030 | Technical Documentation | 84 | 6 | 6 | 6 | 29 |
86031 | Programming Habits | 15 | 14 | 28 | 4 | |
86032 | Game Development | 66 | 14 | 30 | 75 | 53 |
86033 | Graphics | 261 | 10 | 26 | 15 | 56 |
86034 | AI | 30 | 11 | 76 | 2 | |
86035 | Machine Learning | 401 | 59 | 37 | 44 | 27 |
86036 | Making Programming Languages | 1 | 2 | 3 | 1 | |
86037 | Compilers | 2 | 1 | 7 | 14 | |
86050 | Algorithms | 32 | 78 | 33 | 27 | |
86052 | Data Structures | 5 | 17 | 10 | 45 | |
86053 | Databases | 32 | 31 | 45 | 48 | 56 |
86054 | Data Visualizations (unmade) | 22 | 1 | 2 | 10 | |
86060 | Operating Systems | 161 | 15 | 15 | 14 | 10 |
86061 | Booting | 3 | 2 | 4 | 1 | |
86064 | CLI/Consoles | 21 | 37 | 9 | 43 | |
86066 | Unix & Linux | 61 | 80 | 165 | 46 | |
86067 | Apple (unmade) | 1 | 17 | 3 | ||
86067 | Windows vs. Unix | 4 | 3 | 6 | 4 | |
86070 | Networks | 82 | 15 | 14 | 13 | 19 |
86071 | Protocols | 17 | 6 | 15 | 14 | |
86072 | Web Development | 199 | 6 | 33 | 20 | 134 |
86073 | Browsers | 301 | 6 | 12 | 25 | 33 |
86074 | Social Networks (ummade) | 207 | 1 | 8 | 28 | 57 |
86090 | Screen | 3 | 15 | 3 | ||
86101 | Speakers/Microphone | 2 | 10 | 13 | 59 | |
86110 | Distributed Systems | 63 | 8 | 8 | 18 | 12 |
86111 | Virtualization | 14 | 29 | 33 | 40 | |
86112 | Cloud Systems | 25 | 27 | 19 | 34 | |
86114 | P2P/Torrent | 90 | 24 | 6 | 10 | 8 |
86115 | Blockchain | 13 | 25 | 43 | 33 | |
86120 | Hacking | 14 | 3 | 17 | ||
86120 | OSINT (unmade) | 250 | 9 | 1 | 6 | |
86121 | TL;DR Cybersecurity | 33 | 6 | 6 | 1 | |
86123 | Malware | 2 | 2 | 3 | 1 | |
86124 | Social Engineering | 9 | 17 | 16 | 7 | |
86125 | PenTesting | 139 | 34 | 27 | 71 | 7 |
86125 | App/Host/Data Security | 72 | 16 | 31 | 17 | 22 |
86126 | Authentication | 6 | 15 | 30 | 57 | |
86127 | Encryption | 10 | 31 | 20 | 40 | |
86128 | Cybersecurity Compliance | 17 | 13 | 10 | 12 | |
86134 | Job-Seeking: Technical Interviewing | 4 | 26 | 6 | 5 | |
86170 | Gleaned Axioms | 5 | ||||
020 | near-totally unsorted | 184 | ||||
030 | current inbox | 62 | ||||
040 | need to revisit for various reasons | 64 | ||||
050 | grouped piles of stuff | 151 | ||||
060 | a pile of other weird things | 31 | ||||
070 | miscellaneous sidequests | 4 | ||||
100 | my portfolio site edits | 8 | ||||
200 | AdequateLife edits | 61 | ||||
300 | Gained InSite edits | 129 | ||||
400 | TheoLogos edits | 1062 | ||||
500 | NotaGenius edits | 216 | ||||
600 | EntertainingSpace edits | 34 | ||||
700 | Trendless Tech edits | 128 | ||||
750 | basic toolbox updates | 283 | ||||
800 | 13 small pages | 37 |
The flow of work represents itself through a unique semi-ordered flow of “phases”:
- Separate out the guides, opinions, and tools for each section (0->a-d): 2,674 left.
- Send grouped inbox items into their appropriate categories (020-060->100-86170): 492 left.
- Update the old content I’ve already written (100-750).
- Finish out a few easy pages (800).
- Add ready-to-go content updates (a).
- Finish the Entrepreneurship pages (8580).
- Finish the Management pages (8590).
- Finish the Math pages (180).
- I’m aiming for breadth, not depth. I don’t need to perform combinatorics in my head, but I do need to explain in plain English what the heck each math “thing” is, traced along a pseudo-path through the route of standard formalized education:
- Basic arithmetic
- Algebra
- Geometry/trigonometry
- Statistics
- Calculus
- Number theory, with a likely divergence into applied maths and game theory. Along the way, I’ll keep a jargon-resistant dictionary of the big math words.
- I’m aiming for breadth, not depth. I don’t need to perform combinatorics in my head, but I do need to explain in plain English what the heck each math “thing” is, traced along a pseudo-path through the route of standard formalized education:
- Bounce around Trendless Tech for a while (86013-86170).