All deposit of USDC automatically converted to BUSD.
Actually it makes thing easier for user because now USDC and BUSD always calculated as 1:1 with no swap fee. Crypto pair are more lean since they only need to pair with BUSD.
Options to withdraw USDC still available and will use BUSD balance.
You misses where Binance doing automatic conversion for any deposited USDC to BUSD. So every USDC deposit will counted as BUSD.
Withdrawal using BUSD and USDT is still available. Even USDC on some chain are still open. As I understand they just need time to replenish their USDC.
My team use merge in the past. And we found out in git, merge commit may contains it own changeset. Our code suddenly missing, and when we check on both history, commit look fine. Lo and behold, file deletion happen on merge commit. It bite us hard and I never trust merge commit again. Its very hard to read on complex feature merge.
My team now only use rebase, clean up commit using squash, and fix conflict before landing commit on master branch are kind of natural using rebase. Lead developer also have easier time to check file changes.
The way npm install always check latest package version and use them, even if package lock already exists. Which broke apps build many many times due to developer does not recognize this behavior. I know there are npm shrinkwrap and npm ci. Its just other package manager usually follow lockfile on install and have other command to upgrade the lockfile.
Also npm install download gazilion file for each dependencies. With deep directories.
In the past, there are problem because npm way of installing dependencies and hitting this infamous windows file path length limitation.
All are now already fixed or have alternative. But at that time, composer definitely much simpler and reliable.
I used to use Ubuntu for server. Not choosing Debian because of shorter support time and old package.
And then Ubuntu botched some updates on their LTS version. Also they automatically start services after installation. I might want to reconfigure stuff before starting services.
So here I am, with Centos, reliable updates and if I need exotic application, I ran it under docker or podman.
I like to walk short distance with lids open to maintain wifi connection as I usualy keep remote connection to server. For longer walk distance, close the lid for easier walking.
Other factor also contributes to the demise of Sony phone division. Here in my country, Sony Z1 and Z2 boom as they are probably the first premium phone with nice camera and waterprof body. But bad aftermarket support and service destroy that advantages very quickly. Nowdays almost everyone avoid Sony smartphone. Either you choose phone with more support and service center such as Samsung or go to other way with Xiaomi (cheap with almost non existance official service & support).
Have been bitten by docker upgrade from FC21 to FC22 and docker-fig upgrade on FC21 from fedora package. I have faced problem ranging from docker daemon refusing to start, failed to run container, and SELinux alarm ringing every now and then. Not the best developing experience.
Switched to Elementary(Ubuntu based distro) combined with docker repo now.
In my opinion, FC is more suited to lightweight work (email, word, spreadsheet).