If you have 10 people then you make 10 dozen cookies.You keep a dozen and take the other 9 to exchange.It's also fun to make an extra dozen for sampling with coffee/tea at the exchange.It all depends on the people exchanging what else you might want to do.I always attach copies of the recipe to my exchange packages.

Please do what you feel is best for you and I hope your continued success with the protocol. For those who are inexperienced and reading this thread, all too often low and non-threat data miners and tracking cookies are recognized by some users (not speaking of any member here) as spyware/malware and malicious. In most circumstances these cookies as well as most others, are non-invasive, non-threatening and safe. They tend to be more of a privacy question than a security question. If any user feels a desire to be focused on the threat of cookies so be it, but I ask users to remember if they are delivered on your system between removals why isn't there damage created during their short-term stay? They are not isolated nor are they dormant. Now the disclaimer: Yes there has been cookie oriented threats in the past and likely will be in the future. By there nature and design they were quickly defeated and removed with standard applications. However, this potential threat is undoubtedly of less concern than the other threats we face; rootkits, keyloggers, viruses and bots. Be safe, be aware, and use your protection utilities in a systematic manner. DA

No, this isn't a good candidate. It has baking powder, which will lose part of its potency if it has to wait. You need to chill to make slice and bake work nicely. And "final dough will be slightly softer than most cookie doughs" is sort of the opposite of the concept. BUT, there are other ways of doing the "divide dough into 24 equal pieces". The fastest and easiest is to make it into a square on your cutting board--use a square dish if you need a mold--measure the sides and even them up (it's cookies--it doesn't have to be perfect, just more or less), and make marks dividing the square by four in one direction, and six in the other. Yes, the divisions won't be square, but they will be equal sized. You can either eyeball it or use a ruler. Use a big knife, a granton blade carving knife is ideal, but any long thin knife will do, or even a heavy wire, and cut as straightly as you can along the divisions. The description is a lot more involved than the doing. Separate the rectangles and either do a quick roll into balls (-ish) with your palms then squish as usual, or just put them on the baking sheet and squish as is. If you're using a cookie scoop, however, the above will save some actual effort, but I don't know that it will save much time if you scoop dump and go, then come back to bang, bang, bang flatten the whole sheet. Unless you're the type to fuss over each scoop trying to get it even...

Cookies are bits of data that a website can be allowed to store to a text file on your computer. That text file is stored so that it can be used by your browser's software and the websites that you visit. Websites will most often use a cookie to store your password so that you don't need to re-enter it each time you visit the website. If you clear your cookies for a website (e.g., houzz), then it doesn't find your stored cookies (e.g., password) when it checks. Therefore, it makes you enter it anew. Cache is different.... in this context, it's a stored copy of what came from a website/page that you visited. Sometimes when you visit a website URL, it will simply display what's in cache (stored locally) rather than hit the remote webserver to download a fresh copy. Have you ever heard the term "force a reload" or "refresh" on a browser/webpage/website? When you do that the browser is being instructed to go to the webserver to get a fresh copy and ignore what's already in cache. HTH!