kool

So, it's not enough to work...you must drink the kool-aid and forsake your own free time and creativity.

But in that case, it's more about sprinkling in functional approaches here and there, rather than completely drinking the kool-aid.

For more of being with you, my company drank the microservices kool aid.

Probably more kool aid you drank from some politician you saw on TV.

In any case it seems you have drunk the kool-aid so I'll leave the discuss here.

But that's a kool-aid you've been drinking for too long.

I truly wish Craig would drink the Jack Dorsey kool-aid, and have an open API for CL allowing independent developers to innovate around it.

Unless you are a child of the 80s and grew up drinking Microsoft Exchange Kool Aid, there is absolutely no good reason to use Office 365 over Google Apps.

Maybe I'm not drinking enough Kool Aid these days haha.

Anyway, I guess I recommend the Kool Aid...

If you are already drinking the CI kool-aid, you might not honestly have much to gain from Docker that would compel you to invest time and effort into using it to host your apps.

This is someone who has either not only drunk the kool aid, but is already on their way back from the store with another carful of it, or someone with very limited experience of business.

No amount of kool aid, great ideas and "strategical thinking" will help you unless you have someone who understands the space you're targeting.

These kids (I'm 30 now, I can totally pull off the crotchety old man thing) drink the cloud kool-aid and think "great, we don't need to think about our infrastructure".

Then there's people who post pictures of property damage "So drunk I puked all over the carpet last night", perhaps with an attached pix of vodka and blue kool aide, is not going to sell well to a guy who just paid for new carpet in his rental.

You are expected to drink the Kool-Aid and tow the party line.

C# Everything else is niche, recommended by people drinking too much Kool-Aid.

We, as hackers, drink way too much Kool-Aid.