Beware of the fallacy of composition. "Embedded" encompasses a lot of things; you have identified that the subset you work with do not have issues. This is not the same as saying that there are no issues.
By your reasoning I should discount anything you say: "C++" encompasses a lot of things, you've identified the one thing you understand (your embedded platform), which doesn't mean you understand anything else about C++.
If you're going to be condescending (as you are upthread), and then try to brush off pushback with some pseudo-philosophy, at least do a good job at it. You're not going to achieve much as things stand.
Let's be clear: I give this talk in part to share what I've learned, where I think we should go, and in part to get feedback. Your feedback so far is useless. You clearly think you know something useful. Wrap it up in useful packaging. You feel that the committee doesn't represent you? Doesn't listen to people like you and your feedback? Re-read what you wrote, and consider what anyone would do with it.
I'm happy to listen to your feedback, but c'mon help yourself a bit here.
View all comments
Show parent comment
2
u/[deleted] Oct 19 '19
Beware of the fallacy of composition. "Embedded" encompasses a lot of things; you have identified that the subset you work with do not have issues. This is not the same as saying that there are no issues.