Have wanted to work on a "better situational awareness while traveling" app, but haven't yet had the chance. Reachability of a POI is a great place to start, and I _feel_ that "it's a lot harder than it at first looks" aspect.
It would also be cool to:
* Become aware of local attractions. Esp. good restaurants, shops, views, hotels, hiking trails, etc. A lot of rating systems seem to give every fast food venue 3 or 4+ stars. Impossible to sift out the truly good and local / unique from the chaff.
* Become aware of time-limited events. Fairs, art shows, VFD chicken BBQs or fish fries, ... all the little "I wish I knew that was happening, I would have stopped by!" I constantly search for the local, the offbeat, the not-yet-another-corporate-outpost. But again, the chaff!
* Be able to navigate on backroads and scenic roads. Mapping apps are so hyper-focused on getting you there fast. They're not good at "get me there happy"—at least not for those of us that value the path less traveled far more than the highest-speed highway.
I'm also interested in your second bullet. The likelihood that you're passing by a cool outdoor event while blazing down the interstate is a lot higher than if you're staying in town. The data would be very difficult to source.
Thanks for the ideas though. Give Pike a try and let me know what you think.
In the years before VMs, containers, and locked dependency manifests, it was essentially impossible to get repeatable builds. There are still a lot of hurdles and gotchas, but we can at least get a rough approximation. The idea that some other pre-2010 dev team was going to be able reliably build your thing from just raw source code, and have it closely resemble the thing you built—it was a delightful fantasy. Escrow was a sales and legal "don't worry we have that eventuality covered!" CYA and emotional de-risking move, not a practical expectation of ability to build from scratch.
See the embedded video Failed Vocal Attempt (Music Video). However when it is played (at 0:02 or 0:03), it shows a title card for "Neon Dreams." That's the song that seems one part ELO, one part Daft Punk.
Sometimes posts like this are just value-signaling. I hear a lot of cynicism and "just you wait, the other shoe will drop" comments along those lines.
But combined with the other projects Anthropic has pursued (e.g. around understanding bias and explaining "how the model is thinking as it is") and decisions it has made, I'm happy with the course they're plotting. They seem consistently upstanding, thoughtful, and respectful. I want to commend them and earnestly say: Keep up the good work!
You might think you can, for a while. Been there, done that. But you probably can not do so sustainably in most cases. Even if you could, would you really be better off building vs. buying? Outsourcing development, operations, and maintenance is almost always the better choice, letting you focus on the things you do uniquely, differentiably, or meaningfully better.
"We have this awesome internal version of Docs that we're responsible for fixing, upgrading, and doing support for" is not the flex "AI can code anything!" aficionados think it is. Especially when you also have similar internal versions of Sheets, Jira, Slack, GitHub, Linux, Postgres, and 100 other tools.
Switching to sovereignty-protecting, locally-hosted collaboration, compute, and storage is by no means impossible. FOSS advocates have been eagerly beating this drum and providing options for 25+ years.
The missing ingredient has always been the will to absorb the inevitable cost of change, and the friction of choosing something other than the standard, go-to, often at least apparently free (or at least bundled) tools.
The current U.S. threats against NATO and allies creates a rift in the previously-accepted international order that may finally motivate material change. Often such change is chaotic and discontinuous—it feels well nigh impossible, right up to the moment it feels necessary and inevitable.
I fail to imagine a single bit of business software that cannot be achieved with open source software, outside of specific proprietary processes. But your average office technology work, I see being very plausible to move to open source. There is definitely going to be a breadth of quality across the tools, but the outputs can all be the same I believe. Even on a personal level, it's worth cultivating self-reliance on tools you control. But at a national scale it feels perhaps existential, worth what learning pains there may be. You also cultivate local software industries.
> the will to absorb the inevitable cost of change
it's simple economics. When US services have to increase their pricese because of trumps tarrifs and these increases are higher than the cost of change, they'll do it. we're almost there
That's Dan Frye's article, and it is um, a little Dan Frye-centric. He was a legitimately important contributor to IBM's technology management team around Linux and open source, especially as and after IBM made the turn.
But it reads as if he called the shot and piloted the turn. That is not my recollection or understanding. Other folks contributed as much or more to driving the Linux/open source pivot. Irving Wladawsky-Berger, the late Scott Handy, _et al_. It's IBM, so there were a ton of folks involved and contributing.
My source: I was an industry analyst and consultant in the server / system software space at the time, and I was in at least a few of the rooms where it happened.
Have wanted to work on a "better situational awareness while traveling" app, but haven't yet had the chance. Reachability of a POI is a great place to start, and I _feel_ that "it's a lot harder than it at first looks" aspect.
It would also be cool to:
* Become aware of local attractions. Esp. good restaurants, shops, views, hotels, hiking trails, etc. A lot of rating systems seem to give every fast food venue 3 or 4+ stars. Impossible to sift out the truly good and local / unique from the chaff.
* Become aware of time-limited events. Fairs, art shows, VFD chicken BBQs or fish fries, ... all the little "I wish I knew that was happening, I would have stopped by!" I constantly search for the local, the offbeat, the not-yet-another-corporate-outpost. But again, the chaff!
* Be able to navigate on backroads and scenic roads. Mapping apps are so hyper-focused on getting you there fast. They're not good at "get me there happy"—at least not for those of us that value the path less traveled far more than the highest-speed highway.
reply