water
Watermill
Rain Chains & Musical Drains
A rain chain in winter; Dresden Kunsthof Passage; Drainage planters near Pike Place Market in Seattle.
If there is a larger takeaway here perhaps it is about paths of least resistance, with regards to both the actual flow of water and design decisions. On the one hand, it is easy to blindly follow regional precedents and traditions with long histories (or grab whatever is handy at the hardware store). On the other hand, sometimes it makes sense to take a step back and decide consciously how to reveal (or conceal) a natural process.
The Beauty of the Overlooked
An Article by Maria PopovaMedusa from A Naturalist’s Rambles on the Devonshire Coast by Philip Henry Gosse, 1853.
Philip Henry Gosse’s Stunning 19th-Century Illustrations of Coastal Creatures and Reflections on the Delicate Kinship of Life
“These objects are, it is true, among the humblest of creatures that are endowed with organic life… Here we catch the first kindling of that spark, which glows into so noble a flame in the Aristotles, the Newtons, and the Miltons of our heaven-gazing race.”
Rain chains
An ObjectRain chains are a beautiful and functional alternative to traditional, closed gutter downspouts. Guiding rain water visibly down chains or cups from the roof to the ground, rain chains transform a plain gutter downspout into a pleasing water feature. From the soft tinkling of individual droplets to the soothing rush of white water, they are a treat to listen to.
Rain chains (‘kusari doi’ in Japanese) in concept are not a new idea. For hundreds of years, the Japanese have used the roof of their homes to collect water, transporting it downward with chains and finally depositing the rain water into large barrels for household water usage. Japanese temples often incorporate quite ornate and large rain chains into their design.
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.