I've been taking a break from work for the last few weeks, so missed much of the brouhaha over the McKinsey developer productivity article. But I'm sure that I could not write a better response than this one from @tastapod
https://t.co/3PlzZ37kgb
A common mistake: "Let's abstract this in case we want to replace it later."
Examples:
🚫 "Let's abstract React in case we switch JS frameworks."
🚫 "Let's abstract Tailwind in case we switch CSS approaches."
🚫 "Let's abstract Mongo in case we switch Databases".
This is typically a waste of time, and often hinders current use too.
Why? Because to effectively abstract something, we need to know the API we're abstracting.
But we have no idea what a new technology's API will be. Thus, we have no idea whether our abstraction will work with the new technology.
In summary, abstraction can be useful. But avoid abstracting merely to support changing to some unknown future technology.
@davidfowl SslStream with chain validation from a `CaFile` .. as in other TLS implementations such as GO https://t.co/z7Mo9o3jxo or Python https://t.co/8642X71SGW
I promised I would be recording a short video to help people get started with @ZephyrIoT on the MXChip #AzureIoT DevKit. It's out now! I know many people in my network will want to try this out 😊
https://t.co/VwwSpif61P
#iot#embedded#opensource#MVPBuzz@MSIoTDevs
BREAKING!
After succesful referendum at Facebook 97.9% of employees decided to drop @reactjs and instead will focus on rewriring everything to @vuejs. The react core team now works on Vue 4.
I'm so excited that I get to share hosting the #IoTShow with @vavillaiot. Here is her first one with @simpleiot discussing OTA updates for microcontroller with the new Azure middleware for #FreeRTOS and a nice demo using @EspressifSystem#ESP32 boards https://t.co/2uSCXeDw31
@FreegoUS I ordered a bike last month via Amazon. The tracking information provided is incorrect and I don't have a delivery date anymore. Sending emails and get no response. Can you help?