A developer at today’s
Homebrew Website Club mentioned that they didn’t want to have a website built on a particular language because they weren’t familiar with the language and felt uncomfortable trusting their data to it. What if something goes wrong? What if it breaks? How easy will it be to export and move their data over?
Compare this with the average social media user who doesn’t know any code. In their world, they’re making a choice, likely predicated upon social pressures, to post their data, content, and identity on one or more corporately controlled silos. Because of the ease-of-use, the platform is abstracted away from them even further than from the developer’s perspective thus making it even less apparent the level of trust they’re putting into the platform. What is the platform doing with their data? How is what they’re seeing in their feed being manipulated and controlled?
The problems both people are facing are relatively equivalent, just different in their dynamic range. The non-programmer is at an even greater disadvantage however as the silos are moving faster and can do more to take advantage of and manipulate them more seamlessly than the programmer who at least has more potential to learn the unfamiliar language to dig themselves out. This difference is also one of dynamic range as the developer may only need a simple shovel to dig themselves out whereas the non-coder will need a massive excavator, which may be unavailable and still need an operator with knowledge of how to use it.
Featured image: excavator flickr photo by mbecher shared under a Creative Commons (BY-NC-ND) license
