whimsy
emojraw.glitch.me (draw!)
A Website by Shannon LinSpreadsheet Portfolios for UX Designers
An Article by Erica HeinzThe “case study?” column was the whole point of the spreadsheet — identifying which projects I still needed to write up for my portfolio — but at this point I looked at the sheet, and thought “This is honestly a better overview of the work I do than any ‘portfolio’ I’ve seen”.
So I tweeted a screenshot, joking/trolling that it WAS my portfolio (I didn’t include any winks or notes that I was still planning a “real” portfolio), but people didn’t respond with the lulz I expected — they got the idea, or took it at face value and said they were going to do their portfolio this way too!
A small store
A Gallery by Kyeoung Me LeeExit pages
An Idea by Brad EnslenToday I made an Exit page. So many people end their visit by hitting the Back button on their browser. The exit page is a last attempt to get them to explore the Blog Directory to find an entertaining blog. Or failing that to try a search on a search engine they may have never tried before.
The Whimsical Web
A Website by Max BöckA curated list of sites with an extra bit of fun.
Funcooker
A Websitemultiverse.plus
A Website by Kicks Condor & Weiwei HsuAn audacious attempt to reshape blogging, to see where it can go next!
Podcasts and video have really taken over - to the extent that it feels like reading may be falling behind. Can we enhance text and imagery on the Web? Try to give blogging new life?
Lizzo's Juice Shop
A Websitelittlebigdetails
A Blog by Floris DekkerLittle Big Details is a curated collection of the finer details of design.
As Charles & Ray Eames put it:
“The details are not the details; they make the product.”
This is intended to be a source of inspiration.
Created and curated by Floris Dekker. Alumni: Andrew McCarthy.
Games For Crows: Feels
A Game
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.