I've been using ChatGTP by voice for things like cooking and house repair stuff. It's quite convenient for situations in which your hands are busy.
Other week I fixed a a water valve. After planning the thing with ChatGTP I brought the new valve. Then I described what I was seeing as I swapped the old valve for the new one to make sure everything was right. Really cool experience!
Pandas is cancer. Please stop teaching it to people.
Everything it does can be done reasonable well with list comprehensions and objects that support type annotations and runtime type checking (if needed).
Pandas code is untestable, unreadable, hard to refactor and impossible to reuse.
Trillions of dollars are wasted every year by people having to rewrite pandas code.
The challenge of running OCI containers in every OS is a bit similar to the problem of running the same binary in every OS.
I think the only true solutions are (a) OS vendors develop their own native container platforms with UX similar or better than Docker (b) OS vendors agree on some common ABI standard
From a hardware point of view, your average iPhone is definitely fast enough for many types of development.
What's really missing is an easy way to connect to peripherals, plus OS support. Samsumg has something in this direction, though I heard it's not quite mature:
I've been playing with using documents as
OpenAI embeddings for the past weeks and, at least for my use case, the results are meh. It seems sometimes just using context is not enough.
My next step is to play with fine tunning, but I have no results to report yet.
Microsoft (Azure AD to be more precise) single sign on can be configured in a few ways and SMS can be disabled.
If you really care about users not needing BYOD, you can restrict 2FA to hardware keys.
That said I think the overall sentiment of your post still stands, as most orgs just push the device issue to the user (either they need a phone of SMS, push notifications or OTP).
I imagine that using an ASIC is way more cost efficient vs using a CPU.