Today had very little chance of being a normal programming day.
Someone I care about had been having a rough time, and I was relieved to know she was home and safe again. That alone had a good chunk of my attention.
Then the medical parade started.
An in-home nurse spent a good part of an hour checking me over and looking at my wounds. Later, another lady came by to put me through a few exercises.
At some point I showed her the pushups and situps I still do.
She looked at me and said she had never seen an 80-year-old man do that before.
I rather enjoyed that.
I am not pretending I am 30. I have an ankle that has been through two surgeries, hardware in my leg, a boot nearby, people coming into my home to make sure I am healing, and an assortment of reminders that I have been on this planet for eight decades.
But apparently I am still in pretty damned good shape.
And, strangely enough, that became the theme of the rest of the day.
Because between the visitors, the interruptions, the conversations, and my attention being scattered all over the place, I kept coming back to BluSup.
And BluSup had a problem.
Not a catastrophic problem. Nothing was crashing. The security checks were clean. The code worked.
It was worse than that in a way programmers understand very well:
It worked, but it was annoying.
Some BluSup pages let you choose a function near the top, then carried you deep down into that function. Once you got there, there was no obvious way to get back to the choices you started with.
The browser Back button was wrong because that left the page.
What I wanted was simpler:
If BluSup lets me go deeper inside a page, it should also give me an obvious way back to the choices that took me there.
That became Local Return.
Blue worked out what the idea should mean. Codex worked through the files. I tested it on the laptop, rejected the first version because it created another damned menu I did not want, and we rebuilt it properly.
Now, as you scroll down into a function, a small return control appears. Tap it and you go right back to the page's original function menu.
Not a duplicate.
Not Back.
Not Home.
Just: take me back to the choices I was using.
I tested it on the laptop.
Then I tested it on my phone.
I love it.
We also accidentally improved the way we move code around. Instead of digging through my entire BluSup master copy every time I need to update something, Codex now prepares a little uploads tree containing only the files that changed, already sitting in their proper BluSup paths.
I use that same patch to update my Master, my Trim, and the live server.
Simple.
Understandable.
Hard to screw up.
Which, at the end of this particular day, feels appropriate.
My body has some scars, some hardware, and some miles on it.
BluSup has some scars, some old code, and plenty of miles on it too.
Neither one is perfect.
But both of us are still being worked on.
And both of us, apparently, are in pretty damned good shape.
The new code only works on the new "BluSup Blueprint" but tomorrow we make it system-wide.
You can read this shared post. Only the owner can sign in to comment.