Exactly. If they just lay people off, that's just cost cutting, and potentially seen as a bad sign. If they're saying they're laying people off because they're replacing them with AI, then they're innovative!
How is the Anthropic stuff on Bedrock in general? We're using OpenAI stuff on Azure right now and it's frustrating how slowly stuff gets rolled out in our region(s).
Render most of the frontend server-side and just use JavaScript for the dynamic bits only, I guess? I personally haven't done it like this since the advent of SPAs, but I'm guessing lots of things are still built like this.
Guessing it reads some credentials out of environment variables. The client side example shows the server issuing a token so I guess it's only the server that has/needs the credentials.
When we built Kitemaker [0] we elected to not use CRDTs. We built our sync engine after reading the blog article Figma wrote about they didn't need CRDTs because they have the server arbitrating any conflicts. We ended up taking the same approach. It's worked out very well for us though in a tool like our "last one in wins" generally works fine and doesn't lead to a lot of surprises.
For documents, we had to do something more sophisticated. At the time we built our collaborative text editing, the prevailing opinions were that CRDTs were inferior for text editing so we ended up going with Operational Transforms. That took a LOT of work to get right and is still problematic from time to time. If we had it to do all over again now, we'd definitely challenge that decision (and may do so in the future anyway even though we have a system that works).
As a fresh-out-of-university engineer in the earlier 2000s, I had a ton of fun working at Nokia and the sheer number of devices was actually part of that. It was a blast having a stack of all of the weird and whacky devices on your desk at any time. I remember visiting some sort of internal museum in Finland at some point where you could basically see all of the devices they'd ever made. Mind blowing.
Of course getting to the software we were working on to actually run on the things was a different matter...
I think it's mainly the intensity of the sessions. You've got someone on the other end of a call so you don't really chill and take it easy. Creates some urgency to get the thing done and you're just a bit fried by the end.
I'll leave now...