Counter Question - Are you talking about R&D or production code?
All of the above answers apply to R&D groups developing new ideas to improve existing inventions or to provide new scientific adventures that were not previously possible - in those cases I agree.
But there are still many people who write code that actually deploys with the hardware. As with any major effort, you don’t want dreamy dreamers to come up with a radical decision to be guys who really realize what can risk a person’s life. These are two different tricks and two different careers.
I agree with the academic research approaches you talk about R&D groups.
But if you want to write production code, check out the quality control and quality control procedures. All mentioned areas include development contracts with the government, which will require the highest degree of due diligence and care, because they cost a lot of money, they can risk at least a few human lives, and in the case of a nuclear facility, they can destroy entire groups population. You want to make sure that the code has passed many reviews and testing!
To get into the development team, learn some of the high-level development processes and methods - CMMI, Six Sigma. Learn as much as you can about testing and life cycles. Work in an internship close to this area, especially if the internship grants you permission — most of the work you mentioned may require defense permits, and that’s a huge leg if you graduate from college with clearance in hand.
bethlakshmi
source share