We didn’t get similar run times with Haskell.

Rust let us abstract even file types (path to a fastq file, fasta file, annotations, etc) with no run time costs. This eliminate many bugs at compile time.

You may say that we can get it in C too, and you will be correct. But in C we spend our time on herding pointers. Research is given X money for N months (sort of), so we have time constraints on development time.

If we do bit wise work, the compiler tests our base types.

Not to mention multithreading just works. Even big projects like BLAST had bugs that led to wrong results due C/CPP horrible multithreading. We encountered two more tools that had similar bugs.

I think that if someone ever does a meta-studies of research code written in C it may get papers retracted.

After fixing, now that you are expert, please migrate the regex to our new language.

It is easier to safely optimize Rust than C, but that was not the point. The point was on correctness of code.

It is not unheard of for code to run for weeks and months. I need the code to be as bug free as possible. For example, when converting one of our tools to Rust we found out a bug that will lead to the wrong results on big samples. It was found by the Rust compiler! Our tests didn’t cover the bug because it will only happen on very big sample. We can’t create a test file of hundreds of GB by hand and calculate the expected result. Our real data would have triggered the bug. So without moving to Rust we would have gotten the wrong results.

I used Gentoo in ancient time when kernel updates took a whole day. A modern computer can rebuild in an hour, a good one, even faster. I’m not a kernel developer, but I don’t think they need to rebuild the whole kernel for every iteration.

And as for Rust, I’m doing bioinformatics in Rust because our iteration time is order of magnitudes longer than a kernel build, and Rust reduced the number of iterations required to reach the final version.

The average user that will get to join-lemmy will GTFO.

The average user gets their Google account by opening their device and going step by step with nice animations.

Find a person that already has an apartment, bills, work, relationship and isn’t working in tech.

A. Ask him to join lemmy. Ask after a month if it happened (spoiler, it didn’t). B. Help him open an account, check after he month if he kept it.

The average user that will get to join-lemmy will GTFO.

The average user gets their Google account by opening their device and going step by step with nice animations.

Find a person that already has an apartment, bills, work, relationship and isn’t working in tech.

A. Ask him to join lemmy. Ask after a month if it happened (spoiler, it didn’t). B. Help him open an account, check after he month if he kept it.

Been a TA when chatGPT was released. Most students shot their own foot this way before we figured what was happening. Grades went from bell shaped to U shaped. A few students got 85+, the rest failed, it was brutal. Thought I failed my students horribly before I found out it was happening in all classes.

If you actually stuck in such a situation, solve as many problems as you can. An approach that will work for most people:

1. Try to solve
2. Fail
3. Take a peek, understand your failure. If the peek didn’t include full solution, go back to step 1. Else continue to step 4.
4. Move to the next question and go back to step 1.

Make sure to skip questions if they are too easy. Evey 4~ hours take a 20 minutes nap (not longer than 25 minutes). If you actually manage to solve enough problems to pass, go to sleep, 4.5 hours or a longer multiplier of 1.5 hours.

After the exam go back and solve all homework yourself. DO NOT cram it, spread it or you will retain nothing long term.

Good luck.