For a serious reoly, I think the expression “If they have eggs, buy two” is redundant. If they didn’t have eggs, the kid just can’t and won’t buy any eggs.
I think the proper command would be, “Please buy 1 bottle of milk and two eggs.” That way, the kid won’t be confused and it’s still a proper valid command.
Unfortunately though, the sentence is ambiguous even to non-programmers. It is unknown whether the if condition applies to
buying two eggs (buy two eggs)
buying two bottles of milk (buy two bottles instead)
I’ve actually had an excavator take out my network. I’ve also had networks taken out by forklift, train, and a semi-truck towing three other semi-trucks.
Download ML thing.
make new venv. pip install -r requirements.txt.
pip can’t find the right versions. pip install --update pip.
pip still can’t find the right versions.
install conda.
conda breaks for some reason.
fix conda.
install with conda.
pytorch won’t compile with CUDA support.
install 2,000,000GB of nvidia crap from conda.
pytorch still won’t compile.
install older version of gcc with conda.
pytorch still won’t compile.
reinstall the entire operating system with debian 11.
apt can’t find shitlib-1.
install shitlib-2.
it’s not compatible with shitlib-1.
compile it from source.
automake breaks.
install debian 10.
It actually works.
“Join our discord to get the model”.
give up.
I thought you could put curly brackets on a new line in js? Although I know when returning an object it has to be on the same line… fuck JavaScript man
You don’t suddenly find out that your peeler is several versions behind
And then proceed to spend 17 hours trying to get it to peel just the way the invetors wanted it to, which is different from the other 987654321 peelers around.
After 20 years in the field, I hate love despise like 'm ok with technology
Here’s my take. In order to be able to write meaningful unit tests the code should be structured in a certain way, with very modular, decoupled units, dependency injection, favoring composition and polymorphism over inheritance and so on.
If you manage to write your code this way it will be an objective advantage that will benefit the project even if you don’t write a single unit test. But it does make unit tests much easier to write, so presumably you’ll end up with more tests than otherwise.
IMO teams should prioritize this way of writing code over high test coverage of non-modular code. Unit tests for deeply-coupled code are a nightmare to write and maintain and are usually mostly meaningless too.
programmer_humor
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.