Ever tried to read something in your dreams? Coding is basically 90% reading and 10% writing. Then you have to insure that shit compiles and runs.
I can’t speak for you, but I don’t think my brain has a valid edition of the Java Development Kit.
Ever tried to read something in your dreams? Coding is basically 90% reading and 10% writing. Then you have to insure that shit compiles and runs.
I can’t speak for you, but I don’t think my brain has a valid edition of the Java Development Kit.
Just think: People having to get help because the job they quit three years ago keeps showing up in their dreams. What’s worse is that they keep doing it, in control but unaware of the fact that they aren’t getting paid, threatened by their in-dream former boss with being fired if the quota wasn’t met.
Staying awake yet unemployed becomes one of their only escapes. They turn to stimulants to stay away from ‘work’ just a bit longer, just a little more peace.
But they then ‘crash’, falling asleep for almost a day, and starting a shift that feels like an eternity, Inception style.
Bombay is best bai.
Which is particularly ironic as the breed is known for its silky black coat, and bai can also mean “yellow mist”.
How broken are we talking here? Like, installation is kinda borked but technically works broken, or purge it with fire and salt the storage medium broken?
I have often busted my machine learning rig as it runs an ancient (but spacious VRAM) GPU. If I upgrade the drivers by accident, it takes an average of 1-2 days to make everything happy again.
I used to be more cavalier with my boot partitions; I am no stranger to a busy box for repairs. Best moments are when I used to try and adjust a live partition to make more room for the swap partition (or vice versa).
I have screwed up more Raspberry PI installations than I care to count. Usually by my own hand.
I have completely broken Xwindows multiple times due to drivers, trying to go between desktop environments, and most frequently trying to get video cards to work that aren’t natively supported.
Friend, while I appreciate the time and effort on the docs, it has a rather tiny section on one of the truly worst aspects of pip (and the only one that really guts usability): package conflicts.
Due to the nature of Python as an interpreted language, there is little that you can check in advance via automation around “can package A and package B coexist peacefully with the lowest common denominator of package X”? Will it work? Will it fail? Run your tool/code and hope for the best!
Pip is a nightmare with larger, spawling package solutions (i.e. a lot of the ML work out there). But even with the freshest of venv creations, things still go remarkably wrong rather quick in my experience. My favorite is when someone, somewhere in the dependency tree forgets to lock their version, which ends up blossoming into a ticking time bomb before it abruptly stops working.
Hopefully, your experiences have been far more pleasant than mine.
Hahaha!..
Oh shit, you’re serious.
Yeah, it was kinda the stuff of nightmares. I think it actually… fused … some things together.
Python should not be used for production environments, or anything facing the user directly. You are only inviting pain and suffering.
Well, let’s at least keep tabs on it.
Rarely, TBH. Unless you’re OK with being an absolute ass in some form or another.