Trying to read a markdown document on @GitHub this morning and it keeps refreshing and scrolling back to the top. What are they doing with their frontend???
The crisis of software quality was already coming. Coding agents have just accelerated everything. Folks shipping quality are still shipping quality but faster. Those in crisis are unravelling faster. The problems are systemic. So must be the solutions.
@dhh@buildkite (We still have int primary keys for database and legacy reasons but they’re an implementation detail, everything has a uuid representing its true identity, public apis have only ever exposed uuids, and many models have uuid primary keys only.)
@dhh Same as @Buildkite. I’m hoping we can bridge our central service into self hosted components with distributed key generation etc.
Hardest part is sequential build numbers 😅
The smartphone just declared war on the camera industry
Xiaomi just dropped a wild idea: a smartphone with a detachable pro-grade camera lens.
A phone that snaps on a real lens with magnets. Yes, magnets.
It’s a clever move at a strange moment in history.
Camera sales keep falling. Smartphones keep rising.
And the real arms race isn’t glass anymore — it’s AI-powered image processing.
As an AI guy and a photographer, here’s my take:
Hardware won’t save the camera industry.
Software will.
The future of photography is no longer in the lens… it’s in the algorithm.
Phones will keep getting smarter.
Cameras will stay for the purists.
But detachable lenses?
Feels like a bridge between two worlds that are already drifting apart.
But maybe I’m wrong.
Maybe this hybrid future has a place.
What do you think — genius innovation or a beautiful dead end?
#AI #Tech #Photography #Innovation #Smartphones #FutureOfTech
@markjaquith This is also how you trick a toddler out of a temper tantrum, start saying things that are wrong - oh look at that blue apple, what a nice red banana, has you seen this purple orange??
Yeah our tools already detect and retry flaky tests automatically etc so if a build fails it requires diagnosis beyond a repeatable pattern. That’s why it’s tricky.
What the human would do is dive deeply into the build result and its artefacts to understand the error and how to fix it. This is a difficult problem to solve generally. Pipelines, build graphs, etc, vary wildly. Solving this specifically is better, as a human at a terminal with an agent, or an agent in a coding environment of its own trying to push a PR. Neither of those should live within CI, imho, they are adjacent.