I implement protocols to communicate with various hardware (RFID, LiDAR, etc). Most of these communicate over sockets. Some still use serial. I have a library I wrote of socket routines that I use, so it's not like I re-implement that every time, though. And for this, I'd really rather use my library than a 3rd party in case I have to dig in and see what's going on.
As long as it is ethical, doing the "right thing" is doing what you're paid to do. If that means, for example, ship code that you might not like or think is not perfect, that's fine. It's not your code.
Don't worry, if you're still coding at 50, you'll have learned that you are not your job. As Elsa says, Let it go.
There is speed and there's the perception of speed. Some code (games) has to run fast. But most of the code we work on has to only have the perception of speed. If you're loading all of your resources and making the user stare at a twirly, you're doing it wrong.
Question, when FedEx says "Southwest Abort!" and then the controller tells them to turn right and Southwest says "negative" is that because they didn't have enough runway to do either?
Relative to other iPhones, yes. I read that it accounts for 3% of iphone 13 (Pro, Pro Max, mini, standard) sales. The 13 line itself accounts for about 75% of sales. If Apple sold 40M phones per quarter, that 120M of the 13 line, so 3.6M of the 13 Mini. At 699, that's a 2.5BN business. Not too shabby.
> Ubiquiti’s stock price has grown remarkably since the company’s breach disclosure Jan. 16. After a brief dip following the news, Ubiquiti’s shares have surged from $243 on Jan. 13 to $370 as of today.
I get it, it's Apple and it's great and all that.
I'm just not going to wear that on my face.
I'm not.