Second bit of feedback - http://improve-osm.org/ does a pretty good job of highlighting areas of potentially unmapped areas. Via slack, I've made the suggestion to them to open their platform up to multiple sources such as strava gps traces (via their tile layer).
Would you be open to working with them to deliver the potential missing roads; so that you don't have to reimplement a lot of the basics?
Yeah, I think there is a big future in automated and semi-automated OSM updates, combining trace data and machine learning. That was part of my interest in this.
My company Gaia GPS has millions of GPS traces from hiking and similar outdoorsy activities, so I thought to combine that data (though footways may be more challenging than roads to classify). OSM trace uploads and Strava both seem like good data sources to do this work too.
I find the interoperation problems of software alarming - you would think open source tools would grow in use at some point, even if just the basics (ie: postgres/postgis, or tools dumping csv out to other tools, or one or two REST apis).
Could we create open standards? Yes. Will businesses? Probably not.
A lot of 'apps' for food act as an aggregator, which is the closest I can come to an API. But they are locked into one provider - hell, even getting opening hours, menu and how to pay standardised is hard. These all have standards available. No one uses them enough.
Why not? Technical difficulty - my local pizza shop doesnt care about running a payment processing endpoint, structured data, etc. Its counter to their goals.
What we need is an open source point of sale system that is web first - oscommerce with a desktop UI kind of thing. Then it becomes easy to add in 'publish standard compliant data'
Sadly no. The current version of mobile and the web relies on claiming consumer spaces and trying to herd users into them so they can be farmed.
It's a top-down control model.
Thinking in terms of bottom-up user value without imposing top-down control is alien to corporate psychology - even though if businesses agreed open low-friction global standards for payment processing and other kinds of interaction, possibly with some kind of profit sharing, they'd likely do better in the medium to long term.
Does it really though? Those are trivial problems to solve: dont show users tools they dont use via roles/permissions; dont execute code that is unrelated to the current purpose.
Roles/permission code is unrelated to the current purpose.
Really though, it's more of a systemic issue. There're so many ways you can make decisions to make your software make decisions to conveniently pretend you're giving the user exactly what they want without having asked them what they want. Maybe they don't want to download and install code they don't plan or know how to run. Bloat is problem for users because it has machine costs, which users have to pay for in time, money, and attention.
If you went on holiday the cat would more likely starve than roast. Australian and many other cats also regularly endure high heat - 32 degrees C plus. The author really should have left that out or thought it through a little more, detracts from the argument
Boyfriend in hospital doesn't qualify as 'sick leave.' FMLA is very narrow. I've been down a similar hole once in my life before. I was sickened and shocked. One emergency in my whole life. Nominal top employer. Senior position there. Zero support.
Simple fix: apply inner platform effect to your benefit. Either highlight a 'high level feature management tool' (trello/wrike/etc) different to your development workflow, or abuse the current tool by requesting very generalised tickets like 'standing outage prevention' (maintenance!).
No one will reject that because the consequences are lots of revenue.
Would you be open to working with them to deliver the potential missing roads; so that you don't have to reimplement a lot of the basics?