emptor

I have no problem with that, whoever buys their bonds accepts the risks, and the rate is market driven, caveat emptor rule applies.

As always, the clarion call on the internet remains - Caveat Emptor - Buyer beware.

The claims of personal responsibility and caveat emptor can only go so far.

I think caveat emptor absolutely applies with bootcamps, but there are also ones that are certainly worth the money.

If and when there's serious money on the table, you've had your caveat emptor and you won't have any say in how things go down.

MIT's Technology Review occasionally puts out interesting stuff (but caveat emptor, I'm starting to develop some doubts over their journalistic skills).

Don't know if this is scientific so caveat emptor etc.

Imagining that I was given caveat emptor then excuses the future action.

Caveat emptor: completely out of subject.

While it won't specifically detect whether or not mileage reporting has been tampered with, it does signal to a buyer that the software is or was non-stock, and therefore all bets are off, caveat emptor, etc.

Or one can see the difference in Linux distros in how RH is commited to maintaining a certain major release for years, while on the other hand you have rolling distros that come with a caveat emptor style warning.

Far from being pro-consumer, Bitcoin is practically the logical conclusion of 'caveat emptor', trying to take Internet-based businesses back to the days before Upton Sinclar's "The Jungle" was published.

And caveat emptor to anyone responding to this, "you have to embrace change!!!" is exactly equivalent to "I don't give a shit what happens to poor people."

Should one just be super passionate and expect the employee to have a “caveat emptor” approach, or is there a minimum threshold of kimono-opening one should do in order to advise potential hires of the riskiness of both the market generally and one’s startup specifically?

Caveat Emptor: I used Vim for a long time, but switched to Emacs about 7 years ago.

Caveat Emptor: I did not test this since somehow the Debian package of libgit2-dev seems not to include the GIT_* constants.

Yes, and we have thousands of years of 'Caveat Emptor' shenanigans to point out just how necessary consumer protections are in this space.