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.
Targeting old 16-bit computers, the authors couldn't afford to build a sloppy, wasteful UI, and so by modern standards the game UI is remarkably fast and responsive.
maybe performance could be part of a package where you try to take on one of those players. like, hey, look at how much more responsive our thing is than theirs. Might be a nice plus, but that's not going to be sufficient.
One of the things I found most exciting in the last couple of years was seeing as model qualities gotten better and and harnesses and tools have gotten better, how many people um that were directors or VPs or SVPs or any of these levels were actually rolling up their sleeves and trying things out.
as a product manager, I've spent less time in the last year talking to a data scientist than I ever have in my career, even though I've probably spent 10 times more time in data and understanding actually how the product's working than I have ever have in my career.
And the reason they came, I think, is absolutely because of the the better tooling. And I think we were totally right there that like adding a an erasable type system and then using that to enable great tooling is really where the pro where the programmer productivity boost is realized.
we knew from experience that you cannot build good tooling without a type system. You can build decent tooling, but it's never going to scale. It's never going to scale to large teams cuz you can't describe your intents in in the code.
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.
we see the difference between the great engineer and an an average engineer is still two 3x in terms of their capability. They're more inquisitive. they're at the bleeding edge more, they're more innovative,
Uh well, tech is easy, people are hard. And so, you know, sometimes getting the flow really is about understanding what I'm doing, having very clear direction and goals and and knowing what my what my work is doing.
oh 50 gigawatts of economic you know sort of capex in in the data center and what gets built on top of that in terms of tokens is even larger right it might be hundred billion dollars worth of AI value into the supply chain is held up by this $1.2 two billion dollars worth of tooling that simply just cannot expand its supply chain quickly.
you can make your life easier on the biology front by building better engineering tooling and the fact that that's possible is a huge deal. Like that is that is not true for most problems in biology and it gives you a lot of leverage on the problem.
Overall, though, this experience reinforced my belief that the tooling and interface design around LLMs is lagging way behind the actual capabilities, and is an area of active experimentation and development, even aside from any future model improvements.
I think it’s fantastic when businesses are built on open source, the WordPress ecosystem is at least 10B+ a year; Automattic and WP Engine are less than 5% of that.
If WP Engine wants to find another open source project with a more permissive license and no trademarks, they are free to do so; if they want to benefit from the WordPress community, then they need to respect WordPress trademark and IP.
I use MAMP for WordPress development, Postman for API testing, Notion for notes and task management, Slack and Discord for communication and Keynote for course presentations.
The best tooling in the world will struggle to make up for "regularly losing a day debugging your environment," and so getting that aspect right can easily outweigh almost any other decisions you make.
Another thing that needs to be fixed when it ultimately breaks down, another bit of automation that works 99% of the time, but starts making funny noises when you slip into the 1%
When I write for Waxy.org, I write directly in WordPress's new Gutenberg editor, which is now on par with Medium as a best-of-class writing environment for the web.
I've run all my sites on Jekyll and GitHub Pages for a while now. I have found it easier to manage than WordPress (particularly as I know next to nothing about databases),
Sizzy is a cool browser specifically for responsive design. It lets you view all of the breakpoints for a site at the same time and also does a good job auto-scaling fixed size viewports to fit whatever window size you're using.
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.