Elektrine lite

← Feed

@darkuncle@infosec.exchange

Post #4390743

2026-08-05 05:51 UTC

@tbortels@infosec.exchange the argument is quite simply that English is an inherently ambiguous language unsuitable for the precision needed for communicating with computers. That we can perhaps work around this, in some cases, with extra effort, is beside the point.

Replies (1)

  • @tbortels@infosec.exchange 2026-08-05 06:07

    @darkuncle@infosec.exchange Mmm... I get it. I'm not sure I agree. Mathematics proofs are in (mostly) english, or russian, or some other natural language. Legal docs are the same. You can absolutely be precise in English. We just normally don't bother because we know the entity we are speaking to can handle ambiguity. The AI can handle ambiguity. I can say "go look at the cloudwatch logs" and it knows I mean aws, and the current context - and if it doesn't it will ask. Besides - ambiguity happens in code as well. Is "1" a number? Floating point? An ascii character? In perl, it depended on context, and could change depending on usage! If I say "one time" is it really better for that to generate an error rather than DWIM? A preference to use a language you are fluent in is a preference; it doesn't make other's preferences invalid or wrong, and they aren't saying that. My point is simply that it's nice to have other options. I like not having to be pedantic and let the AI make intelligent guesses, especially since they are often correct.

    Open ##4390742