Abstract As code is now an inextricable part of science it should be supported by competent Software Engineering, analogously to statistical claims being properly supported by competent statistics. If and when code avoids adequate scrutiny, science becomes unreliable and unverifiable because results — text, data, graphs, images, etc — depend on untrustworthy code. Currently, scientists rarely assure the quality of the code they rely on, and rarely make it accessible for scrutiny. Even when available, scientists rarely provide adequate documentation to understand or use it reliably. This paper proposes and justifies ways to improve science using code: 1. Professional Software Engineers can help, particularly in critical fields such as public health, climate change and energy. 2. ‘Software Engineering Boards,’ analogous to Ethics or Institutional Review Boards, should be instigated and used. 3. The Reproducible Analytic Pipeline (RAP) methodology can be generalized to cover code and Software Engineering methodologies, in a generalization this paper introduces called RAP+. RAP+ (or comparable interventions) could be supported and or even required in journal, conference and funding body policies. The paper’s Supplemental Material provides a summary of Software Engineering best practice relevant to scientific research, including further suggestions for RAP+ workflows. ‘Science is what we understand well enough to explain to a computer.’ Donald E. Knuth in $A=B$ [ 1] ‘I have to write to discover what I am doing.’ Flannery O’Connor, quoted in Write for your life [ 2] ‘Criticism is the mother of methodology.’ Robert P. Abelson in Statistics as Principled Argument [ 3] ‘From its earliest times, science has operated by being open and transparent about methods and evidence, regardless of which technology has been in vogue.’ Editorial in Nature [4]