afarviral

I want the autonomy but local models of the size I would have the means to host wouldn't be capable enough. What usecases tend to suit these smaller models that tend to produce incorrect or otherwise flawed responses often? Could they work for anomaly detection and what would a rough architecture look like?

Yeah I've just gone back to hand coding everything and pretend AI doesn't exist. Seriously. It doesn't have any measurable impact on my productivity (since there's no meaningful way to measure it), and is slowly restoring my blunted research and reading ability. I don't need extra dimensions of tasks like deleting hallucinations, and get to have 100% personal agency (other than when collaborating with colleagues of course).

There are so many bold claims in this article. I think this deserves taking with a grain of salt.

What if the new release which contains the fixes has new dependencies and those also have new dependencies? I assume they have to Frankenstein packages sometimes to maintain the borders of the target app while still having major vulns patched right in stable.

I'm some ways I'd argue the UI of darktable is ahead of its time and fairly snazzy. It's just a much more sophisticated tool. What is one thing about the UI that specifically feels dated? Burried maybe, but dated?

"has me on antidepressants, anti-anxiety meds, and mood stabilizers"

Have you considered getting a second opinion on your meds? That sounds like a lot if that's 3 separate medications, and not without side effects which may be contributing to a lack of interest in interests.

No, nothing exists in a vacuum.

Why is that? I also used to hold this opinion, but we use it for 99% of our production deployments (or k8s where we need it) and it has been maximally reliable, and super convenient for fault-finding. Maybe I didn't understand your take.

Looks really cool. I like the style :P

I hope it takes off!

I noticed it's a bit slow after clicking the title of a thread, unlike HN which is a bit more instantaneous. It wouldn't be a problem but it's the main interaction so worth double checking/optimizing.

Very cool. I was thinking about something similar. In response to those saying it is not in the true spirit of Zettelkasten, that's probably fair, but this could easily incorporate your own notes/thoughts too, but you get to keep a convenient summary of the content you collected from outsite yourself. I think the other commentors may have missed the fact that while the LLM substitutes you, it does try to create new insights during the "Thread" part of the core loop.

How can you maintain that much stashed code between commits? I assume you refer to it and manually code using the "mess" as inspo? I don't know stash works much deeper than stashing things I might need later so I can pull from remote.

Huh I must have just got in on time as I set up a local account about 12 hours ago following a tutorial.

Would it not be more direct to do gas exchange with blood?

This is interesting, and I'll try to remember to give this a go next time I'm tempted to patch something from the standard library, but...

The README mentions 3 scenarios that this might be preferred over, but not the fourth which I regularly do: Create my own functions/classes that are composed from the unchanged modules. E.g. a request_with_retries function which adds retry logic to requests without the need to monkey patch. I regularly use decorators as well to add things like retries.

For more complex scenarios Modshim might win out, as mentioned in the understated section of the README "Benefits of this Approach":

> Internal Reference Rewriting: This example demonstrates modshim's most powerful feature. By replacing requests.sessions.Session, we automatically upgraded top-level functions like requests.get() because their internal references to Session are redirected to our new class.

> Preservation of the Original Module: The original requests package is not altered. Code in other parts of an application that imports requests directly will continue to use the original Session object without any retry logic, preventing unintended side-effects.

What I think this means is Modshim lets you really get in to the guts of a module (monkey-patch style, giving you god-like powers), while limiting the damage.

I wasn't planning to renew so soon. Then they dropped this bombshell and I impulse bought another 12 months subscription. So far I'm digging it and looking forward to composing some spicey chord progressions.