literallyroy

Is the benefit of using a separate source that you can include images or something else I’m missing? Couldn’t you include context in the commit body?

Thank you for putting this in more generalized terms. I was just thinking replace AI with smart phone and this reads the same.

Unfortunately I think “good faith” goes away quick in the face of “bone shattering”

Smaller more frequent price increases is potentially better than larger less frequent price increases assuming they need the increase to stay profitable? Sounds like they didn’t predict the continued increasing costs.

The company I work for uses GCP and we preciously had intermittent CloudSQL connection errors for a few hours. We reached out and they resolved it after a day or so and said there was a minor incident but I don’t think it was ever publically reported.

Removing access to opus is pretty funny. At least they recognize it’s unacceptable and tell you to go get a refund.

The per-request model was pretty insane.

Hey this is exactly the pattern we have and the bugs we need to catch… yoink?

Yeah that is a “stacked” pr. The tooling is nice especially when have a larger stack and make changes to the first branch. Update refs + push all branches, same with merging and rebasing onto main.

It’s strange how easy it is to spot.

It’s a really cool shade of black though.

Does self-hosted support SCIM or something else easy to connect for automatic user provisioning? Or do yal do account creations manually?

The hypest of hypers seem to be those who are new to the field or were never responsible for long term outcomes.

Thanks. I was curious if someone was going to address the weird use of “CATASTROPHIC” to describe source maps being available for front-end code. It’s already public. Minified is better for the regular user, and should be in production, but it’s like by far the least problematic thing in this article.

Weird AI piece. There was a post a few days ago looking at historical sentiment of HN posts; it looks like someone slapped that info into an LLM and asked for a neat website.

Just read the “outcome” for Warp:

> … and became the most popular modern terminal. Login removed, telemetry made optional — every criticism addressed.

Insane

The go ecosystem is pretty good about being backwards compatible. Dependabot regular update prs once a week seems like a good option in addition to govulncheck.

I don’t see “Jobs done!” in the README :(

That’s a safer approach but will cause teams to need to test in two infrastructures (old world and new) til the entire new environment is ready for prime time. They’re hopefully moving fast and definitely breaking things.

Yep you can use your browser cookies to be authenticated and hit the slack api and get deactivated accounts. It’s wild and depressing to watch folks get deactivated in real time

On a big TUI kick recently and that looks incredible! Good stuff

Duckdb can read in json, so you can dump kafka messages into a file and filter with SQL

Depressingly bad argument that seems to say: we think it’s bad for children and adults, but we don’t ban it for adults so we shouldn’t ban it for children.

Thanks for the reply :]

That seems better as long as you can keep it standard across the team. I don’t usually check each commit when reviewing since frequent iterative commits mean folks change their mind and I’d review already removed logic when looking at early commits.

I’ve been scraping by on basic git usage so didn’t know about fix-up commits, that’s excellent.

I think the callout to squash first will be helpful (if your lots of commits aren’t good info themselves)

Delinia does this currently (I don’t think the fix is public yet).

You can run a python script to track the focused window every few seconds to identify what’s stealing focus.

Any recommendations for healthy family eating that doesn’t require an hour every day?

If it helps: they do not all work this way

It’s definitely some marketing, but way less than it could be. It recommends looking at the redis docs to build a reds client rather than the websites own tutorial/paid product for doing so.

I’m all ears for a better approach because squashing seems like a good way to preserve only useful information.

My history ends up being: - add feature x - linting - add e2e tests - formatting - additional comments for feature - fix broken test (ci caught this) - update README for new feature - linting

With a squash it can boil down to just “added feature x” with smaller changes inside the description.

What are you referring to? I may be missing a line from the article but it seems mostly focused around a lingering GitHub Actions bug and the direction of GitHub.

Was this messaging only shown in Australia? That seems incredibly misleading/a flat out lie.