Philosophy Mondays: Human-AI Collaboration
Today's Philosophy Monday is an important interlude. I want to reveal that I have not been writing the posts in this series entirely by myself. Instead I have been working with Claude, not just for the graphic illustrations, but also for the text. My method has been to write a rough draft and then ask Claude for improvement suggestions. I will expand this collaboration to other intelligences going forward, including open source models such as Llama and DeepSeek. I will also explore other moda...

Intent-based Collaboration Environments
AI Native IDEs for Code, Engineering, Science
Web3/Crypto: Why Bother?
One thing that keeps surprising me is how quite a few people see absolutely nothing redeeming in web3 (née crypto). Maybe this is their genuine belief. Maybe it is a reaction to the extreme boosterism of some proponents who present web3 as bringing about a libertarian nirvana. From early on I have tried to provide a more rounded perspective, pointing to both the good and the bad that can come from it as in my talks at the Blockstack Summits. Today, however, I want to attempt to provide a coge...
Philosophy Mondays: Human-AI Collaboration
Today's Philosophy Monday is an important interlude. I want to reveal that I have not been writing the posts in this series entirely by myself. Instead I have been working with Claude, not just for the graphic illustrations, but also for the text. My method has been to write a rough draft and then ask Claude for improvement suggestions. I will expand this collaboration to other intelligences going forward, including open source models such as Llama and DeepSeek. I will also explore other moda...

Intent-based Collaboration Environments
AI Native IDEs for Code, Engineering, Science
Web3/Crypto: Why Bother?
One thing that keeps surprising me is how quite a few people see absolutely nothing redeeming in web3 (née crypto). Maybe this is their genuine belief. Maybe it is a reaction to the extreme boosterism of some proponents who present web3 as bringing about a libertarian nirvana. From early on I have tried to provide a more rounded perspective, pointing to both the good and the bad that can come from it as in my talks at the Blockstack Summits. Today, however, I want to attempt to provide a coge...
>400 subscribers
>400 subscribers
Share Dialog
Share Dialog
I complained about one pet peeve on Monday (stock certificates for startups) and can’t help myself with another one today: programs that complain about user inputs that are easily fixable. Yesterday I copied a bunch of email addresses from Jobscore and pasted them into the bcc field of an email in Outlook. The emails were comma separated. Outlook didn’t like that – and popped up a dialog saying something was wrong, including suggesting that I replace commas with semicolons. I copied the emails into TextEdit and did a find and replace, but only after first tweeting that I really would expect Outlook to do this for me.
This is just one example of a whole class of problems in which developers did not take the time to make a form accept a likely range of inputs, but instead insist on a specific format. Phone number input fields that don’t allow dashes or dots in the numbers are a perfect example. It is trivial to allow these and discard them after the fact. Another one is that almost all payment input forms ask users about the type of credit card. That is of course completely redundant information because the first four digits of the card number encode that information!
While I am at complaining about user interface annoyances here is another one: browsers not letting you tab into a list box. When filling out a form, I really like not having to move the mouse pointer and just use the keyboard instead. But Firefox and Safari both tend to skip over lists instead of popping them open and letting me use the keyboard to move to the right entry.
I complained about one pet peeve on Monday (stock certificates for startups) and can’t help myself with another one today: programs that complain about user inputs that are easily fixable. Yesterday I copied a bunch of email addresses from Jobscore and pasted them into the bcc field of an email in Outlook. The emails were comma separated. Outlook didn’t like that – and popped up a dialog saying something was wrong, including suggesting that I replace commas with semicolons. I copied the emails into TextEdit and did a find and replace, but only after first tweeting that I really would expect Outlook to do this for me.
This is just one example of a whole class of problems in which developers did not take the time to make a form accept a likely range of inputs, but instead insist on a specific format. Phone number input fields that don’t allow dashes or dots in the numbers are a perfect example. It is trivial to allow these and discard them after the fact. Another one is that almost all payment input forms ask users about the type of credit card. That is of course completely redundant information because the first four digits of the card number encode that information!
While I am at complaining about user interface annoyances here is another one: browsers not letting you tab into a list box. When filling out a form, I really like not having to move the mouse pointer and just use the keyboard instead. But Firefox and Safari both tend to skip over lists instead of popping them open and letting me use the keyboard to move to the right entry.
No comments yet