Blog | https://www.alsutton.blog |
GitHub | https://github.com/alsutton |
Blog | https://www.alsutton.blog |
GitHub | https://github.com/alsutton |
Inspired by Google's move to remove @organicmaps from the Playstore without warning, I finally decided to move my > 3,000 Google Maps saved places to Organic Maps. To facilitate doing this for others' benefit, I made a quick webpage to convert your Google Maps GeoJSON data to GPX and KMZ files that render well in Organic Maps.
https://rudokemper.github.io/google-maps-places-to-organic-maps/
Despite what many purchasing departments think, software developers are not fungible assets.
I'm always puzzled as to why many purchasing departments don't understand that software engineers are not fungible assets. The term "fungible asset" is something I first came across when Simon Stewart was giving a talk during my boot-camp induction when we were both at Facebook. A fungible asset is something you can swap for an equivalent with no detrimental effect, and software engineers definitely aren't trivially swappable. You can swap one 10 euro note for another because they're fungible assets, but few other things are. Would most folk accept someone giving you a Polo instead of a Porsche?, No?, Why not? They're both cars and they'll both get you from A to B, what's the problem? The problem is cars, like software engineers, are not fungible assets. They have different performance characteristics, different abilities, and, in some cases, some variants can not tackle certain problems efficiently (would you like to try and set a lap record of the Nürburgring in a Polo when everyone else is using a Porsche 911?, or take a Ford Mustang on an off-roading course?). So please educate your purchasing departments. I know they have constraints and regulations in place to ensure that what a company buys is ethically sourced and appropriate, but sticking to the idea that you can get an equivalently performing software team from one vendor for 10%, 20%, or more below another vendors quote, when both quotes are honest and fair, rarely works out well.
🚗Android Automotive update will make it easier to talk to Gemini in your car
Android Automotive 16 won't bring a big Material 3 Expressive redesign like Android 16 QPR1 will for phones, but it does have some subtle tweaks.
Here's what's new👇
🔗 https://www.androidauthority.com/android-automotive-16-3567889/
Some days it just blows my mind how some pieces of software have gained so much traction, with so little in the way of support for some common use cases.
Today; #Docker running on an IPv6 only host.
Who thought assigning IPv4 addresses to containers running on an IPv6 only host was a sensible default that is so difficult to override?
🤯
Oh man, this is a trip down memory lane… https://m.youtube.com/watch?v=buuUZFh_pyk
“1984: BANDERSNATCH, BAILIFFS and the Battle for a HIT GAME | Commercial Breaks | BBC Archive”
One of the key things I fought for on Android was that AOSP (the open source release) could be built for and installed on the flagship Android devices. (Nexus, Pixel, etc). Sounds like that's no longer the case as of Android 16. Very sad.
Thanks to the Dependency Track + daily scan, vulnerabilities like this now get flagged pretty quickly so we can do an out-of-schedule dependency bump.
One less thing to worry about :)