We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
The problem could be that you think you know more than you really do, and aren't willing to listen to the voice of experience. OTOH, there's always a resistance to change, especially if you're working outside established norms.
Absolutely. I have an electronics degree, and I run into developers with CS degrees all the time who are not well read in software engineering. Asking someone what their influences are should probably be a standard interview question.
mattydread23 (2793761) writes "Are we finally going to outgrow the days of idiot lights with obscure messages like "Check Engine?" Researchers at IHS Automotive think so. Your car is already collecting a ton of information, from how much gas you're using to how often you play the radio. As sensors get more accurate, and carmakers find ways to transmit this information back to dealerships, we could finally get cars that actually give you intelligent warnings before breaking down. Plus, a better interior experience based on your actual usage." Link to Original Source
Technical side gets plenty of blame. Where are the software metrics that can give a rough estimate on how much effort a project should take? Not easily available, because most of the software world resists FPA.) Where are the reusable domains? Non-existent, because most of the software developers want to stay at the 3GL level.
In the '90s, EEs at the company I worked for were being "reskilled" to do software development. The positions they occupied weren't being refilled (at least, not in the USA). There has been no surge in demand and a high unemployment rate, so why would students choose to pursue it as a degree?