williamscs

Super useful!

Official docs: https://docs.gitlab.com/ci/jobs/job_logs/#custom-collapsible...

Sounds a lot like Mr. Meeseeks. I've never really thought about an LLM's only goal is to send tokens until it can finally stop.

OSS isn't anti-alternative at all? Just because you don't pay for the software doesn't mean there's no competition.

Even well-established software can have meaningful alternatives. Look at ripgrep. While it hasn't replaced grep as a distro default, it's still being used by folks that find it a better solution for them.

On Mac, I've enjoyed kap.

https://getkap.co/

Hi! Just wanted to let you know I'm getting a 500 error on your docs page.

https://docs.odigos.io/

Probably the ability to recoup the cost with a subscription after sale (or one-time purchase like FSD). Lower the cost to get into as many homes as possible, then at least a few folks will pony up for it.

I'm not sure if you purposely mentioned Nebraska only for the xkcd meme or because you knew the Air Force Weather Agency is based in Nebraska.

https://www.af.mil/About-Us/Fact-Sheets/Display/Article/1045...

When I worked for Northrop, they offered a "9/80” schedule. Every pay period, you would work 80 hours in 9 days. Monday thru Thursday, you would work an additional hour (so 9 total), then have every other Friday off.

I used mercurial at one job and my experience was that the day-to-day differences were largely philosophical, especially if you primarily interact with VCS through your IDE, like me. Mercurial’s CLI API is supposedly cleaner, but I hardly interacted with it.

Mercurial has immutable history, so no squashing commits, no deleting branches, at the time I was using it there was no amending commits, in fact reverting a commit doesn’t even come enabled out of the box! Some folks loved it; no changing history, everything documented as it happened. We practiced trunk based development, so no branches except for hotfixes, so there wasn’t a lot of sprawl.

Ecosystems largely don’t support mercurial, so that’s definitely a consideration. Since Merge Requests and feature branches are largely practiced now, I feel like there’d be a lot of noise in a repo if folks used mercurial.

I don’t particularly miss mercurial, personally. I’m less into “pure” workflows and forcing behaviors. I think git is super flexible and generally practical and I’m overall pretty happy with it.

That's what Terraform pretty much is. All it does is manage a graph of dependencies/resources and then relies on a provider, which implements the CRUD.

Not super familiar with Hashicorp's other product Nomad but I'd think it have a similar approach, but more of a continuous lifecycle check?

Maybe it's an odd-number issue with the Pixels? My wife is using my old Pixel 2 with reduced battery life, but otherwise no issues. My Pixel 4 XL is still working great.

But does switching to using canvas solve that problem?

Martin Fowler has called his website a "bliki" (https://martinfowler.com/bliki/WhatIsaBliki.html).