Frosty Knickers

A person who is sexually frigid and unlikely to be sexual, even with a reasonable partnership match.
Frosty - as in barren, frigid, unfertile, too cold to show any signs of life in there/unwilling to have any life in those knickers/panties under any circumstances. Frosted over so as to be immovable to allow access to what is clothed by the knickers/panties.
Not to beconfused with voluntary or enforce chasticy, Incel, celebacy, sapiosexual or demisexual.

"That person has Frosty Knickers/Panties - they resist any kind of sexual talk or respectful approaches because they're irrationally oppositional to having sex with their perfect Partner who they would otherwise find highly sexually attractive."
"Damn girl! Have you got Frosty Knickers now you've got me into your bedroom, I thought you were joking about looking at your etchings."

What would Dolly do?

I'm assuming it's a secular alternative to WWJD, substituting Dolly Parton for Jesus. Elementally it means, respond to adversity by demonstrating that you're not being dragged into negativity and moving on instead. Perhaps my puffing up your chest or holding your head high. Or just because you feel like doing those things, regardless of any adversity.
Inevitably highjacked by faux feminist and pop feminists with self-congratulatory memes about achievements that aren't gender specific.

Person one: "My partner done gone and left me for another woman. what would Dolly do?"
Person two: "Correct your grammar and self-reflect, don't be judgemental or infer that everyone of a certain gender act the same way" *sprays hair heavily and moves on*

single function application

A computer application that only covers a single, distinct, area of functionality with little or no integration with other processes or other applications e.g. a simple calendar application or a business application that has complex functionality, but on for a distinct business process function such as creating and approving Purchase orders, but no direct integration/inter-dependencies with others functions, such as Financial Reporting or Stock Control in external applications or where activated as part of the same application (therefore not a Single Function Application).
The point is that Single Function Applications more likely to be SaaS products as they are less likely to need customisation or additional coding specifically for an individual installation (customer) or Integration testing.
Therefore Single Function Applications may be easily developed with traditional Agile values, rather than needing a Hybrid approach (e.g. a 'Waterfall' Integration and/or Regression Test phase after development Sprints and before Shipping each Release).

I'm developing a Single Function Application which doesn't integrate with any other areas of functionality, so I won't need to do any Integration testing with other applications of other areas of functionality.