toolbox

OOP is simply a tool to put in your toolbox, if it suits you, then use it.

Start with your simple Z Score, this is such an important tool in your data science toolbox.

Trying to write these schemas by hand IS hell, but putting blind trust in your toolbox is possibly even worse.

If one look into a physical toolbox, many of the tools have not changed for generations.

Hot code loading is not absolutely critical, but it's another useful tool in Erlang's high-availability toolbox.

Both are designed with a focus on performance and robustness, while incorporating the large toolbox of features demanded by content creators.

That's not even counting any 0 day's that are (probably) sitting in someone's toolbox.

Anyone reading posts of high-security engineers pushing strong hardware and software security pre-Snowden would've survived almost everything in NSA's toolbox using such methods.

Android offers a surprisingly good toolbox for diagnosing and abusing wireless networks.

I wonder if that makes unix-likes so resilient is that at its core it is not a tool, but a toolbox.

Have we begun shuffling around the gadgets in our toolbox to distract ourselves from the difficult problems we need to solve?

It is a toolbox of methods which generally do work.

If you're in the business of education, your "toolbox" is essentially whatever people need to learn.

It is high time to develop communication-efficient algorithms for the basic "toolbox".

NLP is about stealing what works to extend its "toolbox".

What sounds most interesting to me is that it seems to be kinda "dialect-oriented" -- meaning that to use it idiomatically, you should get used to writing tiny parsers (with provided toolbox) for small ad-hoc DSLs.