You know what actually motivates founders day-to-day? The fear of failure. Even though they're doing this thing that if they succeed they'll be super rich. Um that does motivate them but the thing that motivates them at the at any given moment is the fear of like disaster or looking like a fool, the server crashing, right?
Um everywhere in nuclear is like this. There are uh totally fake costs from an industry that is just totally anemic and doesn't know how to build anything anymore.
there's definitely a group of PMs and I certainly used to be one of them earlier in my career whose specialty wasn't technical or customer-oriented, it was politics.
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.
So a a big challenge in object-oriented programming is dividing the responsibilities because you're moving the computation to where the data is. Saying, "Well, this object does this and that object does that is a really critical decision because you want to you want the computation near to the data so that there's less coupling between them." which is a lesson that I I think uh kind of got lost in the noise. That's the fundamental design move in ob in designing object-oriented programs and I I think I stand behind that.
which is why when I see manifestos today I'm just like too soon. Not a bad idea. Would love to have one just too soon. It took 15 years for the technical change of object-oriented programming to come before we could say here are the consequences of it. Here's how in a simple way we can express how to effectively use this technology that we've been using day in and day out for 15 years. The genie comes along. People are like, "Well, what's the new manifesto? It's just not manifesto time yet.
Like we see the end productivity every few months in the form of model launches. Like there's no kidding yourself about this. Like the models make you more productive.
The third book in Cagan’s trilogy, this one focuses on how companies can transform their cultures from project- to product-oriented. This book is probably less useful for the individual contributor, but it offers hope for anyone trapped in a feature team that something better is possible. Buy it for your boss or CEO.
are your small actions accumulating or are they evaporating? You know, are you doing small things each day that are oriented toward a larger outcome or are you doing small things each day that are just kind of like one-offs and don't really add up? In a lot of ways, I feel like the two time frames that matter most in life are 10 years and 1 hour
And it's like the growth experimentation is more the the the slow and steady or fast and steady, I should say, uh approach where you're just continually iterating. You're making the product experience better, but then every so often, right, there's a big wave that comes in. you can quadruple your, you know, registrations overnights and yeah, you'd be a fool not to take advantage of that.
That's why Hitler was never a meth guy. That's also why I think this video is fake. He didn't take meth. I studied Morell's, the things he gave him. He gave a lot of things, and only twice was meth.
I think there's this whole idea, I call it a denial of attention. I think there's an entire attack vector that's going to be happening. We're using LLMs to generate fake bug reports, fake all these things to just actually effectively to demotivate and hurt open source maintainers.
The bar I typically suggest is that the people manager doesn't need to have the most technical depth on the team, but they need enough depth that they can follow most discussions without slowing them down, understand who's correct in most debates without needing to rely on trust, and generally stay oriented easily.
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.