So why were there no tests against the full dataset? Because that made the CI runs take too long.
As a software tester, I've done a few back of the envelope calculations, filed a bug report if the maximum value is too long, and forced the programmers to prove me wrong. Most of the time they go back and refactor the code. Sometimes they wait until the bug bites them in the ass just before code release.
Your web site codebase is not written in python3, if you're using Pelican - it's written in fucking Markdown.
Some of the website content is written in Markdown. The rest are in Python data structures that are manipulated by other Python scripts and Jinja2 in the templates..
Great, you can spend the next 20 years maintaining your stupid codebase and never advancing or learning anything new.
Let's plot the evolution of my oldest website: Basic HTML (1997-2002) -> LAMP (2002-2007) -> Joomla! (2008-2011) ->
Wordpress (20011-2016) -> Pelican (2016-Present).
And installing python2, making a virtualenv, installing pelican & beginning to publish using the native fabric functionality shouldn't take somebody competent and familiar with python more than the time it requires for their computer to process the commands.
I'm using Python 3 exclusively on my systems. You should get with the program and make the transition.
You really must grow out of help desk and learn some useful stuff...imbecile fucker. And stop pretending you understand something about computers or even know how to read English errors. You are a fucking waste of space on this planet.
A CS could prove that your well-tested program is actually broken.
When I first got a job as a video game tester, my supervisor gave me a notepad and let me play the video game that they released the year before. I found every bug that the game shipped with. Over the next six years, I would write 30,000+ bug reports and be responsible for ten titles as lead tester. I'm well familiar with well-tested code being broken because management overruled me at the code release meetings.
And a CS could show you that your well-tested program's performance won't scale in production.
A problem domain that doesn't keep me up at night because I'm just a coder and not a professional programmer.
I can think through a coding problem well enough, as well as or better than most programmers I know.
According to https://readable.io/ your sentence has too many adverbs ("well" flagged twice). It also reads like an English major writing out of his ass.
Funny how the guy claiming he's really great at thinking through things can't catch obvious errors in his own writing.
Perfect grammar isn't a requirement for thinking through problems. My obvious error is the usage of "than" (comparison) rather "then" (time). A common mistake that I make because it's related to my learning disability of being unable to distinguish similar sounding words (i.e., than/then, glass/grass or ear/year) due to a hearing loss in one ear. Than/then was a particular challenge until a college instructor explained the differences.
Spending double on a new computer will not cause your program to finish in half the time if it's waiting on a poorly constructed network request.
Those days are long over. I switched out my quad-core processor for an eight-core processor. Performance overall didn't improved that much because most of my applications are single core.
IT guy! My mail is crashing! It says assertion failed! Fix it with your coding skills! Quickly! IT guy stop surfing donkey porn and fix the code now! I need my mail!
Sorry. I work in InfoSec, not Help Desk. Call 1-800-IBM-HELP.
A different programmer looks at it a year later, determines that it looks too complicated, and refactors the code to be more simpler "in a far more elegant, better scaling and maintainable solution."
Seems like you're complaining about script kiddies and not coders. I'm a coder because I got my programming degree from a community college and I don't work professionally as a programmer (I work in IT support), but I can think through a coding problem well enough than most programmers I know.
You're not renting the cartridge; it belongs to you.
Perhaps you didn't see the quote marks around the word "rent" in my comment?
You may or may not get a credit towards the purchase of a new cartridge if you return your old one for recycling, but there is no penalty for simply keeping it.
The penalty for keeping an empty cartridge is wasted space. I once cleared out a storage closet filled with 300 empty printer cartridges. Fortunately, every cartridge was inside a replacement cartridge box. Spent a day taping up boxes and slapping on shipping labels.
You certainly can if the car could have avoided him by being written a little better.
If the accident is avoidable. Some accidents are not. I read an article last year that self-driving cars won't be safe until all the human drivers are off the road.
Depends on how well the unit test is written. I spend three times more time writing the unit test than the actual code. Mostly because I test for what the results should be and every possible edge case that I think could happen. Once I'm satisfied with the unit test, I'll tweak the code for speed.
The opposite extreme is where everyone linked their project to a left-pad package and the developer pulls the package in a hissy fit, breaking the Internet at the same time. A left-pad function is something that every programmer should be able to pull out of their ass.
when you are maimed in your self-driving car because its computer was too slow to pick the crazy driver out of the crowd
You can't blame the self-driving car for an accident if the crazy driver drives out of a crowd into traffic. Cars in other lanes are predictable events. Cars driving on the sidewalk and running over pedestrians are not predictable events.
Slashdot Mirror
So why were there no tests against the full dataset? Because that made the CI runs take too long.
As a software tester, I've done a few back of the envelope calculations, filed a bug report if the maximum value is too long, and forced the programmers to prove me wrong. Most of the time they go back and refactor the code. Sometimes they wait until the bug bites them in the ass just before code release.
Do you think they had more than that as a plan when they went to the moon?
I'm still a fan of the Apollo Venus flyby mission.
https://falsesteps.wordpress.com/2012/07/21/manned-venus-flyby/
my GOD you are so smart!
Uh, no. Let's quote Blazing Saddles instead: "Ooh, baby, you are so talented! And they are so dumb!"
Your web site codebase is not written in python3, if you're using Pelican - it's written in fucking Markdown.
Some of the website content is written in Markdown. The rest are in Python data structures that are manipulated by other Python scripts and Jinja2 in the templates..
Great, you can spend the next 20 years maintaining your stupid codebase and never advancing or learning anything new.
Let's plot the evolution of my oldest website: Basic HTML (1997-2002) -> LAMP (2002-2007) -> Joomla! (2008-2011) -> Wordpress (20011-2016) -> Pelican (2016-Present).
And installing python2, making a virtualenv, installing pelican & beginning to publish using the native fabric functionality shouldn't take somebody competent and familiar with python more than the time it requires for their computer to process the commands.
I'm using Python 3 exclusively on my systems. You should get with the program and make the transition.
https://wiki.python.org/moin/Python2orPython3
California is leading the resistance! Woo-hoo!
You really must grow out of help desk and learn some useful stuff...imbecile fucker. And stop pretending you understand something about computers or even know how to read English errors. You are a fucking waste of space on this planet.
That's kind of harsh to say to an AC. :P
A CS could prove that your well-tested program is actually broken.
When I first got a job as a video game tester, my supervisor gave me a notepad and let me play the video game that they released the year before. I found every bug that the game shipped with. Over the next six years, I would write 30,000+ bug reports and be responsible for ten titles as lead tester. I'm well familiar with well-tested code being broken because management overruled me at the code release meetings.
And a CS could show you that your well-tested program's performance won't scale in production.
A problem domain that doesn't keep me up at night because I'm just a coder and not a professional programmer.
You accidentally a few words.
According to https://grammar.com/ my usage of "than" was called into question.
I can think through a coding problem well enough, as well as or better than most programmers I know.
According to https://readable.io/ your sentence has too many adverbs ("well" flagged twice). It also reads like an English major writing out of his ass.
Don't play Nintendo in front of your aquariums. You're giving fishes the wrong impression about humanity.
Funny how the guy claiming he's really great at thinking through things can't catch obvious errors in his own writing.
Perfect grammar isn't a requirement for thinking through problems. My obvious error is the usage of "than" (comparison) rather "then" (time). A common mistake that I make because it's related to my learning disability of being unable to distinguish similar sounding words (i.e., than/then, glass/grass or ear/year) due to a hearing loss in one ear. Than/then was a particular challenge until a college instructor explained the differences.
You're not a programmer, right?
Not professionally. I work in IT Support.
Spending double on a new computer will not cause your program to finish in half the time if it's waiting on a poorly constructed network request.
Those days are long over. I switched out my quad-core processor for an eight-core processor. Performance overall didn't improved that much because most of my applications are single core.
IT guy! My mail is crashing! It says assertion failed! Fix it with your coding skills! Quickly! IT guy stop surfing donkey porn and fix the code now! I need my mail!
Sorry. I work in InfoSec, not Help Desk. Call 1-800-IBM-HELP.
[...] looks a little more complicated [...]
A different programmer looks at it a year later, determines that it looks too complicated, and refactors the code to be more simpler "in a far more elegant, better scaling and maintainable solution."
Seems like you're complaining about script kiddies and not coders. I'm a coder because I got my programming degree from a community college and I don't work professionally as a programmer (I work in IT support), but I can think through a coding problem well enough than most programmers I know.
How can I keep up with replies to my Slashdot comments if I can't quickly closed out the tabs I've already looked at?
You're not renting the cartridge; it belongs to you.
Perhaps you didn't see the quote marks around the word "rent" in my comment?
You may or may not get a credit towards the purchase of a new cartridge if you return your old one for recycling, but there is no penalty for simply keeping it.
The penalty for keeping an empty cartridge is wasted space. I once cleared out a storage closet filled with 300 empty printer cartridges. Fortunately, every cartridge was inside a replacement cartridge box. Spent a day taping up boxes and slapping on shipping labels.
So it's highly dependent on what you think could happen, and what satisfies your sense of sufficiency.
It's called programming. The [computer | self-driving car | AI | programmable girlfriend] is no better than the person who wrote the software.
Despite all that's been invested in development methodology, this is remains a black art.
That's why I always laugh when a computer science graduate gets on his high horse. Those of us in the trenches know better.
You certainly can if the car could have avoided him by being written a little better.
If the accident is avoidable. Some accidents are not. I read an article last year that self-driving cars won't be safe until all the human drivers are off the road.
why not? normal drivers are found at fault ALL THE TIME for NOT avoiding hazards
Some accidents are unavoidable accidents that can't be prevented.
Depends on how well the unit test is written. I spend three times more time writing the unit test than the actual code. Mostly because I test for what the results should be and every possible edge case that I think could happen. Once I'm satisfied with the unit test, I'll tweak the code for speed.
The opposite extreme is where everyone linked their project to a left-pad package and the developer pulls the package in a hissy fit, breaking the Internet at the same time. A left-pad function is something that every programmer should be able to pull out of their ass.
http://www.haneycodes.net/npm-left-pad-have-we-forgotten-how-to-program/
You will, because you are the only truly elite being in existence, and your lemonade skills prove it.
My preference for Python 3 over Python 2, Ant over Make, reinventing the wheel and shooting people disqualifies me from being elitist. :P
when you are maimed in your self-driving car because its computer was too slow to pick the crazy driver out of the crowd
You can't blame the self-driving car for an accident if the crazy driver drives out of a crowd into traffic. Cars in other lanes are predictable events. Cars driving on the sidewalk and running over pedestrians are not predictable events.
The only difference between what you describe and what these "simulation" theorists are is who their god is.
Their God is an angry white dude from the Old Testament. My God is a beautiful black woman from the New Testament. ;).
If performance sucks, buy a faster computer. Speed covers a multitude of sins.