buckets

Compassion doesn't mean you have to throw away buckets and buckets of money.

The licensing page lists three buckets of free, open source licenses for various parts of the project.

We offload a ton of our scripts to S3 buckets on random unrelated domains and it's a pretty common practice.

Honestly, people who write garbage PHP would write garbage rails/python/node too, because the errors fall into a few buckets: 1.

Because you've got to figure out which buckets of money you're going to get paid from.

But there are no reports of New York residents illicitly cracking those buckets open for fun, as claimed in the headline.

But now realized buckets for rounding won't be of equal size and it's wrong.

So, autonomy, replace the CIO, or buckets of cash to compensate for risk.

And yeah, I was thinking of buckets as append-only lists that got dropped in their entirety when out of range.

I wonder if buckets could be represented as lists stored inside a tuple or another list...

I was skeptical of the five buckets initially (given my detailed Mint categorization) but realize that that's really all I need.

Likewise, there are plenty of other objects not designed to kill people that are used for that purpose (stones, rope, buckets of water, etc).

Demographics are an antiquated way of dealing with the "there are too many people to deal with!" problem, so we put them into buckets.

"After" is irrelevant to the discussion, its still separate taxes on separate buckets of income.

I'll have to try improving the list implementation with "buckets"...

From the article: The earliest “hydrants” in New York City (dating back to the early 1700s but lasting until the late 1800s) were simply buckets of water scattered around the five boroughs, left locked by the fire department so as to keep out thieves and vandals.