The complete release log for the ⚒️tullyelly persona.
141 releases · Page 2 of 8
About a month ago I asked the bot how many words I've written on the site......and then forgot about it. I stumbled upon it again today, asked for updated numbers, and then requested a summary be produced. This is that summary:
I've published 322 Shaolin Chronicles containing 115,551 words.
I found a bug in the volleyball portions of the site. Maybe one day I'll fix
it. Maybe I'll never think about it again.
I love you all the same.
Does anyone remember prettylulu around here?
Oh, look who it is!
It's a check the box to say I did it kinda day. Sickness continued.
All that to say I got myself sick this weekend. Could have been travel, a young kiddo, an older kiddo, or maybe just a vomiting dog.
I should probably get some rest tonight instead of what I wanted to do next.
I appreciate your patience as you undoubtedly waited for me to either say or link to the title of this lastest chronicle. It's even more fun for me when what I'm about to write is not true in the moment I shared with these words, but will be true in the moment I published the chronicle.
Point being......I ain't in Kansas no mo, toto (wolff?). lulz
I did a bunch of other stuff and also ran out of time. We'll close with one final photo of my evening instead.
I don't really want to be here. 🫠
I travel for work this week and the anxiety leading up to something like this is super duper annoying. New people, new places, familiar people, different places, and then lord knows what.
I don't like it. It's never gone.
Acceptance is the goal.
Upon returning home, we received a surprise visit from fern. He was in a super nasty mood today. Agitated and all kinds of wound up.
He was so needy in a strange way that I didn't get much in the way of project work done because of it.
Hello nasty. 🫠
If you made it this far, you are one of the sickos.
scroll amendment · 2026-07-302 out of the last 3 days there were bugs that preventing photos from showing up. This is because I stopped giving a fuck briefly, and didn't test anything before hitting send. Send it. Ya dig?Oh, and PS for the real sickos......I found my favorite purple tape and here's the two photos where busted at some point:
I have no excuse tonight. There's power, just no will to go with it.
I didn't get to spend any time with the homie today either. He was pretty sad about it.
Power came on again late last night and we took it for granted again......right up until it went out again tonight. It went out just as I was about to get to some stuff I would log here.
Alas, I fell for the okey doke and we packed up our perishables ready to take up residence at lulu's. It's about time she carried her weight around here and took us in for once. 🫠
And then? The power came back and here I am. Blogging to tell you I won't be blogging againt. Circumstances beyond one's control.
Shouts to mom for the assist.
I'm going through it this week. Can you tell?
Not literally.
Except where I mean it.
After my besties both left, I created a way to link directly to any individual ReleaseSection. I had intended for this specific section to be done today so I could link to the finished product, but alas, I got sidetracked on a few other missions. The work there will continue tomorrow.
Cool new functionality though!
Iterate.
I needed to commit some code this week, so cipher took all of three minutes and fifty-one seconds to the following. Check out all of the stuff I track for no good reason (italicized in cipher's voice):
Implemented standardized table search across the clearly matching CardAttack directory tables:
Added a shared TableSearch component and filtering hook. Search is case-insensitive, covers relevant row fields, updates mobile cards and desktop tables together, and announces result counts accessibly. Homies’ legacy inline search logic now uses the shared implementation.
Ranking, Hall of Fame, detail, summary, and admin tables were left unchanged because they use different data or interaction contracts.
git diff --check passedNo dev server was started.
Quick break for some code that I've been sitting on related to some of my favorite people: TCDb Trade Partners.
The next deal with mfreeman showed me a good opportunity to implement it and if you click the previous two links you will find the boilerplate starting point for another wing of my systems.
Hey bot, please summarize all changes made today for our audience.
Today's content will be kind of in order, except where it isn't. Which might be mostly. Guess we see where the day takes me from here.
I have less ambitious expectations out of my personal quests these days. As an example, I'm just trying to commit a minimum of one code change per week. The great re-org and all those cardattack time-sucks make it hard to be here, there, and everywhere else all at once.
Point being, today is that weekly deadline to deploy some code (other than these chronicle, which is a different kind of code, so it ain't like I ain't even when I ain't). I didn't know what that would be until 30 minutes ago when I was cleaning up chronicle.
While I'm not getting forcably removed from my bed, I'm learning that I should ask cipher to make more small changes to the site. Counterpoint: I'm busy. Shut up me. We're doing just fine around here.
Point being, in the past 30 days, the number one page in terms of views is . My tiny brain thinks this is because a small subset of folks have this page bookmarked and use it as an entry into my daily mental disturbances. AKA chronicles. 🫠
Constraint fixed. 🫠
Iterate.
Nothing on this site is intentionally forever. I might revisit today's content fifteen years from now - with a bit of luck. I invented the ScrollAmendment component so that if something does change, especially something that I change, can be noted. A blip in the matrix recorded. So many words to say that cipher has now updated this component to require a date to be passed.
I wrote this:
They did that:
Sharpening these:
Yes, lulu: I know what this means. And what it did in two minutes, 12 seconds was incredible. When it found scroll amendments without a date and used the Git history to solve a problem I never even hinted at - fun to watch live. It would have taken me a half day to accomplish what it did before I could even return with a fresh cup of coffee.
Second point being, that content wasn't there when this was originally released. Now with dates!
Whether that is true or not, whenever I need to find the published version of an old chronicle it's a pain in MY ass to find shit so I gave the page a facelift. It now includes a search function to please me.
Along with me pleasing me, the page has been updated to fit the more current sitewide stylings and I also snuck in a quality of life improvement for anyone that uses this page to get to the latest chronicle.
After said QOL improvement: the most current post is the first actionable portion of the new landing page. Click the link, jump into the latest chronicle: stay a day one stan.
Me-to-me:
You don't need me to show the way, love
I'm also quite lazy so I turned this command......
......into this command......
It's smart enough to do other things so that I'm prepared for edge cases and saves me from excess typing just about every day.
Layman(lulu)'s terms: it's easier for me to link images within these chronicles.