I agree that an exercise14.rst would be nice, but to save time I’ve let the code speak for itself now together with the visualizaion. I’ll probably revisit and better document the exercises later.
At the Explanation link I try to give a general explanation about Pyrhon mutability (and copy later on), I agree some readers might find it hard to relate that to a specific exercise, but I don’t want to write a specific explanation for each exercise.
Ah! Haven’t yet reached stubborn old geezer stage.
Don’t immediately understand exactly what the code does? Must be cuz of mental slippage. Like brain plague or residual PHP or jinja2 knowhow that can’t be purged.
We all know it’s not from drug use or excessive party lifestyle. Maybe excessive retro Linux gaming?
Whatever it is, those exercises are great diagnosis tool.
Here is the link to the code which is being in-browser remote executed
exercise14.py
There is no “explanation” next to or within the file. A
exercise14.rstortest_exercise14.pywould be nice.The Explanation link provided contains a mountain of visual shit (aka noise) none of which looks like
exercise14.pycode.The OP is trying to teach us, i get that. Looks like i’m failing the (mountain of visual shit) reading comprehension section of this exercise.
Thanks for your feedback, much appriciated.
I agree that an
exercise14.rstwould be nice, but to save time I’ve let the code speak for itself now together with the visualizaion. I’ll probably revisit and better document the exercises later.At the Explanation link I try to give a general explanation about Pyrhon mutability (and copy later on), I agree some readers might find it hard to relate that to a specific exercise, but I don’t want to write a specific explanation for each exercise.
First i love the visualizations. It grew on me. And supportive of coding challenges posts. As long as there isn’t a flood of them. Which there isn’t.
I get your position. That there just isn’t an explanation for each and every exercise. The other comments made it seemed like there was.
When i clicked on the Explanation link, the browser didn’t initially scroll to the Mutability section. Went downhill from there.
btw i’m too dumb to know the answer and too lazy to copy+paste the code into a REPR.
All the other commenters are just dishonest pretending they totally got it without running the code ;-)
Actually running the code? I got to the stage where only AI can help me understand anything ;-)
Ah! Haven’t yet reached stubborn old geezer stage.
Don’t immediately understand exactly what the code does? Must be cuz of mental slippage. Like brain plague or residual PHP or jinja2 knowhow that can’t be purged.
We all know it’s not from drug use or excessive party lifestyle. Maybe excessive retro Linux gaming?
Whatever it is, those exercises are great diagnosis tool.
AI reads github issues and crapoverflow for us cuz that is where packages are mainly documented.
The package documentation is a historical document according to every PEP ever. ;-)
What if github issues&discussions disappeared tomorrow? That feeling in your ballsack is what free falling feels like?
Forever wars? np we are due for some excitement.
github disappearing suddenly … that keeps me awake at night
Is Copilot unemployment in it’s future?