[–] 1 point 8 months ago* (1 child)

I don't even necessarily disagree, but how do you say the exact name of the fallacy you are invoking without seeing the problem in what you're saying?

There can be clear start and stop points. Why would this ever lead to regional managers as you describe? Why would it ever lead to people you simply disagree with? To argue in good faith, you need to take the point as it stands, clearly stopping at a level of someone who is "responsible for far more death." That is the argument that the above commenter posted, and there's not a good reason to extend that any further.

They got to do what they do using our system of law- so we will need to use that system of law to stop them.

Now, I'm going to step away from the context of homicide, but this is at a base an incredibly gullible point. Virtually every civil rights movement has been accomplished through breaking laws, called civil disobedience.

"an individual who breaks a law that conscience tells him is unjust, and who willingly accepts the penalty of imprisonment in order to arouse the conscience of the community over its injustice, is in reality expressing the highest respect for law." - MLK

  • source
  • parent
  • context
  • [+] -8 points 8 months ago (1 child)

    Large language models can generate defensive code, but if you’ve never written defensively yourself and you learn to program primarily with AI assistance, your software will probably remain fragile.

    This is the thesis of this argument, and it's completely unfounded. "AI can't create antifragile code" Why not? Effective tests and debug time checks, at this point, come straight from claude without me even prompting for it. Even if you are rolling the code yourself, you can use AI to throw a hundred prompts at it asking "does this make sense? are there any flaws here? what remains untested or out of scope that I'm not considering?" like a juiced up static analyzer

  • source
  • [–] 2 points 1 year ago*

    And to clarify, the deal wasn't even a peace deal. It was a "ceasefire now, then when Russia recuperates and starts again, we'll have 0 contingencies. See, what if a bomb dropped on your head right now? We can't predict the future!"

  • source
  • parent
  • context
  • [–] 3 points 1 year ago

    If the pictures are not, forced therapy is probably the best option.

    This is true, but it really depends how "therapy" is defined. And forced therapy could mean anything from things like the old conversion therapy approach for gay people.

    You might argue that these days we wouldn't do anything so barbaric, but considering that the nature of a pedophile's is very unsavory, and the fact that it will never be acceptable, unlike homosexuality, people would be far more willing to abuse or exploit said "therapy"

  • source
  • parent
  • context
  • [–] 11 points 1 year ago

    This is a smarter breakdown. I had a similar thought that this is a test to see how many people will conform to a random demand, basically fielding for which departments are fighting against his authority to know the areas to focus on.

  • source
  • parent
  • context
  • [–] 2 points 1 year ago (1 child)

    COBOL doesn't have a date type. And there were "people" in that "list" that weren't just 150 years old, and they varied in ages.

    The real answer is that the list that they're saying is people getting social security, isn't the list of people getting paid, just lists of random ages in the database, which ultimately means nothing.

  • source
  • parent
  • context
  • [–] 1 point 1 year ago (1 child)

    I think it makes sense that people who don’t have actual experience in making projects in a specific language won’t be aware of details such as the value 0 being the default in a certain kind of field in a certain language which makes it a good flag for “data unknown”.

    The whole "COBOL's default date is 1875" thing is just a lie. COBOL doesn't even have a date type.

    So the problem doesn't have anything to do with COBOL, someone just made it up

  • source
  • parent
  • context
  • [–] 1 point 1 year ago

    So spend a chunk of money to hire a team to upgrade the database that's working to one that's programmed in a new language, might will have errors, then have to fix those errors, and you'd also have to train the existing team or replace them with someone who knows how to use and maintain the new database. You'd potentially want to upgrade or change the hardware too from an old mainframe computer unless you want to only sidegrade to like C-90 since your old IBM computer won't support newer compilers. In the meanwhile there's a HUGE risk of breaking something or even just not getting anything accomplished

    It's definitely an objective that's good but if you're chasing efficiency and cutbacks, it's the opposite of what you'd want to do.

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