It's not SQL, but it's relational.

docs.convex.dev/understanding/

Hah mostly

Hang in there. This is a great reflection on the context they were part of, and what you can do moving forward.

When I came back to work after paternity leave, I emailed all the leads on my team to reply with 2-3 bullets for the following categories:

1. What went well
2. What didn't go well
3. What else should I know

I was caught up real fast. Then basically archived my inbox.

I used to redo my website completely every few months. Now I've had the same design for almost about 15.

Maybe this is the year...

lol

I caved and bought a second one. The first was The Economist. The second is The Verge, I've been reading / listening to them since they started and I just wanted to support them.

Example of product design decisions that stay as holdovers from another era in a lot of products we use everyday.

I can totally imagine this being helpful for newer computer users.

That said the simply a screenshots folder now would be fine.

I was a mobile eng for many many years (since basically day one in 2008). I have written a few small apps in RN for fun. I think this is the way most mobile apps should be built.

This was now long enough ago that I can't remember all the details, but hopefully, I got the highlights right.

We ended up building a two-step sync, once from the cloud and once from the local disk. Then merged it all into a single database table that we then paged into memory for infinite scrolling.

Photos Android app had it's own unique challenge because it was trying to be the default way to view photos on the phone, and a seamless cloud photo library at the same time.