as software engineers most of us are sitting in an office chair all day we spend hours staring at a screen, not moving more then our fingers or wrists sometimes we lock in and it feels like there are only occasional windows to move if so, start simple. take a screen break and do: - a 5-min walk around your house - 25 push-ups - 25 jumping jacks anything to break the chain of not moving trust me, you'll thank me in a year
the external tools that we use to help us reason, remember, associate, calculate-from counting on our fingers to chatting with an advanced LLM-should be properly understood as extensions of our own cognitive process.
and I thought programming sitting fingers on keyboard staring at code that's that's where I do my learning because that's where you can no longer fool yourself that you actually understand either you compute the correct value or you don't compute the correct value. So I wanted to elevate that moment of reality meets program and that's where the programming comes from.
Always try your stupid ideas if you can do it cheaply and reversibly. Jumping off a bridge is not a reversible decision. Not talking about that. I'm talking about stuff like this where you're just like, "Here's a stupid idea." 99 times out of a 100 it'll fail. But that one time you won't have any competition cuz nobody else is stupid enough to try this idea.
I love chiseling my code and the way I use AI is in a separate window. I don't let it drive my code. I've tried that. I've tried the cursors and the wind surfaces and I don't enjoy that way of writing. And one of the reasons I don't enjoy that way of writing is I can literally feel competence draining out of my fingers.
Their words now
I will now start any project I'm starting with. I'm starting agent first and that's a massive shift
Big flat toggle buttons under satisfying tension. Clear affordances. You push them down, not in. One click catches, one doesn't. You can use them with bare hands, oven mitts, fingers coated in slippery whatever. Doesn't matter. Plenty of surface area. Outstanding design. It's all been downhill from there.
I enjoy it even almost like as a sort of pair programmer AI pair programmer who doesn't drive who's just there to give suggestions to know the API to do all these other things but the second it starts wanting to autocomplete my code I'm like yeah I'm out bro
Their words now
I love chiseling my code and the way I use AI is in a separate window. I don't let it drive my code. I've tried that. I've tried the cursors and the wind surfaces and I don't enjoy that way of writing. And one of the reasons I don't enjoy that way of writing is I can literally feel competence draining out of my fingers.
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.