3 ms·

It is safe to say that Computer Engineering has a problem with enabling knowledge transfer.

jauntywundrkind 1y ago
Yes! But it's also obvious that the industry doesn't have a prayer to ever reform. Stuck between proprietary and NDA's chips everywhere, using proprietary and NDA's toolchains and development kits, to product proprietary DRM'ed products. This is an industry that is about as far from the light of science & enlightenment as it is possible to get, ensnared as deeply in the entangling anti-human anti-science Intellectual Property qualgmire-hell as can be got. Oh sure plenty of science goes it! It's fantastically interesting & technical! But aside from some Application Notes write-ups trying desperately to help move the practice along, move it out of jank, knowledge goes in, but it doesn't ever come out! There's such a lack of peershios with which to practice science, to report your findings to, to replicate works on. The software world talks about its patterns and practices. The biggest industries on the planet are building software like wild AND are mad into open source. But... computer engineering is the shadowland, where no talk nor victories that happen there are allowed to be shared, where nothing escapes confinement. What a fucking plagued awful land of people unable to ever do the right thing, unable to bring their work out of the dark & into real civilization.
- nyarlathotep_ 1y ago
  I can find 1000s of posts or blogs or whatever on every React nuance, Rust thing, LLM trend, or whatever, but nothing even describing what "real" embedded programming looks like in any fashion (I'm not counting blinking an Arduino LED here). What does writing ABS module software look like? I'd actually love to know--it's not an area where you can "vibe code" your way to a 'working' product.
  - gmueckl 1y ago
    Can't speak for cars specifically, but other software built to comparable standards requires a super rigorous process including detailed specs, risk analysis and mitigation, detailed design, comprehensive automated and manual testing against the soec including test coverage, tons of documentation on everything and finally a third party certification on everything. The process is so far removed from typical web and business slop that it's an entirely different world of its own.

Yes! But it's also obvious that the industry doesn't have a prayer to ever reform. Stuck between proprietary and NDA's chips everywhere, using proprietary and NDA's toolchains and development kits, to product proprietary DRM'ed products. This is an industry that is about as far from the light of science & enlightenment as it is possible to get, ensnared as deeply in the entangling anti-human anti-science Intellectual Property qualgmire-hell as can be got. Oh sure plenty of science goes it! It's fantastically interesting & technical! But aside from some Application Notes write-ups trying desperately to help move the practice along, move it out of jank, knowledge goes in, but it doesn't ever come out! There's such a lack of peershios with which to practice science, to report your findings to, to replicate works on. The software world talks about its patterns and practices. The biggest industries on the planet are building software like wild AND are mad into open source. But... computer engineering is the shadowland, where no talk nor victories that happen there are allowed to be shared, where nothing escapes confinement. What a fucking plagued awful land of people unable to ever do the right thing, unable to bring their work out of the dark & into real civilization.

nyarlathotep_ 1y ago
I can find 1000s of posts or blogs or whatever on every React nuance, Rust thing, LLM trend, or whatever, but nothing even describing what "real" embedded programming looks like in any fashion (I'm not counting blinking an Arduino LED here). What does writing ABS module software look like? I'd actually love to know--it's not an area where you can "vibe code" your way to a 'working' product.
- gmueckl 1y ago
  Can't speak for cars specifically, but other software built to comparable standards requires a super rigorous process including detailed specs, risk analysis and mitigation, detailed design, comprehensive automated and manual testing against the soec including test coverage, tons of documentation on everything and finally a third party certification on everything. The process is so far removed from typical web and business slop that it's an entirely different world of its own.