But closed source expensive tools are a problem.
344 karma · joined March 17, 2010
https://twitter.com/krigle
But closed source expensive tools are a problem.
My experience is that ESA lets the industry (and maybe universities) do most of the SW/HW development and ESA does stuff like requirements and high level management. But I have never followed a project from start to finish, only been in the aforementioned industry :)
I don't think this use case is uncommon, and unfortunately when you are multiple persons working on a shared remote feature branch you can't rebase the branch from master and then push it either.
What work flow do people who have shared remote branches use? Or do you think that way of working is broken?
I think sequentially allocated states that fact. From what information do you mean it can be deduced?
I was merely saying that for someone wanting to _start_ doing embedded work saying "go get a ___ degree" is certainly not a very helpful answer.
I'm an EE doing both embedded HW (FPGA/ASIC) and SW for a living. I still have no problem saying to a beginner that they can play around with Arduino to get a feel for things.
And disrespecting Arduino like that does not seem good either. Doing Arduino will actually teach you about both microcontrollers and electronics and there's a lot of nice modules available. Of course it is not like writing your own OS but it's a start, and you can always use the hardware and ignore the Arduino software.
The best way to get started in embedded is to begin on a project where you actually build something that you want to build. That will help you with requirements on the platform you choose, be it Arduino, Raspberry Pi, FPGA or whatever.
Those were the days. I think it was the perfect way to get started with programming :-)
Seriously? Even if we added high end embedded processors (e.g. 1 GHz ARM) it would hardly be noticeably in the car's total weight. Of course automotive manufacturers will need to think more about security. CAN is a pretty crappy protocol to start with (security wise at least) ...
But this is the road SpaceX is not taking ...
And all these techniques only protect against soft errors. I was more interested in how to mitigate against permanent errors (latchup) and tolerating high total dose when using commercial components. Will they do this by screening components which are manufactured using potential good fabrication process e.g. SOI.
Thus I don't like unnecessary merges of unfinished work, it increases the risk for breaking the tests, which will slow down development.
If you rebase your feature branch continuously then you achieve what you are asking for without merging unfinished work.
Maybe certain fabrication technologies (geometry/SOI/packaging) will produce COTS semiconductors which can take a lot of total dose. I'm not sure of the status of this. Does anybody have any insights?
I would think that the biggest benefit of using COTS is performance and developer efficiency. It is certainly possible to run Linux on the available rad hard parts (PPC, SPARC, MIPS) but due to low usage the development environment will not be as good.
Code deployed in space is not changed "if it ain't broken".