Crabs holding each other’s pincers into a crab train.

If you swallowed then yeah, extra protein.

If you find half a worm, you just spit it out, cut/bite out the wormy part and continue. Can’t throw the whole fruit. Although the worms I remember in guava make hard shells around them as they eat, so most times you bite into it, know immediately, and throw that part.

Wow I have opposite problem. I don’t like reading papers that much. And while I do write I don’t like to spend too much time there either, so I just end up procrastinating by making new things with plots, analysis, codes, helper scripts and such.

As someone who has been working on a project involving a network (directed graph) with nodes that need references on both sides, I do agree with many points in the article. And yeah the burrow checker isn’t perfect, as someone who came from C I do get to points where the logic is fine, but burrow checker doesn’t get it and I’m like “C would let me just do it”.

But I think I don’t agree with the parts about it not getting better. Author said he’s using it intermittently for a few years, I also have been using it for last few years and now I just write things the way rust expects it. And I think it has helped me not worry about a lot of runtime bugs. I just worry about the logical bugs and that’s about it.

Not perfect, but I think it’s pretty good. Also if you really want to force rust to do things, sometimes a little unsafe rust gets you there.

Honest opinion programming is easy and fun when you learn it and it saves you time and allows you to test your ideas. Creating something gives you dopamine.

Problem is before people even try any programming for themselves, they are introduced to it through school or work where they have to do it for homeworks or analysis while also learning new things. And they hate it.