• 0 Posts
  • 880 Comments
Joined 2 years ago
cake
Cake day: June 21st, 2023

help-circle




  • Wild assumption.

    I don’t worship. That’s just plain stupid, at least in my opinion. Books can be read for the sake of reading them. Knowledge isn’t some weird forbidden apple on a tree. It’s something used to make informed decisions in the world.

    Please seek therapy. The psychosis is strong with this. The “us vs them” mentality is nothing short of cultish brainwashing. Worship is fine, belief and faith are fine, community building is even cool, but turning it into a cult just justifies my decision to distance myself from religion more.







  • Why not?

    Are you asking the author or people in general? If the author didn’t answer “why not” for you, then I can.

    Yes, I’ve used Claude. Let’s skip that part.

    If you don’t know how to write or identify defensive code, you can’t know if the LLM generated defensive code. So in order for a LLM to be trusted to generate defensive code, it needs to do so 100% of the time, or very close to that.

    You seem to be under the impression that Claude does so, but you presumably can tell if code is written with sufficient guards and tests. You know to ask the LLM to evaluate and revise the code. Someone without experience will not know to ask that.

    Speaking now from my experience, after using Claude for work to write tests, I came out of that project with no additional experience writing tests. I had to do another personal project after that to learn the testing library we used. Had that work project given me sufficient time to actually do the work, I’d have spent some time learning the testing library we used. That was unfortunately not the case.

    The tests Claude generated were too rigid. It didn’t test important functionality of the software. It tested exact inputs/outputs using localized output values, meaning changing localizations was potentially enough to break tests. It tested cases that didn’t need to be tested, like whether certain dependency calls were done in a specific order (those calls were done in parallel anyway). It wrote some good tests, but a lot of additional tests that weren’t needed, and skipped some tests that were needed.

    As a tool to help someone who already knows what they’re doing, it can be useful. It’s not a good tool for people who don’t know what they’re doing.








  • In the meantime, we can expect AI to be at the center of more layoff announcements —whether people believe the job cuts are solely the results of AI or not.

    If the AI bubble pops, you can bet the layoffs will be the result of AI, though not in the way people usually mean by this. Honestly, as much as I don’t want to see what it does to the world, I’m still curious what would/will happen.

    You simply cannot replace people with AI. The statement itself is nonsense. Even so-called “agentic” AI cannot replace an employee in all aspects of work. You would need AGI to approach that.

    Like the article mentions, it’s just an excuse to fire people.


  • Mixins are composition! They don’t describe what a type is (“circle” is a “shape”, etc) but rather what they can do (“circle” can have its area calculated, it can be drawn, it can be serialized, etc). Mixins in Python just so happen to be implemented by adding base classes.

    Inheritance itself isn’t really a problem. It usually only matters when you have unnecessarily deep hierarchies, where a change in a base class can change functionality in dozens of classes in an unintentional way. Similarly, it can add complexity once the hierarchy is deep enough, but only really if you throw too much into the base classes.

    Python’s ABCs are more of interfaces though, which is why despite Python using base classes to “inherit” them, a lot of that is really composition (or putting a class together from parts) rather than inheriting and overriding implementation details from a parent/grandparent/etc type.


  • Assuming you’re referring to F&H 1, that came out five years before Steam reviewed this game. It’s possible they simply became more strict over time and never revisited F&H because it never came up.

    Also, Steam’s rules (or any other private platform’s rules) are not law. Precedent doesn’t really matter. They can decide arbitrarily when rules apply and don’t apply (so long as they don’t violate anti-competition laws and so on). One would hope they are consistent, but being an organization with likely multiple reviewers, it’s unlikely they are always in sync, especially with decisions separated by years.

    A different question to ask is whether the scene you described would have passed review in 2023. I haven’t played F&H, but based on your description, it seems unlikely.