https://www.timeanddate.com/calendar/?year=2026&country=9

Toggle the calendars here and you’ll see it.

They updated op-s-domain.com/telegramchat -> redirect telegram.me.

“Get off your high horse” is the phrase I flipped because I was grandstanding.

What phrase are you referencing?

I got this a few months ago -- 4k, solid brightness, and ok color.

Is it the OMG BEST? no. But I Disabled wifi, and even the channel display.

I use it with an apple TV with CEC on the TV -- I turn on the apple tv, TV turns on straight to apple interface. I turn off from the apple remote, TV turns off.

It's effectively "an apple TV" -- I'm happy.

love the idea, but if you aren't from a Shengen country you can't get into Shengen countries without a fingerprint scan and a face photo at the airport:

https://travel-europe.europa.eu/ees/data-held-by-ees

No way to opt out of the scan.

Sure, you are right. Git allows you to keep distributed state and eventually reconcile that.

Customers are trying to do that at absurd human scales right now without AI. Git itself is a bottleneck for large enterprises with large repositories and large CI configurations.

It may be hard to believe but it’s true.

Git has always been one of the biggest perf bottlenecks inside of the product.

First for any scaled deploy we recommended NFS. We were young and dumb and it was too slow. (We’ve all been there)

Then we went to an RPC model with gitaly and even unwrapped some of the git calls inside of that to speed it up.

Just a few months ago we had a large customer with thousands of devs and a large monorepo ground their deployments to a halt because of a cloning strategy change that introduced an accidental 10x in git calls. Git itself was the bottleneck because it’s not designed for this scale and speed.

For enterprises where thousands of developers are contributing code via git to a centralized system of record, who are firing off 1000s of CI jobs Git is absolutely a bottleneck.

Now with LLM technologies we should easily expect a 5-20x code volume increase on the conservative side. Git is being stretched to its perf limits.

(Source: see my profile)

I was weather-status neutral until I bought a house that has flooding challenges. Knowing that enough rain that could trigger flooding helps me avoid surprise cleanups and property damage.

(Like a reef tank sterilizer)

I suspect that once the sendgrid account is compromised, they then send out these phishing emails, hoping to compromise _other_ sendgrid accounts to look for password overlap and/or keep the flow going.

So yes, review and “narrative voice” will be more valuable than ever.

Found this as an example: https://lowendbox.com/blog/black-friday-bytehosting-is-here-...

> Ask this: “How does a project go from an idea to a ticket? Specifically, at what stage are engineers brought into the conversation; when the problem is identified, or after the solution has already been decided?”

The root of this question is great. The way it's phrased would be a flag for me.

I'd coach someone to ask it this way: "Can you tell me about how bugs and feature requests go from known to implemented/deployed? I want to know how it maps to my previous experiences/workflows"

This is the same question effectively. You will get your answer, and can ask a clarifying follow up if needed.

Or someone else that “can’t get their stuff together?”

A lot of people never even “move”.

> There are some out there who would love fans of Ruby on Rails to suffer because of its association with DHH.

This isn’t about DHH spouting whatever he is spouting.

It’s about people trying to convince others to not associate with Rails because of DHH.