Read other people’s code… particularly code by experienced developers. One good way to do that is to single-step debugging through the test code in a well-known package, stepping into the code being tested.

I suppose if you don’t know how test frameworks like pytest work, tackling how they work and how to do single-stepping with some toy example code will be a prerequisite for the above, as will spending some time studying how packages are made. (The latter may seem unattractively tedious, but the knowledge will pay off even if you never become an expert at making your own packages.)

These exercises are very likely to expose weaknesses in your understanding of all sorts of things. Be patient and keep studying!

bit of a cutthroat way to characterize what you “like”. Might actually make the interviewer downvote you for threatening their position.

have not. But I like salt on my grapefruit, so maybe I will try it.

Functions don’t return… equals goto. Everything must be done by side effects… all variables are global. Global state mutation is inheritance… no grok. Every call is non-blocking and spawns a new thread… atomic bomb for junior software engineers.

??? … shorting the stock of the company that adopts this.

Profit!

There are two wrong sides here… so it can be difficult to predict what anyone will lean further away from. Beware of assuming that means they are leaning toward the other side though.