New Article: How to stop forgetting what you read https://t.co/5oGObe4srl Why do we forget so much of what we read? I think the answer is less about finding the perfect note-taking system and more about building a larger base of knowledge.
Facts and Fallacies of Software Engineering by Robert L. Glass. In essence, this is a book about an industry that refuses to learn. That was true 25 years ago when this book was published, and it's probably twice as true today. (Just think about all the AI adoption metrics being rolled out — back to productivity mistaken for lines of code produced, only more elaborate. And expensive). What I like about this book is that Glass doesn't present anything new. Quite the opposite, actually. Rather, it's about research lessons that we all should know, but tend to forget. Ever had to do an estimate, or plan according to a requirements spec? Or maybe you thought that enough eyeballs make all bugs shallow? Then this book is for you. A great work by a fantastic author.
And it's really about being empirical. So forget all of the things that you learned about past models. Forget everything that you've learned about computer science theory in class. Look at the model, try to do a task, see where it struggles, and then based on that adjust. So it's just like very much become it's not a theoretical science, it's become an empirical science.
Now the thing is you can of course write examples in your documentation and Rust makes all examples into tests. This means that if you change the underlying code now your test fails. And so this means that you can't even you can't forget to update your examples in your documentation.
as leaders we get so focused on value statement mission statements we forget the mission statement is not the mission. The map is not the territory. Mission is an emergent property of the living superorganism of the thing we're birthing.
I've worked a lot of companies right but I'm wrong all the time and I think consumer behavior can be very fickle and especially when you work at a company you become a power user naturally. So sometimes you you may forget like what the actual user experience is for a brand new user.
So yes, the tools are great. We can use cursor. It helps us. It autocompletes. It writes a bunch of things. But the acceleration of learning I think is another maybe underutilized tool in all of our arsenals
I'm pretty sure people thought Microsoft had an advantage on the internet and Google and um Meta had an advantage on mobile and everyone thought IBM was going to win PCs. Like once IBM made a PC, that was it. It's all over now. And we kind of forget that like there were PCs before and then IBM made one and that kind of became the standard but then IBM lost it.
If you look at the S&P 500 now and you look at the amount of value from companies created in that, one could argue that actually almost all of the exuberance and hype was totally warranted and it in fact did change commerce in fundamental ways.
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.