Skip to main content

Make 99% Invisible Visible

I mentioned 99% invisible on my last FoxShow - it's a fascinating and amazing show, talking about design, typically in architecture. For those who build software, what IS interesting is how design impacts a variety of things. Subtle things, like how if you close your eyes, a lane change feels like a 90% degree turn or just a quick flick of the wrist. Or how four uber-creative guys decided to ensure certain words were ensconced in metal. Or even more fun, what really should happen when patent-violators go bad.

However, more to the point, 99% Invisible is on KickStarter, a web site to help businesses or groups fund things through the crowd. The show started looking for some money to help broaden its scope so it can do more shows. But they hit that target almost instantly. Now they are trying to do something  a little more fun ---- reach 5,000 "backers". They're almost there (4,600 at this writing) with 4 days to go.

You don't have to give a lot of money --- in fact, if you listen to the show and don't like it, then don't bother. But if you do like it, why not pledge $5 or anything? (if you give more than $30, there are some "gifts")

Why give? Well, if you like the show, the original goal was to try and make more episodes every year, by helping one of the interns be able to work regularly on the show. That goal was hit within 24 hours. Now with increased backers, there are other goals: more episodes, make video episodes, who knows.

One of the best things of the show is that it is re-listenable. From the web site, "They’re produced to stand up to multiple listens and reveal more each time they’re heard. The ultimate goal of 99% Invisible is to make radio that inspires mindfulness and wonder in all the things in the built world."

If that doesn't sound like something (or anything) that could improve your software design, maybe you're not listening (or looking) hard enough.

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...