Why I askedI wanted to understand how speed, energy use, and a changing range estimate related to each other.
What I learnedI learned that air resistance rose quickly at highway speeds. Lower speeds could extend range, but the gain depended on conditions. A steady arrival estimate could already reflect adaptation to lower energy use.
Why I askedI wanted to understand what isolated desktops actually solved. I followed the idea through the choice of hardware and operating system.
What I learnedI learned to separate isolation, capacity, supervision, and scheduling. Two agents could have separate desktops and still conflict while changing the same website account.
Why I askedI had assumed a classifier's main job was filtering information before a larger model saw it. I wanted to understand what changed when software owned the workflow.
What I learnedI learned to separate model judgments from the code that stored state and chose actions. A more detailed prompt still left the model in charge; explicit state and rules made parts of the process inspectable and testable.
Why I askedI wanted earlier experiments to improve later advice. I had been thinking about what an assistant should remember as its models became more capable.
What I learnedI learned that a useful memory needed links from an idea to an action, an observed result, and a later decision. Saving more notes did not close that loop, and missing measurements could not be treated as failed experiments.
Why I askedSomeone posted that every developer needs a cheap always-on mini PC for agents. I already run agents that depend on local tools and logins, and I wanted to know what a second machine would actually buy me.
What I learnedAn always-on box keeps agents alive after I close my laptop, and cloud coding agents already cover some of that for self-contained work. The painful gap is syncing API keys and CLI logins onto the second machine, not buying the hardware.