content
Raw size isn't enough
Content as value
A web of books
Rewarding Curation
An Article by Wesley Aptekar-CasselsSomething interesting about the design of Twitter is that it doesn’t have much of a way of rewarding curation, only authorship.
...I’m inclined to think that the mechanisms of distribution of information are very important, and I think figuring out ways to reward good curation is probably an important thing.
...I don’t really know what the solution is here, but I do think that finding and curating good links and bits of information is useful, and something that should be rewarded more than it currently is.
The McClusky Curve
An Article by Shawn WangHe coined this thing, which I call the McClusky Curve… So if you go first, you want to either be first in the cycle or you want to go later and add a very differentiated, deeper, in depth take that nobody else has where you’re adding value to the conversation.
But if you go anywhere in the middle, you’re just in the noise.
...I think this is the fundamental tension to staying relevant to the discussion, and therefore growing your readership. Your creation process needs to generate some mix of timely vs insightful, yet of course the worst of all is to try to do both and end up with neither.
Care for the Text
An Article by Robin RendleWhenever I’m stuck pondering the question: "How do I make this website better?" I know the answer is always this: Care for the text.
Without great writing, a website is harder to read, extremely difficult to navigate, and impossible to remember. Without great writing, it’s hardly a website at all. But it’s tough to remember this day in and day out—especially when it’s not our job to care about the text—yet each and every <p> tag and <button> element is an opportunity for great writing. It’s a moment to inject some humor or add a considerate note that helps people.
…These are the details that make a good website great.
All websites are just digital movie theaters now
An Article by Ryan BroderickIf I had to guess where this is all going, I’d say that what an internet platform is actually has already permanently shifted. Instead of apps trying to dominate specific features — a platform for video, a platform for expiring content, a platform for connecting social networking, a platform for livestreaming, a platform for resumes — we’ve already entered a new era of online networks where they all will essentially offer the same services and instead, focus increasingly on specific demographics.
Safari 15 isn't bad, just misunderstood
An Article by Jeff KirvinWhat I see in Safari 15 is the first steps into a new design language for iOS, one prioritizing adaptive, contextual interfaces. Ever since the move to the new “all screen” iPhone X design, content has been king on iOS, and Apple has been removing more and more user chrome. This is the next step on that journey.
Deadlines are bullshit
In software development deadlines are a necessary evil. It is important to understand when they are necessary, and it is important to understand why they are evil.
- External vs. internal deadlines
- Why are internal deadlines evil?
- Engineers who love their work
External vs. internal deadlines
When are deadlines necessary?
- Contractual obligations
- Technical liabilities (e.g., dependency EOL)
- Compliance, government, investors, and other external stakeholders
What do all of these deadlines have in common? They are all important. They are all deadlines that cannot be missed. They are all external.
When are deadlines evil?
- Your manager says you have a deadline
- Your software development methodology says you have deadlines
What do all of these deadlines have in common? None of them are important. They are arbitrary. They are all internal. They are all bullshit.
Why are internal deadlines evil?
- Estimation: When estimating engineering work a substantial time investment is required by an engineer in order to get an accurate estimate.
- Misaligned Incentives: There is an incentive to lie and give estimates much longer than the feature is truly expected to take.
- Low Morale: Deadlines are likely to be missed often. Repeated failure has a cost to the morale of the team.
- Micromanagement: Deadlines are wielded by middle managers as a whip to harass and annoy engineers working on features.
- High Stress: When engineers feel the pressure of other stakeholders holding deadlines over their heads it creates an environment of high stress.
- High Turnover: On teams with high turnover rates the best engineers have an easy time finding new work and leave quickly, the worst engineers have a difficult time finding work and remain. This selects for a lower quality team over time.
Engineers who love their work
The resolution is simple. Never have internal deadlines. Operate on a prioritized and ordered list of features. Estimate only when necessary to prioritize and do so in a t-shirt sizing way. Trust your engineers and they will begin to love their work. Engineers who love their work are happy and productive.