|
|
|
|
|
by Beanis
5040 days ago
|
|
Developer work is too varied to have a single consistent voice. Drop the union idea, the word has too much baggage and becomes a huge people management issue. Turn it into what developers do best, build an app/api. I'm not sure if this idea will make too much sense; I need to see if I can find some time to explore it a little more. I could see building an app/api which is a mixture of a news/issue aggregator and a remote config editor. Figure out how to surface issues to developers in a consistent way. Then let developers decide which issues matter to them, and how to deliver updated configs. Then let developers decide how to use the api/config from there. Maybe some apps will decide to disable in-app purchases for some time period, maybe some will alter code-flows to use a competitor of a big company, maybe some app will praise some company for their stance on some issue. The developers need to be in full control at all times though. The api would let developers read the remote config from their apps. Maybe it just turns into a remote config service, and the activism part gets lost... but it might work as a vehicle for this kind of activism too. |
|