notsirius

yeah that makes sense - think i blended your parent comment with jbs789's reply to it about feedback to the cook

I actually think it’s more about the emotional maturity to cut to the chase and address someone’s actual concerns.

I’m a big fan of bluntness / honest feedback, but it can still be done very rudely when inappropriate

like the svp observed that the ic was saying the details, not because the ic needed to share them, but because the ic was anxious that the svp didn’t view them as competent. So the svp cut to the chase and addressed that directly

For your food example, a host might ask if you like the food - not because they care about their cooking skills - but just want to make sure you had a good time. So, saying you don’t like the food and giving cooking suggestions would need to be accompanied by some reassurance that you still enjoyed their company or beautiful home or something. Otherwise it’s still rude

you'd probs want a commit hook for that

have worked in analytics for a while. Engagement is a very broad category. Not all engagement metrics are toxic. For example, daily active users is healthy for a business to measure and is engagement. Commenting on Hackernews is engagement. Meta also has a wide range of engagement metrics - not all of which are problematic

Ah - so youre running in direct mode then? https://docs.docker.com/ai/sandboxes/workflows/#direct-mode

Def makes integrating easier but I try to avoid using direct mode for security (exposes .git folder, though there's probs a better way to protect it by disabling hooks or something)

Sometimes is up to date. When its not - you can just use a kit and add command: install : codex update https://docs.docker.com/ai/sandboxes/customize/kits/

"login multiple times for each sandbox"

I've been using sbx for a bit now, and there have been some old versions that had this problem, but haven't had this problem in a while when using secrets https://docs.docker.com/ai/sandboxes/get-started/#authentica...

This was added recently https://docs.docker.com/ai/sandboxes/usage/#multiple-workspa... ` sbx run claude ~/project-a ~/shared-libs:ro ~/docs:ro`

Also had this pain point as an sbx user. Given the risk this adds to the host, would be great if there were more docs on how to setup kits to make it safer (e.g. disable yolo mode).

Yup https://github.com/docker/sbx-kits-contrib/tree/main/pi https://docs.docker.com/ai/sandboxes/customize/kits/

Ooh - can you share more about your setup with superset? I tried getting it integrated with superset a while ago with no dice.

been using this for a while - works great! Has also had a lot of updates over the past year so worth checking out again if you tried it a while ago

are you saying that all of the programmers you’ve met in real life have automated their work away and are coasting while waiting for their bosses to fire them…?

…if not, they’ve found developer work that ai can’t do yet, no?

does claude desktop actually solve this issue? I’m on mac and use docker sbx to solve this https://docs.docker.com/ai/sandboxes/get-started/

Are we sure they’re not secretly training on private data via some loophole…