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
One of the questions asked by a Tech Tuesday reader was about using multiple different programming languages for different parts of a site. Back in the early days of the web that wasn’t really an issue because you would write the page generation in something like Perl or TCL and that was all there was. Well, not really because even then you had to know HTML but of course early HTML was so minimal that it didn’t really matter much.
Well along came more HTML, CSS and most importantly Javascript. So at that point you were almost certainly up to 2.5 languages (something on the server, Javascript and I am counting HTML+CSS as 0.5). Then more recently with progress using Javascript on the server you were potentially able to go back to 1.5. Then again almost everyone is also developing apps and if you want native performance you are potentially adding another two languages: Java for Android and Objective C for iOS.
So what should you do? For very small teams there can be some gains from using only one language and in an ideal world a single engineer would be able to do everything in Javascript (if and when HTML5 apps ever really make it). At a minimum it would reduce tooling and testing overhead which is an important consideration.
Having said that, I think the prime directive should be to use the right tool for the job even if that results in multiple languages. The benefits from a proper match will ultimately outweigh the added cognitive and tooling overheads. Also, you should be very suspect of any engineer who has only ever programmed in one language and does not feel comfortable or interested in picking up a new one.
PS Please ask more questions!
PPS Minimal links today but I am running to catch a flight!
One of the questions asked by a Tech Tuesday reader was about using multiple different programming languages for different parts of a site. Back in the early days of the web that wasn’t really an issue because you would write the page generation in something like Perl or TCL and that was all there was. Well, not really because even then you had to know HTML but of course early HTML was so minimal that it didn’t really matter much.
Well along came more HTML, CSS and most importantly Javascript. So at that point you were almost certainly up to 2.5 languages (something on the server, Javascript and I am counting HTML+CSS as 0.5). Then more recently with progress using Javascript on the server you were potentially able to go back to 1.5. Then again almost everyone is also developing apps and if you want native performance you are potentially adding another two languages: Java for Android and Objective C for iOS.
So what should you do? For very small teams there can be some gains from using only one language and in an ideal world a single engineer would be able to do everything in Javascript (if and when HTML5 apps ever really make it). At a minimum it would reduce tooling and testing overhead which is an important consideration.
Having said that, I think the prime directive should be to use the right tool for the job even if that results in multiple languages. The benefits from a proper match will ultimately outweigh the added cognitive and tooling overheads. Also, you should be very suspect of any engineer who has only ever programmed in one language and does not feel comfortable or interested in picking up a new one.
PS Please ask more questions!
PPS Minimal links today but I am running to catch a flight!
No comments yet