I love abstracts that has a byline with assumptions. "Attendees should be expected to have familiarity with X, Y, Z" helps a lot! And it allows me to pick the talks I want to go to that matches my level of expertise better.

Or at the very least slap a link or something to where the prereq/assumed knowledge can be obtained

And, unrelated, but HR departments suck at explaining 401k options that are available to their employees

People are clearly sick and fking tired of being forced to give up their privacy it's driving them to drink and grinding their teeth until they fall out

The point gets me every time

One of the things I think the vibe coding stuff hasn't yet really come to terms with is junior developers and owners often think the key skill for developers is ability to write code, and principal developers know the /actual/ super power that distinguishes principals is their ability to debug.

People are turning everything from bottom to top into a clusterfuck of nothing but extremely large open text fields. And it's a MISTAKE.

If anyone promotes better/safer results from open fields: be skeptical. Chances are good they'll form a reliance on this.
You'd think people would remember all of the problems brought by open text fields and why input validation matters... Alas...

It's a shame this news has to be hidden behind me agreeing to give up a portion of my freedom to read it.

A good place to look may be expert witnesses:
www.jurispro.com/category/aut...

Very much depends on context, which make and model, and how honestly they feel comfortable discussing the details of the technology used by their current employer.
Much like anything else really, just multiplied by safety. Less "super-secret" more "cya"

Need lenses that block IR. Surprisingly tricky.
Another thing about shit like this that bothers me even *more* - even the 'knowing' recorder doesn't have access to all the data being collected.