https://www.perforce.com/blog/kw/NASA-rules-for-developing-s....
272 karma · joined January 26, 2016
https://www.perforce.com/blog/kw/NASA-rules-for-developing-s....
If your job is safety critical software I guess they'd pay for relevant training. If not, looking at the course outlines at least lets you know what trainers think are important topics, for example
https://www.feabhas.com/content/robust-software-embedded-sys...
One training course I had talked about how to design a system with integrity while integrating open source code of unknown integrity. Since software quality and safety critical software depends so much on process, then open source by default isn't built to any integrity level. If a system needs two independent implementations of a calculation, an open source code base would never show that.
If you have an experienced safety engineer, ask them about how typically to design the system and software to make the safety case easier and they'll have some ideas of what needs to commonly be done. It depends on the integrity level what strategy and process needs to be followed.
It's not just the code style, but there's a broader mindset that you need to develop.
There's also good presentations and lectures that come up from time to time here or on YouTube where the failure of safety critical software is studied. These can be excellent case studies: Such as: https://news.ycombinator.com/item?id=31236303
Maybe the company would pay you more but the recruiter either:
- told them you're cheap, mistakenly or not
- wants to get you in cheap so they get follow on work
- doesn't know you expect a lot more
- is getting a bonus if they find suitable cheaper candidates
- doesn't yet know what you're telling us and so hasn't passed on the feedback on the poor offer.
- would be happy to fight for higher pay as they're paid a % of your annual rate.
A claim could be A->C
Supported by separate claims: Since A; A->B; B->C, etc?
See these links for more: Question asked in the EU parliament: https://www.europarl.europa.eu/doceo/document/E-8-2018-00081...
https://news.newenergytimes.net/2020/11/03/open-letter-to-it...
UK: Give Beauhurst a call: https://www.beauhurst.com/
Another source might be to talk to people at accelerators/incubators. Scotland: https://www.thisiscodebase.com/
Particularly I'd mention Eric Arcenaux: https://www.youtube.com/watch?v=Q5hS7eukUbQ
Listening to podcasts by performers about their daily routine might be useful if you want to know what they need to do to care for their voice in order to be able to perform daily.
i.e. a sideways move into a different team in the company or asking for a mentor (e.g. 10 years ahead) outside your team might make a big difference to your job satisfaction.
"Glasgow's first Intensive Therapy Unit was developed, consequent to a large outbreak of poliomyelitis in Denmark, with many of the patients there requiring artificial respiration." https://www.amazon.co.uk/Pathology-Human-Infections-Associat... This led to a pathology department, and my grandfather working in that his whole life (specialising in infectious diseases), and then writing a 3 volume encyclopedia on the subject: "The Pathology of Human Viral Infections and Associated Conditions"
Death.
Being able to distinguish between "my tags" and "public tags" would be necessary.
Hire people (on good money) with the personality type that likes to find problems. If the team is all composed of "Mr Right-Now" and no "Mr Right" personality types then it will move very fast and have lots of issues. A diverse team helps.
TDD tries to insist tests are developed first, partly to ensure they're not skipped.
Reinforce the message: "Measure twice, cut once".
Good leadership and top-down support to make changes are important. If they won't care enough to stump up the money and follow through to check it's happening, don't expect much change.
Fuel-cell/electric hybrids are a different value proposition and will keep going.
But they'll increasingly drop gas hybrids and jump to full electric, perhaps after the next generation of vehicles.
Clyde Space will sell the bits to make a cubesat or even build it for you. https://www.aac-clyde.space/
Alba Orbital do the same thing at a smaller (& cheaper form factor): http://www.albaorbital.com/
Add a sensor that you can sell the data from. Make a deal to sell the data. Use the money / guarantee of the deal to raise money to fund the satellite development and launch.
To open the notebook and be able to start typing (or pasting in from email etc) is a very low barrier of entry, compared to say using a Confluence wiki page and having to login then click edit.
I understand from a Louis Theroux documentary on gambling addicts that it is the feeling of the near miss that is actually addictive and not the feeling of the win. Gambling addicts are used to winning and so they don't get a buzz from that.
I've never tried this, but as an idea: can you redirect their questions to a full team chat and get their own team members to solve them? Saying "ABC asked XYZ" might put the onus on them to up-skill their team and it might also show you who's able to answer their questions on their side. After a while they might just ask their questions directly in that.
Speed: Does the server have enough RAM? Is it running with the recommended database for fastest use? Atlassian offer some guidance: https://confluence.atlassian.com/doc/performance-tuning-1302...
I work in embedded so we reuse: device drivers, MCU abstraction layers, communication protocols, key (to our business) areas of application level logic.
Reusing components is about reusing design, which ultimately means you're reusing/extending a specification as well. If up front you can define the specification to be standard for a bunch of projects you can plan for a lot of reuse and justify the upfront work.