3 ms·
If you absolutely can't persist and have the money to take some risks, you could consider the scientific computing space which in some cases still uses FORTRAN,
by sushshshsh 6y ago
If you absolutely can't persist and have the money to take some risks, you could consider the scientific computing space which in some cases still uses FORTRAN, though I imagine most things are in C now there.
- soganess 6y agoWouldn't the legacy codebase be a turn off for this individual? Plus, no shade intended as I do scientific / academic code professionally, but for historical reasons a lot of scientific code has one goal in mind; be as effing fast as possible, no matter the cost. Often times projects like WRF or BLAST achieve this end to an impressive extent, but there is a reason the most readable code is not always the fastest. The latency / throughput budget of a project can be divvied up in a lot of different ways. In your mobile app it's likely best to avoid optimization for clarity; so you might overspend in the name of maintenance or easy of extension. That said, if this was the 80s and you were attempting to sequence genes, you are probably thinking "clarity be damned we'll just rewrite it later when computers get fast." That is what a lot of scientific code looks like. It is written just as the idea is possible, probably a little before it is possible. As a result there are esoteric optimizations everywhere and questionable architectural choices as far as the eye can see, all in the name of "making it actually happen."
- non-entity 6y agoI mentioned this is another thread the other day, but every "scientific programmer" job ive seen basically asks for a scientist who just happens to be able to program.