Thinking out loud if Apple would resort to making 2 versions of their iPhones? And then exclusively selling the USB-C version in the EU, and everywhere else giving the customers a choice.
> what we desperately need is not more no-code builders, but a robust, DB-backed builder with an object-based workflow, and with code-behind for custom workflow logic
I find the microwaves with dials just last longer, and they are usually cheaper. In my experience, the touch pads on the digital ones breakdown faster.
There used to be a site call ClerkDogs.com that probably had the best movie recommendation system I've used. You started off naming a few movies you liked, and it would provide a list of movies you'd also probably like, and it was very accurate.
From what I remember, the database was cataloged and maintained by actual humans, and not some algorithm following behavior patterns.
Just an observation: Why aren't Lyft's employees using Lyft's ride-sharing service to get to work?
I know that's not the point of the article, but if your company owns ~25% of the market share [1], wouldn't it make more sense to instead give your employees "Lyft credits" (or whatever it's called), and have them use the service on a near-daily basis.
But with the mobile and Mac app (haven't tried the iPad app yet), it shows a "list type" view (not sure if that's the correct term).
Are you considering adding a "week planner" view to at least the Mac app?