Ah, yes: weaponizing cybersecurity requirements to trick - I mean “motivate” - higher management to do things “right.”

My thought as well, but those stones were shaped to match each other, reducing the amount of grout needed. It just goes to show the old ways still work, but you have to commit.

This is a dangerous metaphor. Remove the old wall and it turns out the new beautiful wall was leaning against and supported by it.

I get what you mean, it’s just that the metaphor could support both perspectives.

Like if the variable is then used in a function that only takes one type? Huh.

And bow to the compiler’s whims? I think not!

This shouldn’t compile, because .into needs the type from the left side and let needs the type from the right side.

I came here to laugh, not to cry!

[clicks light switch off and on repeatedly]

Welp, I guess we’re closed for the week.

I’d say I feel seen, but it’s really dark in here.

let a = String::from(“Hello, world!”).into()

I’ll see myself out.

That makes sense. I’m also involved in localization efforts. In niche cases, it’s paid off to work with the clients directly on that. You get you a good balance between correctness and day-to-day usefulness.

Since ladder is mostly diagram-based it almost doesn’t need to be localized and isn’t jarring when you use non-English variable and function names with English keywords.

Apart from being strictly left-to-right.

If he worked in Germany, did he use English or German mnemonics?

If he worked in Germany, did he use English or German mnemonics?

Industrial controls equipment made by German companies can be programmed in English or German. You can also switch languages (German/English) at any time and the IDE switches over all the keywords.

Semicolon!

Shared with my favorite blind iOS dev. Should be a good laugh!

I also can’t get the printer to work.