In the garden, and RAIN!!! (2)
POSTED BY: SIGNYM
UPDATED: Monday, September 7, 2026 11:50
VIEWED: 338648
PAGE 830 of 834
The reason why I suggested adding an identifier to every session is to allow the AI to find EVERY session. That, plus revision numbers, might allow you to reel back to a soecific session and version.
-----------
"It may be dangerous to be America's enemy, but to be America's friend is fatal."- Henry Kissinger
NOTIFY: Y | REPLY | REPLY WITH QUOTE | PERMALINK | TOP | HOME
I think our heat must have rolled your way, SIX. We're enjoying 85°F weather.
-----------
"It may be dangerous to be America's enemy, but to be America's friend is fatal."- Henry Kissinger
NOTIFY: Y | REPLY | REPLY WITH QUOTE | PERMALINK | TOP | HOME
Quote:
Originally posted by SIGNYM:
The reason why I suggested adding an identifier to every session is to allow the AI to find EVERY session. That, plus revision numbers, might allow you to reel back to a soecific session and version.
We've just been calling each session by a number. S1 through S12 now.
The thesis document has become the timeline of all the things worthy of note, whether it was additions to the code or changes to the behavior in the blueprint. Each session "knows" who it is from the beginning when I initialize it when saying something along the lines of "Session 11 died, you are Session 12", and it remembers this and adds anything to the history using their identifier.
We don't upload entire chat histories in bulk. The size of them vary greatly, but they've been anywhere from around 500kb to 2.2MB, and they contain a lot of conversational bloat and stuff that the current session just doesn't need. The blueprint is only around 20kb right now, and the thesis is about 35kb.
They wouldn't be able to roll back to a specific number for a version of the code or parts of the code outside of the current session, other than rolling back to the exact version that I give them in the beginning of a session. This is simply because they don't have that information (unless I give it to them later).
When a session is initialized, it is directed to immediately create an Initial Save State, which is a pristine version of the codebase, thesis and blueprint documents from the end of the previous session. At any point I can initiate "Save State 1", 2, 3, etc. You don't want to load too many of these up without clearing them out along the way though, because it causes a lot of bloat on the server side. (I've been told this, but I've had as many as 4 or 5 save states created in a session before I started culling them).
I've only ever rolled back to a Save State once before, when things got really jacked up. The problem with the save states is that I don't want to allow it to have free access to create them whenever it feels like it or it does it all the time and if that bloat really is a problem it would happen almost right away. If I don't remember to make one fairly frequently though, I could end up losing a lot of good stuff we did if I were ever forced again to use one. I should probably add a rule to make the AI prompt me to make a save state every 2 hours or so, although with our new revision numbers on code changes it's probably not as important as it used to be.
What is cool is that it's pretty good at figuring out what we were trying to do with the codebase in previous versions.
I told you that this session had cut our codebase down to 33kb from a high of 56kb. That was true. But unfortunately a lot of things it thought was just "garbage" wasn't garbage, and we ended up adding most of it back. Along with the additions of around 5 feature requests this session, we've added back so much (in a different and more efficient way) that we're back up to 51kb now. But when adding back things that we had already figured out in our old spaghetti code, when provided with old code, the new session is able to say "oh, I see what you accomplished here. This is how we're going to do it now".
That's an annoying way to spend a day for sure, but there's no arguing that the codebase is much better for it. As I mentioned, the code will run about 5 times as fast as it used to and you don't hear that old hard drive chugging hard the whole time anymore. Everything works as it did before (and better than ever) now except for the tweaks we made to automatic processes that enforce certain thresholds for human operator review. Right now that code is still far too aggressive, and I need to get the guardrails back in now.
Oh... and I've had this session reorganize our historical documents. The blueprint now has an additional section that
NOTIFY: Y | REPLY | REPLY WITH QUOTE | PERMALINK | TOP | HOME
Quote:
Originally posted by SIGNYM:
I think our heat must have rolled your way, SIX. We're enjoying 85°F weather.
-----------
"It may be dangerous to be America's enemy, but to be America's friend is fatal."- Henry Kissinger
Uggh.... The high today is 97!!! On September 2nd!!!!
Gross.
--------------------------------------------------
Those who dance always seem crazy to those who can't hear the music.
NOTIFY: Y | REPLY | REPLY WITH QUOTE | PERMALINK | TOP | HOME
Out soon on what has by the look of it a wet morning. Need some groceries and my area is sitting at 66F. Suppose to get rain today.
NOTIFY: Y | REPLY | REPLY WITH QUOTE | PERMALINK | TOP | HOME
All done for today and missed the rain by half an hour.
NOTIFY: Y | REPLY | REPLY WITH QUOTE | PERMALINK | TOP | HOME
Mah jong in the morning in the rain.
NOTIFY: Y | REPLY | REPLY WITH QUOTE | PERMALINK | TOP | HOME
Man...
I just got scammed by Scamazon.
Last night I realized that I was out a working coffee maker and needed to make an emergency purchase.
The last one I bought was the absolute WORST POS coffee maker I've ever had, which was an Amazon Basics branded unit on sale for less than $20. Four and a half star rating too! Whoooooo!
The thing had the shittiest pot with the thinnest pouring spout imaginable, so unless you spent a half a minute slowly pouring the thing into the back, you were liable to spill 10% of the water outside the unit. NUMBER ONE GRIPE ABOUT COFFEE POTS, IMO.
Then it wasn't long before the spring mechanism that allows you to pour a cup while the pot is still brewing just snapped right off. I was able to get it back in using some twist ties and it kind of worked, but not really.
And last night I noticed my coffee had gone cold while the light was still on, and later when I went to make another pot it was just dead. Nothing but the light worked.
So I sprang for a $30 Black and Decker this time.
I open it up today...
IT'S THE EXACT SAME GODDAMNED MACHINE.
I'm not joking. The ONLY difference is it's got the Black and Decker branding on the maker and the pot instead of Amazon Basics.
I'm glad that dude burned their warehouse down earlier this year.
Fuck Amazon.
--------------------------------------------------
Those who dance always seem crazy to those who can't hear the music.
NOTIFY: Y | REPLY | REPLY WITH QUOTE | PERMALINK | TOP | HOME
It's all made in China, no matter whose name is on it.
We bought Agilent gas chromatographs and mass spectrometers for our lab. We could tell which ones were made in China bc the serial # began with a "C" (as opposed to a "U") and there was ALWAYS something effing wrong eith the China units! Either the flow controllers were defective or the internals were dirty with trace machining oil and needed two weeks of baking our before use.
You'd think companies like Agilent and Krups would enforce better QC tho!
-----------
"It may be dangerous to be America's enemy, but to be America's friend is fatal."- Henry Kissinger
NOTIFY: Y | REPLY | REPLY WITH QUOTE | PERMALINK | TOP | HOME
Turns out, even a good deal of the internals of our voting machines are made in China.
The machines that have internet connectivity.
Who knew?
--------------------------------------------------
Those who dance always seem crazy to those who can't hear the music.
NOTIFY: Y | REPLY | REPLY WITH QUOTE | PERMALINK | TOP | HOME