The “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!
Today 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.
An 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?
Who advocates in the requirements process for the product itself—its conceptual integrity, its efficiency, its economy, it’s robustness? Often, no one. As often, an architect or engineer who can offer only opinion based on taste and instinct, unbuttressed as yet by facts. For in a classical Waterfall Model product process, requirements are set before design is begun.
The result, of course, is a grossly obese set of requirements, the union of many wish lists, assembled without constraints. Usually, the list is neither prioritized nor weighted. The social forces in the committee forbid the painful conflicts occasioned by even weighting, much less prioritizing.