This is a more wonky thread about how I made this visualization in #Rstats using the awesome visNetwork

On Bayesianism, the Many Worlds Interpretation, and personal identity.

Some thoughts worked out in a letter to a friend, which is the kind of thing you do when off Twitter for a glorious week. (🧵)

“Chance is ignorance”—the Bayesian story; all probabilities represent states of mind, not states of the world. One *could* put (some) chances “in the world”, but let’s take Occam’s Razor seriously...

That the probability of a fair coin coming up heads is 50% simply means that marginalizing (tracing, as the physicists say) over the hidden facts leaves you, nearly, maximally ignorant of the outcome.

Quantum uncertainty (access below!) poses an apparent challenge to this story. There seems to be nothing to be ignorant about when it comes to (say) electron spin—there is nothing “inside” the

The electron is a simple object, in other words. So where does the uncertainty come from? One could follow David Wallace’s wonderful interpretation in terms of chaotic dynamics and decoherence, but let’s see if we can take another route...

This post is pretty bizarre, but it manages to hit on so many false beliefs that I've seen hurt junior data scientists that it deserves some explicit

(1) The notion that R is well-suited to "building web applications" seems totally out of left field. I don't feel like most R loyalists think this is a good idea, but it's worth calling out that no normal company will be glad you wrote your entire web app in R.

(2) It is true that Python had some issues historically with the 2-to-3 transition, but it's not such a big deal these days. On the flip side, I have found interesting R code that doesn't run in modern R interpreters because of changes in core operations (e.g. assignment syntax).

(3) "Most of the time we only need a latest, working interpreter with the latest packages to run the code" -- this is where things get real and reveal some things that hurt data scientists. If this sentence is true, it's likely because you don't share code with coworkers.

(3) Really is a broader issue in data science: people only think of what they need to do their work if no one else existed and code was never maintained. Junior data scientists almost always operate on projects they start from scratch and don't have to maintain for long.

An amazing new project from @bearpelican was just released: https://t.co/DBov6sZTVS . A beautiful design; you can auto-generate a melody from chords, chords from a melody, and more.

It's technically brilliant, combining BERT, seq2seq, and Transformer XL
https://t.co/jF3mO5aXiu

It's also a wonderful example of leveraging and customizing the fastai framework in a deep & thoughtful way.

Here's the full set of blog posts diving in to this

Pandas is an amazing data analysis and manipulation library for python, Really popular when working with ML, Data science or more.

It has a robust data structure, Dataframe for manipulation and analyzing data.

Here's some tips to help you work better with pandas. Let's go! ↓

If you're not aware about what a Dataframe is, It's an optimized data structure for loading data, analysing it, manipulating data in it, and Mostly gathering insights.

It uses Cython backend which transpiles into C for optimized code.

Here's how a dataframe looks like,

Before we start, You need to ensure, you have pandas installed. If you don't, Do that before moving ahead!

Here are the tips, Let's go!

1/ Convert PD series to Dataframe

We all have struggled, when we deal with pandas series. It's always easier to work with Dataframes, rather than series. Here is how you can convert series to dataframe easily.

2/ How to create dummy Dataframe for testing

We always need dataframes for testing and analysing normally, if we do not have data ready. Here is how you can use Pandas API to generate different types of data.