Yes! This is exactly why I continue to use Arduino for both personal and "work" (various non-industrial one-off widgets), despite having been literally laughed out of the room by embedded software and hardware engineers for even suggesting it.

Like for one project as a student, we had to make a dozen or so units of a custom data logging thingy. The plan was to use STM boards, but I suggested using Arduino software/libs because all the hardware was supported and we didn't really need anything STM-specific. Eyes were rolled, something to the extent of "Arduino is for amateurs and children" was said, so I volunteered to work on the server side instead and let them have their fun with STM32 HAL. They ended up having to interface with most things manually because libs just don't exist or aren't publicly available. Half a year later, they needed to set up a more of these units, but it was in the middle of the supply chain issues and basically no affordable STM boards were in stock. Meanwhile, the local electronics store had more than a hundred Arduinos in the warehouse. My screenshot and winking emoji were not appreciated in the team chat. The new generation now uses various Arduino (Atmel) and ESP boards with software now fully written on top of the Arduino stack with only one or two board-specific sections in the code.

I've never regretted choosing the tools that were intended for hobbyists and kiddies. They laughed at me for using Python. Of course there are good reasons for choosing the grown-up tools, but also bad reasons, and the bad reasons translate directly into costs in time and effort, lack of adaptability, and so forth. These things are normalized by the structure of the organization, but remain painfully visible to the astute observer on the sidelines. And to the users.

Amen. I've been doing embedded since forever and am continually stunned how engineers shun simple, open source tools for complicated expensive ones with no value add.

For work, I had to program on a industrial Atmel board. I was baffled by the crappy librairies Atmel provived with the board. Stuff like the I2C lib was broken and I had to patch some code that was checking interrupts flags and such. I spent days to do something I could have done in days at home, and the board was still unstable. That's why companies with non-critical sytems don't bother with 'industrial' developement boards, when it's cheaper to buy Arduino compatible boards. Oh, and the documentation and knowledge available online is gold, when compared to the crappy docs from a big tech firm,

Work stuff, or hobby stuff? If work, what industry? An environment where you are able to do ad-hoc replacements like that sounds cool as heck!

Work stuff, but in an R&D environment where nothing goes into large scale production. If something threatens to be useful, it gets handed over to the dev team. The devs are actually very good engineers, but they do use the traditional methods. Moving across platforms is a headache -- perhaps the biggest problem is that the contract shops also have their own chosen platforms, so it's hard to outsource even minor work when a little bit of extra capacity is needed. Every platform is an island.