846 karma · joined May 15, 2010
Accepting the redefinition of terms merely because they are popularly misunderstood is literally putting the inmates in charge of the asylum. wink
Your client then can machine read that documentation (which can have long-lived cache headers or be immutable, so your client doesn't spend it's whole time re-checking documentation).
There will be a set of definitions that the client understood when it was coded, and by checking a payload for matching meanings, it can consume the information.
If it finds something it doesn't understand, it could even try to take some compensating action (e.g. suppose it's a client which displays images to it's users, and it encounters a new type of image format. It could perhaps look up a registry of javascript canvas image renderers and download suitable code to display the new image).
what happens when the Douglasses are no longer around?*
...
Here is how the plan works. Immediately upon learning of our deaths the executors of Dick's estate (his two highly computer literate kids) will post two files on our www.compmngr.com web site and will send out a broadcast email advising our customers how to download the files. The first file is a small standalone computer program called RegisterEvent.exe, which allows you to create your own registration files. So you won't have to register with Douglass Associates and you won't have to pay a registration fee. You can read more about RegisterEvent and how to use it below. The second file is a ZIP file containing all the source code for COMPMNGR and its supporting programs. This file will only be of interest to those few users who want to continue COMPMNGR development and who either know C++ programming or or willing to hire a C++ programmer.*
http://www.douglassassociates.com/compmngr_history.htmI'm hesitant to suggest they buy it out though.
If developers could just record what they wanted to achieve alongside how they achieved it my life would be much easier. I'm not even asking for the "why".
Keep your job, allocate a fixed amount of money each month to the business, and spend it all on advertising, copy writers and development.
You already know how to program, so you can be an effective PO for a remote team, you (probably) don't know how to delegate work or market stuff. Also, having to pay for the development will encourage you to create a real minimum VP.
It would end up full of fake job spam, and the listeners might want quality filters. I can imagine that you might pay to validate your identity as not-a-spammer.
As for policing, I think that would probably be where the money would be made - reputation/quality of the messages being posted.
They had an experimental project called 'annotations' where you could attach 1k of json to each tweet, like a DIY microformat.
I got onto the beta and created a prototype twitter client which you could attach mini 'apps' to tweets based on the payload type, e.g. you could tweet out a poll, or an inviation to play a game or a job advert or whatever, and you could attach your own app as a listener.
I think it could have been pretty amazing, basically A Message Bus For Everyone. If you build this yourself, you will run into the chicken and egg position, twitter could have pulled it off as they had the eyeballs and the developers.
Unfortunately they pulled the plug on it, around the time they started to close down the ecosystem.
The format itself is designed for a particular problem domain, namely outputting mobile-application specific controls and behaviours.
It would be an interesting exercise to extract those aspects into a custom vocab for JSON-LD + Hydra (or Siren, or (insert) other generic hypermedia formats).
http://www.markus-lanthaler.com/hydra/
It would also be interesting to have the hypermedia format defined as a schema somewhere.