Developers (mostly in the beginning stages of their career) often tend to use OPTION (RECOMPILE) an an excuse for introducing more and more adhoc T-SQL into the application and then tend to eliminate SP's altogether. And then they reach a stage where plan cache gets filled up to the brim again and again.
I'm not a native speaker, but this part in the blog is a little bit confused for me. I understand that T-SQL can fill up the plan cache by the described reasons in your article, but the opton RECOMPILE will not cache any statements in the cache. The explanation is also only related to T-SQL statement usage instead of SPs and not to the RECOMPILE option?
Instructs the SQL Server Database Engine to discard the plan generated for the query after it executes, forcing the query optimizer to recompile a query plan the next time the same query is executed.