I do not mind a longer connection if the airport or city makes it worth it.
I want to build smarter itineraries instead of always chasing the shortest total travel time.
Not every airport that looks good on paper feels good in practice.
I want to build smarter itineraries instead of always chasing the shortest total travel time. is exactly the right target. The best systems are the ones you will still use after ten trips, not just one enthusiastic weekend.
Not every airport that looks good on paper feels good in practice. is the part most advice ignores, and it usually ends up being the reason people quit a tool or workflow.
I try to keep it simple: solve the biggest pain point first, then add extra optimization only if I keep up with it naturally.
My rule is that if a setup takes too much manual maintenance, I replace it with something simpler even if the theoretical upside is lower.
You must be logged in to reply to this thread.
Log InNomadic_Nick
Thread Starter
4 replies
4 replies
4 replies
4 replies
4 replies