[–] 1 point 2 weeks ago (2 children)

Spending your day reviewing code churned out by an LLM, is a soulless and tedious way to spend your life.

Someone has always had to review the code. And the author has always been responsible for their PRs meeting a quality bar. I don't see how this is any more soulless or tedious than before we had LLMs. Maybe you just never enjoyed reviewing code in the first place, and now you have to do it more?

  • source
  • parent
  • context
  • [–] -1 points 2 weeks ago (4 children)

    I think you're thinking about this in a very negative way when you also have the option to see it as an opportunity. You said yourself that now you're focused more on design and architecture, and most of your time is spent reviewing code. That sounds like a relatively good place to be, assuming you're happy with the quality of the code. Now you can spend more time solving new, harder problems that you couldn't before.

  • source
  • [–] 1 point 2 weeks ago* (last edited 2 weeks ago)

    I know what you mean, but this is also essentially the same rhetoric that actual racists use to refute good policies like DEI. Diversity is a good thing, and I'm not sure you can achieve it by letting everyone self-police their behavior towards someone of a different race. Racism simply exists in our culture whether or not people are aware of it, so we need policies that counteract it.

    Maybe a more persuasive way of saying the same thing: if you agree that some ethnicities or social demographics are historically disadvantaged and need more help than others, why would you not try to focus policy to prioritize their needs? It's similar to making policy that reduces child suffering at the expense of some freedoms for adults.

    That said, I also believe it's good to try making policy that doesn't explicitly target specific races if possible. For example, strengthening workers' rights in general improves the lives of an entire economic class, and coincidentally it would disproportionately help Black and Mexican people (per capita).

  • source
  • parent
  • context
  • You are correct to point out the distinction between race conditions and data races. Rust only rules out data races.

    I don't know whether the race in question was a data race or not.

    I would still wager that Rust code generally has fewer race conditions than C, given that mutable aliasing can be used as symbolic prevention of race conditions, i.e. your &mut T doesn't necessarily need to hold data; it can represent some domain concept.

    aren’t language specific

    There are actually languages that guarantee deterministic concurrent execution, and this can rule out larger classes of race conditions than just data races. See the Bloom language and CALM theorem.

  • source
  • parent
  • context
  • view more: ‹ prev next ›