davidkuennen

Thank you! It's been an excellent experience over the years really. Always easy to ship and always easy to keep up with flutter improvements which have come consistently.

I never felt that context size was any issue at all in codex. I don't know how their compaction works, but it just keeps on going as if it has no context limit at all. At least in my experience.

How do you expect the developers to pay for the service? Map tiles alone are already very expensive and data heavy.

Setting up my own server (migrating off GCP LB) taught me so much about networking. I was especially surprised that providing IPv6 is such a performance boost for low bandwidth phones since they mostly only operate on IPv6 by now and IPv4 needs some sort of special roundtrip.

On slightly off topic note: Codex is absolutely fantastic right now. I'm constantly in awe since switching from Claude a week ago.

Write down 10 of your TODOs that generate income. As per natural law, it's likely that 1-2 of those TODOs will have 80% of the impact while the other 8-9 will have almost no impact. Now here comes the interesting part. You propably already know the 8-9 tasks that have almost no impact, but as per another law, those are also the easiest tasks (checking mails and such). On that list the TODO that feels like the biggest hassle and you least want to do will likely have the biggest impact. Sit down and just do it. Now, without delay. That already makes you more productive than 98% of your colleagues.

This is actually much more important than the volume of data transferred. Having 33% lower latencies across the globe would be huge.

I also tried a lot of todo apps and ended up with a sheet of paper :D