Very insightful, this helped put things into perspective.

You can’t stop peope from using AI, but at least people are being transparent.

Doing this will lead to people using AI without mentioning it, making it even harder to parse between human-origin content.

How do you guys handle redaction? I'm sure even when trusted individuals are in charge of authoring, there's still a potential of accidental leakage which would probably be best mitigated by a team specifically looking for any slip ups.

Thanks for the insight.

Team has a good sense, typically. In this case, the names of the columns in the Bot Management feature table seemed sensitive. The person who included that in the master document we were working from added a comment: “Should redact column names.” John and I usually catch anything the rest of the team may have missed. For me, pays to have gone to law school, but also pays to have studied Computer Science in college and be technical enough to still understand both the SQL and Rust code here.

Could you elaborate a bit on how going to law school helped? Was it because it made it easier for you to communicate and align with your CLO?

Probably because he could check legalities of a release himself without council. It is probably equivalent to educating yourself on your rights and laws so if you get pulled over by a cop who may try to do things that you can legally refuse, you can say no.

wrong thread

thanks %

I think it's really cool as well. Although, it does start to look a little wonky with quotes and probably some other characters and makes skimming a bit harder. Maybe monospaced fonts will start to handle this better if it gets popular?

Ruby typography support in terminals maybe?

This is pretty entertaining.

Can you please post the link once you’ve written it? This sounds really interesting