I don’t think so. The vast majority of people in DS I have come across take uncertainty and its reporting seriously.

It was the boss that wasn’t fluent in uncertainty. And this I have seen a few times. Statisticians / data scientists climbing the corporate ladder high into management seems rare?

Have a look at the source of R CMD check and feel better about how you’re managing complexity.

Once again appreciating the sober takes gang. 🙏

@pivot-to-ai.com.web.brid.gy there’s a daily here for you.

I started watching this with a pit in my stomach due to how hard it is to utter a single statement about anything in this space that isn’t loaded with caveats.

But that was gone by the end! Love the ecosystem map idea. Nice one.

But if you do try to do more, be careful you don’t make the package more annoying to test / work with. That’s not in your user’s interest either!

Increment a major version number (per semver), and mention the breaking change in your NEWS.

If you have reverse dependencies you’ll have to let them know and give them some time to update.

Anything beyond that is a kindness.

It’s a bad look. It wipes anything user had sitting in the env from the rprofile for one. Suggests total dependence on interactively running scripts manually, which in turn suggests lack of training in reproducible data sci / eng practices.

Very good!

But if you were moving into a new home and had to assemble a bunch of flatpack furniture back to back you’d be wishing for the screwdriver after the first or second one.

Now imagine you have to assemble flatpacks 5 days a week for the rest of your career.

It’s electric drill time!

I think that’s pretty good. One thing I would add is that the value of specialisation becomes more obvious at scale.

Like if you have a choice of one tool for your home you choose swiss army knife as it will do a passable job at all the odd jobs...

Cc @thewaroncars.bsky.social Randall enters the chat

I don’t even know if there’s really a contest for greatest DS lang…

“The second best language for any task” - this is how Python market Python. They know it’s mashed potatoes.

And look at this function. A deprecated argument. A vestige of refactorings past. Unmistakably human authored.

Also inhale deeply through your nose. It’s got a faint odour to it no?

There are similarities to the untrained eye. But trust me your users WILL know the difference.

Make n high enough and you’ll get the famed ‘stack overflow’. I think its about 10000. That’s why you don’t see it in the wild.

However there is s technique to avoid the overflow, see Tailcall().

So what are we doing custom build, layouts, bindings? All of the above?

You will use these like twice a year and twice a year you will feel like a data wrangling jedi.