thinkxl

I'm a happy Dagger user. I use it heavily for GitOps, but I never thought to use it like this.

Definitely joining the Discord server.

I've had a good experience with Woodpecker CI. I've heard that installation and integration with ForgeJo isn't easy, but I deploy everything to my homelab using Dokku, where I push a Dockerfile, mount a volume (on setup), and it's good to go.

I assume this isn't optimal for a business setup, but for personal projects, I don't miss GitHub Actions at all.

.env files are a different use case than config files.

You can use them together. Config files provide configuration to the application. The config file can read environment variables, so you can deploy the same code across different environments, e.g., your local computer, staging, and production.

Then, each environment will provide system-related configuration, e.g., `DATABASE_URL`.

With this setup, the same code will work on each environment.

Now, .env files should live only on your local machine; on any other environment, they should be set differently, not in files.

The .env file is a convenience, but not the only option for environment variables, nowdays you can use 1Password too.

One of the greatest things of the Vue community is that they are not dogmatic about a technology choice. They welcome everyone, and proof of that is that they are building tooling that benefit everyone not only their community. So, we can switch over to Vue whenever we want. I personally prefer React and I'm super grateful of Vite and their ecosystem.

If React implodes because of bad architectural decisions, Vite should fork it.

It's crazy that the best React DX is provided through Vue's community projects.

I came to reply this. They have been building very cool CLI projects and those projects end up composing new bigger projects. This is their last one (That I know of) which use most of the other projects they created before.

They didn't do it flashy for this project specifically (like Claude Code, which I don't think is flashy at all) but every single one of their other projects are like this.

I agree. You describe how it happens; however, I still don't find a justification for these:

- rely on competent people directly under the executive to guess what that means

- after-meetings in which everyone tries to interpret the executive’s feedback

- the executives are busy and hard to get access to

Imagine having a riddle as feedback in which people from different backgrounds and cultures gather to decipher a meaningful direction.

Well, the answers to your questions don't sell books, right?

Additionally, the explanation might work for the exec asking the question, but not for others.

I don't like that executives don't have to put in the effort to communicate their concerns and put pressure on the people who already have the pressure of researching, validating, and presenting the solution.

I'm probably going deeper than I should. Still, if the executive asking the question isn't technical, he could direct the question to the executive who's supposed to have a technical background that earned their position in the company. You know, people making decisions should have an understanding of what they are building/selling.

i don't want to be the "get off my lawn" person or "old man yells at cloud," but i couldn't get to what the tool does because the landing page is so overwhelming with colors, the background, the borders, things moving around.

the CTA buttons across the site are inconsistent in shape, form, and color.

the text color in the footer has awful contrast, so it's hard to read.