rekahrv

That's an interesting example. Also, the same pattern has happened to other terms as well: 1. At first, a quite specific meaning. 2. As time goes on, the same term gets used for more & more things.

Great book. The interview with Peter Attia on Star Talk was also interesting (and some parts hilarious): https://startalkmedia.com/show/medicine-3-0-extending-human-...

Yeah, anything that contradict s PEP-8 conventions looks unnatural in Python. :-)

Yes, that's a great point. Some names are generally unclear, but more often, they are unclear in a context. Do you have some "contextual" examples?

I agree with those points, both on the positive and negative side. Do you have some examples of vague or misleading names?

Yes, exactly. Thanks for the clarifying question. :-)

Any kind of artifact in code: modules, functions, classes, arguments, variables...

“Every six months or so, someone would ask in our meetings, ‘Should we think about general purpose code generation,’ but the answer was always ‘No, it’s too difficult, the current models just can’t do it,’”

Lol

TLDR:

* Falsy values (empty string, empty list) should have the same behavior as None. * Don't use `==` for comparison with None or NaN

Thanks a lot, that's very insightful.

Comparing the launch of Effective XGBoost to Effective Pandas: What do you think: What are the reasons XGBoost had so much more sales in the first days?

* bigger audience? * better topic? * anything else?

PDEP-8 suggesting various changes regarding the `inplace` and `copy` arguments: https://github.com/pandas-dev/pandas/pull/51466