Related posts
Marc Littlemore GitHub
The the words it uses that this site has seen least often elsewhere. Posts are matched on those words alone — nothing here is a summary of this one.
Top people
Showing Profile →
Hiding
Hiding
20 September
19 September
16 September
14 September
12 September
11 September
9 September
2 September
19 August
-
Their words
I remember anytime I would work with a big site on their performance problems, uh you could easily spend half a day, um you know, just looking at traces before you've even written any fixes at all. And now that we have LLMs, it's very quick to like reason through massive stack traces and actually be able to get down to fixes you can make.
12 August
10 August
8 August
-
Their words
I REALLY want to believe that this fixes prompt injection risks for coding agents, but I'm just not there yet
15 July
From one piece Context engineering with Dex Horthy 2 beliefs, in the piece's order there
-
Their words
And so if I say, "Hey, make this change." and the agent makes the change and then it runs the test and then they're broken and then it fixes the test. I have very high confidence the next change I asked it to make, it's going to follow that path again
-
Their words
So I think the the thing I'm most excited is actually like what we call like iterated loops or like slow loops where we basically have a cron job. We have the loop the the the structure of the loop is really easy. It's like run this llinter fix one thing commit and push and then we run that every night in our GitHub actions and we wake up every morning to one PR that makes the codebase a little bit better.
9 July
7 July
9 June
7 June
-
Their words
make the product, fix the product after you get customer feedback and then make the business which means make the margins.
2 June
28 May
27 May
-
Their words
The job of product isn't to just receive a problem and ship the immediate solution. It's to absorb all the problems and understand that there's one solution you can ship to fix 50 different problems.
13 May
-
Their words
But but the thing is like doing programming languages, you come to realize it's a long play. I mean, if if you look back at the the stuff I worked on, it it it goes in 10-year cycles at least. And TypeScript didn't really, for example, or C# for that matter. I mean, it took it it takes 10 years to get to, you know, version one is great, but it has all sorts of issues, and then you got to do version two, and then it's not until version three that it really starts to be great.
16 April
18 March
28 December 2025
23 December 2025
23 November 2025
21 November 2025
-
Lovedrcmnd.app
Maestri House Rechargeable Milk FrotherTheir words
This Maestri House device fixes all of these problems. It just feels great to use.
31 July 2025
7 April 2025
5 November 2024
29 September 2024
-
Usesrcmnd.app
ChezmoiTheir words
Chezmoi - for my Dotfiles
18 June 2024
1 April 2024
-
Their words
This is not the same world that you were part of. The complexity is off the chart; we are hidden layers and layers under the scaffolding. And we are used everywhere.
3 January 2024
17 March 2022
-
Their words
Finally, the health of the project depends on issue triage, bug fixes, refactors, and design work more than on new features. In fact, new features increase the maintenance burden.
30 November 2021
30 January 2020
-
Usesrcmnd.app
iTerm2Their words
I use iTerm2 as my terminal with the Z Shell rather than bash. No real reason other than I started using it after moving over to using dotfiles and I like the plugin and theme system.
-
Usesrcmnd.app
HomebrewTheir words
All of the above are installed using Homebrew and Homebrew Cask. Take a look at my Brewfile in my dotfiles for more info. This allows me to move to a new machine and be up and running incredibly quickly.
20 February 2019
17 June 2018
-
Their words
This is because systems accumulate months or years of state, and you have to drain that all away. Conversely, the same properties that make them slow to fix make them extremely durable once in effect!
14 March 2017
Nothing matches.
What is a korrent?
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.