The terminal is dead. Most developer tooling will be washed away by tokens. Shells, text editors, CLI tools won’t be used by humans anymore. There’s no need to know command line flags and jq invocations anymore.
I’ve written about the people familiar with the matter pattern before—it means Reuters have anonymous insider sources that their reporters (and editors) find credible.
If the UK is to survive water-starved summers in the future, it will need to build more reservoirs and plug holes in our existing pipelines at the same time.
But I also think that in my mind, 20 years of DevOps was really about one thing. Trying to create one feedback loop that connected people writing code to that code in production. And it failed.
basically the idea is like the IDE of the future needs to be rethought from the ground up for agents. And it might not even be a like I don't know a lot of editors kind of started with the text field and bolted on an agents tab.
In truth, rather rapid electrification projects, without decade-by-decade continuity, exist outside the UK and are often quite reasonable in their costs, as in Denmark, Israel, and especially India.
But I have come to realize that as a web developer, Linux is just better. Linux is just better. It's closer to what I deploy on. The tooling is actually phenomenal.
Their words now
anyone who's working with the web, who's working with Ruby, who's doing DevOps, they should be on Linux because first of all, that's closer to what we deploy.
After many years, Sublime Text remains one of my favourite code editors. I still often use it to edit huge files or to make heavy edits through its powerful find and replace feature.
Over the past few decades, journal editors and peer-reviewers have increasingly insisted that papers must present large datasets that have been treated using complex statistical methods in order to make even the mildest claims about what caused what.
A useful read for more experienced engineers and those wanting to improve architecture and devops skills on designing and operating reliable systems. The content is excellent, but the book is not designed to be read in one sitting.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.