literallyroy

6 ms·

31.
by literallyroy 4mo ago
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.
32.
by literallyroy 4mo ago
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 publicall
33.
by literallyroy 5mo ago
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.
34.
by literallyroy 5mo ago
Hey this is exactly the pattern we have and the bugs we need to catch… yoink?
35.
by literallyroy 5mo ago
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.
36.
by literallyroy 5mo ago
It’s strange how easy it is to spot.
37.
by literallyroy 5mo ago
It’s a really cool shade of black though.
38.
by literallyroy 6mo ago
Does self-hosted support SCIM or something else easy to connect for automatic user provisioning? Or do yal do account creations manually?
39.
by literallyroy 6mo ago
The hypest of hypers seem to be those who are new to the field or were never responsible for long term outcomes.
40.
by literallyroy 7mo ago
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
41.
by literallyroy 7mo ago
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 popu
42.
by literallyroy 7mo ago
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.
43.
by literallyroy 7mo ago
I don’t see “Jobs done!” in the README :(
44.
by literallyroy 7mo ago
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.
45.
by literallyroy 7mo ago
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
46.
by literallyroy 8mo ago
On a big TUI kick recently and that looks incredible! Good stuff
47.
by literallyroy 8mo ago
Duckdb can read in json, so you can dump kafka messages into a file and filter with SQL
48.
by literallyroy 8mo ago
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.
49.
by literallyroy 8mo ago
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 log
50.
by literallyroy 8mo ago
I think the callout to squash first will be helpful (if your lots of commits aren’t good info themselves)
51.
by literallyroy 8mo ago
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.
52.
by literallyroy 8mo ago
Any recommendations for healthy family eating that doesn’t require an hour every day?
53.
by literallyroy 9mo ago
If it helps: they do not all work this way
54.
by literallyroy 9mo ago
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.
55.
by literallyroy 9mo ago
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
56.
by literallyroy 10mo ago
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.
57.
by literallyroy 11mo ago
Was this messaging only shown in Australia? That seems incredibly misleading/a flat out lie.
58.
by literallyroy 1y ago
Only incident we needed AWS support we had an engineer on call with us for several hours (including a shift change for them). Might’ve been a one-off but has seemed like their support is pretty phenomenal (also talked with someone who worke
59.
by literallyroy 1y ago
Yeah I thought they were going to show something cool like multi-tenant architecture. Odd to write this article when it was clear they expected to be impacted as they were reaching out to customers.
60.
by literallyroy 1y ago
I’m not the person you’re replying to, but I’m interested in your response to your own question if you’re up for sharing. My uninformed opinion if you want it: No, it’s not normal for someone to speak to an attorney before traveling. That q

More ›