tapping on the muesli vs corn flakes comparison gave me no visual feedback to indicate it was ever going to do anything.
then it died.
when it came back I tried tapping on Visual Studio Code, expecting a page to come up but nothing happened. after enough time to flip back to hn and tap that sentence out (on my phone) and there was a page load happening. another 5s after that, a page with a lot of things on it but very little content appeared.
so a couple thoughts:
if you're going to manage page loads and nav with javascript, visual feedback is not optional. (better yet, don't do it with js at all. you don't have to go full SSR, just let your web server handle more of the effort)
every example you have there is going to boil down to personal preference or context dependence. like corn flakes vs museli, no one is going to make buying decisions based on that. there is no "better" only in that comparison, only "better for my situation". same goes for local businesses, IDEs, and whatever else. these scores don't tell me if it will work for me, only that it's popular. this is why the best review sites these days compare and present the results as "if you prefer X, then consider A. if you're on a budget but want Y, then B is a good choice." people want to know what's best for them. if you've got the data then frame a new users experience around "what are you looking for and what do you care about" rather than this zillionth hot-or-not-with-a-twist clone.
biggest issue I've had with flash is that it seems to hit a sort of "dumb o'clock" wall. right around the time Beijing would be going to work, response quality takes a dump on instruction-heavy tasks when context grows beyond ~120k tokens.
responses are still usable, no hallucinations or anything, but it's worth keeping in mind if you rely on detailed instructions or large context windows.
same here. gpt-5.x medium was my default for coding and v4 flash (max) has completely replaced it. it's the first open source model that made me feel like I could just let rip and not worry any more than Claude or GPT.
When planning small-to-medium sized changes, I found that it was a little bit faster than GPT-5.5 (high) and produced equivalent results. on large changes its results were fine but GPT's were more thoroughly thought through. DS v4 beats the absolute pants off GPT when it comes tone and style though.
I'm working on one right now where nearly everything can be expressed as a combination of workflows. There will be some built-in agent types out of the box but all the Lego pieces are there if you want to put together something different.
I agree with you that, when sharing, location should be stripped by default with an option to include it.
After seeing this post I checked my recent photos. I'm using a Pixel 6 Pro with the most recent android release and the stock camera app. None of my recent photos have location in the EXIF, even locally, and there's no option to turn it on.
It's particularly galling that the Camera app still wants location permissions and if you view a photo in the Google Photos app, the location is still there. Google can have those exact locations, but no one, not even the user, can.
that is too much flight time for a 4-5 day trip. 14 hours of flight time usually means at least 20 hours of travel time. anyone doing that is going to be wrecked the next day, then they would have to turn around and do it again at the end of the trip.
presumably you'd be wrapping up the offsite on a Friday, so people would fly back that morning or Saturday morning. if they fly back Friday then they lose a day of offsite time, if they fly back Saturday then they lose their weekend to travel and recovery.
if a large % of your team is within 5-8 flight hours and it's only a handful of people coming from further away, then I'd spring for an extra night or two at the hotel/airbnb for the people with extra long flights.
cost and activities are hard to gauge without knowing team size. smaller teams can usually share a large airbnb which helps a lot with cost. larger teams means hotels and the cost balloons.
similar story for activities. larger teams limits your options and makes pleasing everyone hard. I'd recommend booking one or two "all-hands" activities, like dinner at a fancy restaurant, and researching some "this is a thing if anyone is interested" ahead of time. with a large team, make arrangements if enough people opt-in, or for smaller teams make it easy for people to go off and do that on their own. I've had good success with booking a few all hands activities and setting up a shared space where people can hang out together. smaller activities tend to naturally grow out of those interactions.
tapping on the muesli vs corn flakes comparison gave me no visual feedback to indicate it was ever going to do anything.
then it died.
when it came back I tried tapping on Visual Studio Code, expecting a page to come up but nothing happened. after enough time to flip back to hn and tap that sentence out (on my phone) and there was a page load happening. another 5s after that, a page with a lot of things on it but very little content appeared.
so a couple thoughts:
if you're going to manage page loads and nav with javascript, visual feedback is not optional. (better yet, don't do it with js at all. you don't have to go full SSR, just let your web server handle more of the effort)
every example you have there is going to boil down to personal preference or context dependence. like corn flakes vs museli, no one is going to make buying decisions based on that. there is no "better" only in that comparison, only "better for my situation". same goes for local businesses, IDEs, and whatever else. these scores don't tell me if it will work for me, only that it's popular. this is why the best review sites these days compare and present the results as "if you prefer X, then consider A. if you're on a budget but want Y, then B is a good choice." people want to know what's best for them. if you've got the data then frame a new users experience around "what are you looking for and what do you care about" rather than this zillionth hot-or-not-with-a-twist clone.