bennine's comments

On: Zed now predicts your next edit with Zeta, our new open model

[bennine]

> but programming is an exercise for me, not just to make it work and call it a day.

The problem is that mid, upper management and execs don't much care for how we feel about it.

They are literally measuring who is using AI and how much and will eventually make it into an excuse for poor performance.

[markus_zhang → bennine]

Yeah I don't really mind using AI coding in work because it's boring as hell. And getting things done quicker is almost a virtue in the business world.

I should have clarified that my original comment is about side projects or serious software engineering.

On: Preview of Explore Logs, a new way to browse your logs without writing LogQL

[bennine]

Interesting. Will be following this tool.

There is a CLI tool with the same name that does something similar - https://github.com/johanhaleby/kubetail

On: A Simple Framework for Architectural Decisions

[bennine]

Thanks for the link

On: AWS releases Finch: An open source client for container development

[bennine]

What does this offer over Podman? Podman is a near drop in replacement for docker.

On: OKRs Are Hard

[bennine]

OKRs should be used to craft major projects and initiatives. They shouldn’t be used for direct performance evaluation.

They are helpful because they align effort and energy, top to bottom, in the direction most relevant for the business.

It goes without saying that if the organizational OKRs are messed up, then it’s messed up all the way to the bottom.

On: Sweet Shell: With Oh-My-Zsh, SpaceVim, Starship, True Color, and Demo Mode

[bennine]

Any differences over Alacritty? Seems like this has same exact main selling point.

[throwaway12223 → bennine]

glyph rendering

On: Dagger Python SDK: Develop Your CI/CD Pipelines as Code

[bennine]

Hey there, this looks interesting. What's the scope of this project? Is it meant to be closer to developers or do you see this being used in production?

How is progress of builds, observability, etc being tackled?

[shykes → bennine]

> What's the scope of this project? Is it meant to be closer to developers or do you see this being used in production?

Dagger is meant for both development and production. Note that Dagger doesn't run your application itself: only the pipelines to build, test and deploy it. So, although the project is still young and pre-1.0, we expect it will be production-ready more quickly because of the nature of the workloads (running a pipeline is easier than running an app).

> How is progress of builds, observability, etc being tackled?

All Dagger SDKs target the same Dagger Engine. End-users and administrators can target the engine API directly, for logging, instrumentation, etc. The API is not yet publicly documented, but will be soon.

We're also building an optional cloud service, Dagger Cloud, that will provide a lot of these features as a "turnkey" software supply chain management platform.