But Python is strongly typed. If you say x=2, type(x) will say “int”.
It does suffer from an excessive overloading of operators (“a” times 6 shouldn’t work). But that’s neither here nor there.
If Python wasn’t strongly typed, it wouldn’t be conceptually possible to move it towards explicit typing as the current push is.
Now, it’s not statically typed. You don’t get to assign values and interpretations to memory addresses. This is what “performant” people usually defend. But _that_ has nothing to do with typing assuming semantic roles in codebases.
This is the case in my marriage, but not in my parents’. They are musicians, artists, perform together and/or take active stakes in each other’s careers. They weren’t sexual as I was growing up (I’m not giving intimate details here) but they had this whole other source of cohesion. A much greater one indeed — I have fond sexual memories but my parents have dozens of live albums at cool venues.
Then, maybe all of this anomie is a disease of affluence. The other thing that united my parents was that, well, they had to fight for survival and for the means if giving us kids a decent childhood experience. Maybe that alone works like continuous shared trauma, us-two-against-the-world.
I use Python to generate DPLL and likewise with MiniZinc. It’s no different from SQL: there’s something of an impedance mismatch that’s already felt in eg Sympy.
We pretty much did binary search to find my lithium levels. The lethal concentration of lithium is very close to the therapeutic range, but we couldn’t afford to spend long on low doses (since you have to take blood tests to assess effective dosages.)
My dad used to take warfarin too and keep a very steady diet of dark leafy greens (his poison of choice he wouldn’t give up). There are meds now that are less dependent on food, your grandviejo may want to ask about.
I have pretty sharp productivity/energy/focus fluctuations and often achieve more by waiting for the “inspiration” (so to speak) to come and do tasks quickly than by slogging through low times. But they’re pretty sharp: sometimes something might take me two hours at low tide and ten minutes at high tide.
Then there’s the issue of what to do at low tide.
I’ve tried countless times to adhere to Pomodoro or Jocko Willink-type mindsets that willpower is fickle while discipline equals freedom. But the results don’t seem to be there.
OTOH the other day I heard someone in the Netflix doc about Alberto Nisman’s murder that described a terrorist network as a “matrix”.
I grumped as card-carrying pedants are duty-bound to, but then realized that if there’s a 1:1 correspondence between graphs and (adjacency, incidence) matrices, then there’s very little loss of meaning in referring to graphs as “matrices”. Maybe in some communication contexts it’s even clearer.
The examples I have seen tease but are not fully clear on how far GPT-3 can go on tasks that are not in principle text generation tasks.
For example I’ve seen the translation to HTML code demo. Of course, LSTMs already generate quasi compilable code. But the promise seems far better here. Countless “AI” tasks can be conceptualized as entering prompts and receiving code — playing chess, finding logical implications (maybe from tabular data like in Formal Concept Analysis), detecting outliers in columnar/matrix data. How much does GPT do? How much turf beyond chatbots and automatic journalism does it cover?
I’m using lattice (line) diagrams to understand intersection concepts like this. They’re easy to generate from cross tables using FCA tools such as the “concepts”
Python available in pip.
It’s somewhat surreal to point this out (being so jaded to the made-up “dog whistles” of recent American culture) but the uppercase sigma is a historic fascist symbol in Brazil.
It does suffer from an excessive overloading of operators (“a” times 6 shouldn’t work). But that’s neither here nor there.
If Python wasn’t strongly typed, it wouldn’t be conceptually possible to move it towards explicit typing as the current push is.
Now, it’s not statically typed. You don’t get to assign values and interpretations to memory addresses. This is what “performant” people usually defend. But _that_ has nothing to do with typing assuming semantic roles in codebases.