marwamc

hahaha love the spec comparison.

Also, can't wait to try this. I use a markdown-based notes/workplans/context workflow that works for the happy path but falls on its head for some edge-cases. Sometimes I have to abruptly stop a piece of work, and I might not get a chance to perform the post-work-item markdown notes ritual. If I'm resuming the same piece of work within 24hrs, it's relatively straightforward to remember what I was working on before the abrupt stop. However, sometimes it might be several days before I resume a work-item that was abruptly stopped, and in those cases, the context switchback feels like hair-pulling. This promises to reduce that pain somewhat. The last commit (usually a few steps ahead of the work-plan persistence ritual) becomes a recoverable checkpoint.

Picking a fight with the European labor unions was not a smart move in hindsight.

Backing AfD in Germany and calling them Germany's "best hope for the future" likely rubs the rest of the non-AfD polity the wrong way. He turned driving a Tesla into a political stance in Germany.

+1 for generating plans and then clearing context. I typically have a skill and an agent. I use the skill to generate an initial plan for an atomic unit of work, clear context and then use the agent to review said plan. Finally clear context and use the skill to implement the plan phase by phase, ensuring to review each phase for consistency with the next phase and the overall plan. I've had moderate success with this.

The split globally was ~54% hybrid/electric and ~46% gas. And author wonders why Porsche doesn't want to give up 46% of their Macan customer base? Or to be charitable, author wants Porsche to make that 46% Macan customer base, choose between an ev/hybrid Macan and whatever ICE alternative is available in that segment.

I see what's happening. I never validated those build artifacts... Thanks for the catch. Will rebuild notify you here.

When using AI coding assistants to refactor symbols across large codebases (6k+ files), developers face a binary choice: precision (LSP-based tools) or efficiency (grep/ripgrep). Shebe attempts to address this trade-off by way of a good old BM25 index, which is surprisingly fast and efficient.