3 ms·
> Namely, there is a broad social perception that hardware design is "real" engineering, and that software is a joke. Yup. Not just in Asia. The US suffered fr
by ChrisMarshallNY 4y ago
> Namely, there is a broad social perception that hardware design is "real" engineering, and that software is a joke.
Yup. Not just in Asia. The US suffered from that, as well. It may have changed (for the US), by now, as I spent 27 years at a Japanese hardware company.
I spent most of my career, as a software dev at hardware companies, and got the brunt of that crap. It was infuriating.
During my time, I wrote some very good software. In the early days, when my team was given a lot of leeway, it was sent out, and got [mostly] positive reviews.
As time went on, Japan got more and more involved with/in control of the software development that we did, and threw more and more restrictions at us.
We were forced to do a standard hardware-centric waterfall development process. If I even mentioned the word "agile," I might as well have just gotten up and left the meeting, because everything I said, after that, was ignored.
They took away all of the user interface from us, and we were just doing "engine" work, which was actually pretty cool, but, they sucked at UI.
Towards the end, I was reading terrible reviews about our software, and tried writing stuff that would directly address these gripes.
My work, and any similar work from my team, was ignored. Instead, they had some disastrous relationships with external companies, under (I assume) the impression that we were not capable of writing "modern" software, and these folks were (they were able to write "modern" software, because their work was terrible, and I have issues with the Quality of "modern" software, in general).
- nrp 4y agoIt is indeed exactly the reverse in the US currently. Pay ranges for software engineers tend to be higher than for hardware engineers at big tech companies, and many folks with electrical engineering backgrounds end up going into software as a result. Also similarly, people building hardware inside of software companies tend to have to put up with mismatches in expectations, including questions around why they can’t build hardware in an “agile” process!
- ChrisMarshallNY 4y ago> why they can’t build hardware in an “agile” process! That's not good, either. Hardware really needs a "measure twice, cut once" approach. It can be made more iterative, but that is expensive.
- aidenn0 4y agoSometimes I feel that "Agile" has become so diluted to mean "there are feedback loops in the design/execute process" and if that's the case then 6σ is an "agile" process for hardware.
- ChrisMarshallNY 4y agoI like the spirit of the Agile Manifesto. I feel that the devil is in the details[0], though. Nowadays, the word "Agile" means "Waterfall, but with different names," or "Tear off all your clothes and run naked through the bluebells! Do what you want!" I'm really big on Discipline and Quality. It's entirely possible to have a flexible and iterative development process, but there's no way to avoid the difficult bits. They just get shifted around. [0] https://littlegreenviper.com/miscellany/problems-and-solutions/ https://littlegreenviper.com/miscellany/problems-and-solutio...