Signal drop!
Relay (operand.online) is unreachable.
Usually, a dropped signal means an upgrade is happening. Hold on!
Sorry, no connección.
Hang in there while we get back on track
How Broken. (?)
I've been coding since my first year of high school, in 2005. No day in any of those 20 years has been spent on vibe-coding.
I imagine this solid run of legacy coding practice is going to end soon, because I do see the use of using LLMs for learning a new language, and I have a clear idea of my needs as I approach Rust. I'm on pace to make it through the Rustlings course this weekend, and the language has nice guard rails; I'm confident that I can guide the language model in proper directions.
Though there has been no vibe coding, there has probably been too much "crucial rush" coding. Readers realize I am eager to speak about my homelessness and nomadism, and these scenarios mean paring down the energy I spend on my cyber practice. Looking ahead now that I am in a proper camper home, I am making too many promises to be so lacksidasical any more.
I've recently circled back up with colleagues at Open Gov Hub, where I made my third or fourth round of promises to put case.law to use.
During the Congressional Hackathon -- with only a small break to heckle and curse Michael Johnson as he hoarded the stage and microphone to announce the House's succumbing to Microsoft's AI expansion -- I produced a scraper for the case law documents, and began to pull the corpus.
That scraper was made in [NuShell] and had been called domain.nu;
later on I pulled the logic into index.nu,
to add logic for processing documents
from the DoJ's Epstein document releases.
I acquired documents from the original dump,
breaking the case.law parser in the process,
and made no progress in processing either record corpus
in the ensuing weeks, wherein I was finding shelter from blizzards
and shuffling broken cars around (as legally as possible)
in three states.
So I've long been burdened by barely-good-enough processes that are simply holding me back.
The final mishap came last weekend, after I had spent four days in Baltimore during the blizzard, learning the basics of solar camping under layers of ice, and running to the camper for 15 minute spells before my fingers began to ache. I had a good many hours in the Baltimore Node, where I definitely kept from closing my eyes for too long on the new comfy couch. I also lost a good many hours of sleep in the process, and am realizing that recovery from sleep debt carries symptoms much like depression.
All the same, I finally packed up from Baltimore on Friday, and headed to George Mason University to join into the Global Game Jam. I had big ideas on Friday night about how to approach the theme, "Mask". As soon as I logged on, Saturday morning, I checked and could see that my domain failed to respond.
No one shall ever be able to say for sure if this is a case of corporate espionage or sabotage, because the small miniPC that I had been running my domain on from the minimal security on-premise shelf at Baltimore Node had once again had the power strip kicked or nudged or plucked. This seems to have happened on three occasions, always when I leave Baltimore after a long coding session. When I finally end up where I need to be, I find that the computer has gone offline, and I need to come to grips with my lack of a recovery option.
So, I've long been ready to upgrade.
Here's a quick summary of the problems and security lapses I can recall in this moment.
- [ ] crucial
.nucode has no specs or test harness. - [ ] the elixir app has no specs or tests.
- [ ] the elixir app has no solid road map.
- [ ] the MicroVM deployments can only handle a couple of hand-spun apps.
- [ ] the Resource Guide has broken and is basically disengaged.
- [ ] I am the only user; maybe I need to examine open-source auth
- [ ] miniserve has likely had no security appraisal.
- [ ] my main coding machine had passcode-based SSH access enabled for 1-2 months.
- [ ] I did nothing to sign my git commits.
There's more to say, tho I became distracted by making the diagram at the beginning of the page.
All of these problems began making me anxious, so I had to think ahead. Sorry if you read through all of this, some days simply is nice to spill your mind.
I do think that diagram's going to help tho, I'll see how much of that I can make use of next week.