critique
A distinct and complementary stance
Scholars and critics
Starved for good journalism and criticism
Downsides of the internet
The McClusky Curve
The dying art of the hatchet job
An Article by Dorian LynskeyI find that the act of disagreeing with a sharp takedown sharpens my appreciation of the work in question. If I have to think a bit harder about what I like and why I like it, that’s fine by me, especially when it’s something that has been almost universally acclaimed.
...It’s not that I long for an epidemic of gleeful brutality but I will always cherish the right of critics to express their hate, hate, hate in the ultimate service of what they love, love, love.
Discourse in web design
An Essay by Jason Santa MariaA website is its own, singular thing. We know it isn’t a book, a TV show, a film, or a song, but our language is limited to talking about it in those restrictive boxes. A website is a mix of all of those things, and none of those things. It is influenced by place and time. A website changes with age. It can evolve and regress.
It was then I wondered if the problem wasn’t that web design lacked its own Emigré. What if we actually lacked a shared language to critically discuss web design? Art, architecture, and even graphic design, have critics and historians that give context to new work through the lenses of culture and important work from the past.
Design Discourse is in a State of Arrested Development
An Essay by Khoi Vinh[Designer News] is good, useful content, but most of it is written by designers themselves. Taken as a whole, it’s also a useful illustration of something vital that our industry lacks: balanced, insightful, independent writing that critically evaluates the profession.
One Designer's Response to Khoi Vinh's Complaint
An Article by Brandon DornThere is a place for discussing technique, for which forums like r/Design, Designer News, and the like are well suited. Yet expecting these platforms to provide insightful, serious critical discussion is like going to McDonald’s for an artisanal sandwich. Sure, they may advertise that, but that’s not really what you’re getting.
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.