MCP let's you hide secrets from the LLM

you can do same thing with cli via env vars no?

Yes, I'm using Dagger and it has great secret support, obfuscating them even if the agent, for example, cats the contents of a key file, it will never be able to read or print the secret value itself

tl;Dr there are a lot of ways to keep secret contents away from your agent, some without actually having to keep them "physically" separate

FWIW mise has a task runner built-in too.

How is that not a unit test?

I've hear people refer to it as an end-to-end test, where unit tests usually test a single class or function.

That's only if you subscribe to the London school of though, which results in a bunch of useless tests that are coupled to implementation details.

You don't need to retrain the whole thing from scratch every time.

For me it's because coworkers are pumping out horrible slop faster than ever before.

Slop is, by definition, AI generated. So ... no it didn't.

slop is not, by definition, AI generated. The word slop is from the mid 16th century, and its modern colloquial/meme use originated in 4chan in 2016. That's why we call AI slop "AI slop", and not just "slop".

Time to update your dictionary -

slop: "digital content of low quality that is produced usually in quantity by means of artificial intelligence"

https://www.merriam-webster.com/dictionary/slop

It is strictly this meaning I intended.

My guy, most people don't even know what nix (the package manager) is.

Time to get familiar then.

Yeah, the mojo pitch is so good, but I don't think anyone has an appetite for the potential fuckery that comes with a closed source platform.

Is an `EventEmitter` a framework or a library?

> Is an `EventEmitter` a framework or a library?

It is best described as a pattern implementation (observer / pub-sub).

Example Node.js EventEmitter usage:

const EventEmitter = require('events');

emitter.on('data', handler);

emitter.emit('data', value);

-----------

You explicitly instantiate it. You explicitly register listeners. You explicitly emit events. It does nothing unless you call it. There's no lifecycle, no main loop, no required structure.

EventEmitter is not a framework because it does not define application structure. It doesn't own the program's control flow. It doesn't decide when your code runs (beyond callbacks you register). It does not enforce conventions or architecture.

People sometimes call it a framework incorrectly because of two sources of confusion:

1. Callback-based APIs feel like inversion of control. But this is partial IoC, not framework-level iOc.

2. It is often embedded inside frameworks. Examples: Express routes, React synthetic events, Electron internals.

A library. It doesn’t define how you structure your application in any way.

Neither. It's an implementation of the interface in question.

LSP supports refactoring commands

But Claude Code does not, which is the point you have missed