Consider working on genomics

There is a significant gap between how software is currently developed in this space versus how it should be developed. The vast majority of genomics-related software is not written with speed or reliability in mind. Too often, projects have no documentation within the code itself and no tests. Instead, a single individual who built the tool and has worked with the code since its inception is solely responsible for ensuring that the results "still look good" between releases (in an ad hoc manner, no less)—a claim that I think is incredibly generous given the breadth and complexity of evaluating genomics results. This state of affairs makes it difficult for anyone other than the original author to contribute to these code bases, further cementing the one-maintainer policy. This is not a good position for our field to be in. Many of the projects that are critical to the foundation of genomics are reaching or have eclipsed the ten-year mark. How much longer can we expect these individuals

saved by

• Yutaro Shimizu