emptiness
Occupied by a void
Roland Barthes wrote that the centre of Tokyo is occupied by a void...it is a quiet forest that lies at Tokyo's heart.
...The centre of Tokyo is certainly a void, but one that is protected by a circular train line, the Yamanote, which forms a 40-km (25-mile) loop around it. It seems to me that this ring of steel emphasizes the importance of the void, and the depth of its significance.
Names vs. The Nothing
This is the first site along the tour. In here we have a void. I remember the building that used to stand here, it was painted blue. Passing through it, you can imagine how us, as ghosts – should the building be standing here – would have to actually be invisible to pass through these walls and now it’s the reverse. The building is the ghost and we’re passing through these walls.
Erased de Kooning Drawing
Once, Robert Rauschenberg erased most of a drawing by Willem de Kooning, and then named it Erased de Kooning Drawing.
I am in no way certain what this is connected to either, but I suspect it is connected to more than I once believed it to be connected to.
Most important of all are the pauses
Japanese music is above all a music of reticence, of atmosphere. When recorded, or amplified by a loudspeaker, the greater part of its charm is lost. In conversation, too, we prefer the soft voice, the understatement. Most important of all are the pauses. Yet the phonograph and radio render these moments of silence utterly lifeless. And so we distort the arts themselves to curry favor for them with the machines.
Empty rooms
A Quote by Bruce NaumanI don't think empty rooms are ever really empty. I think we subconsciously put our emotions into them.
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.