I've used pyenv for years and it's an awesome tool. Keeps python binaries separate and it has a virtualenv plugin. I've gotten others to use it as well.
It works great for library owners who need to run tox/nox on multiple versions of python in test suites. Love it.
pyenv also has this with the .python-version file which will switch versions. And with the plugin, you can use virtualenvs in pyenv so that a .python-version can be simply: my-cool-project-virtualenv and switching to that directory automatically switches to it.
Yes but karma makes it worse. It incentivizes getting getting upvotes because you don't want to "ruin" your karma. Expressing controversial opinions, even if they don't generate downvotes, are discouraged with karma. Even OP says he gets a dopamine hit by seeing the karma number go up.
Nice. Can we expand the idea to things that make programming nice, fun, or overall enjoyable?
First post of good code will be a picture of an empty file.
I don't like karma. It incentivizes short, meme-y posts since those are things that get gets a lot of karma.
Probably 100 more chapters of no progress, then a spin off where they are married with a kid but he still won't admit that he likes her because he hasn't beat her in shogi.
Just sit back and enjoy the ride.
Yeah that's a good point. It's telling that inheritance is by design difficult to change unless you follow very specific rules of good OO design patterns.
I guess it's easy to write bad code in any programming paradkgm but inheritance makes it easy to screw up.
Yes! Loot boxes are awful for children (and even adults). Glad to see the Dutch doing something about this, and I hope others follow as well.
Most of us have bad memories of over-complex hierarchies we regret seeing, but this is probably due to the dominance of OOP in recent decades.
This sentence here is why inheritance gets a bad reputation, rightly or wrongly. Inheritance sounds intuitive when you're inheriting Vehicle in your Bicycle class, but it falls apart when dealing with more abstract ideas. Thus, it's not immediately clear when and why you should use inheritance, and it soon becomes a tangled mess.
Thus, OO programs can easily fall into a trap of organizing code into false hierarchies. And those hierarchies may not make sense from developer to developer who is reading the code.
I'm not a fan of OO programming, but I do think it can occasionally be a useful tool.
Ahhh! Such a nice chapter. I liked how she just has shogi on her mind all the time, which is keeping in her character.
Not a big fan of this series but I do like the character design. Thanks for sharing.
"I can read this Perl scrip"t should translate to "I'm lying".