This works because of the relative path to the pyenv.cfg file.
319 karma · joined November 28, 2012
This works because of the relative path to the pyenv.cfg file.
The conversation around snaps starts at 5:20.
It sounded to me that they genuinely tried to put themselves in both side's shoes.
Did you have a particular language/runtime in mind?
If I could only give one advice to someone about improving their learning skills, it would be to learn about spaced repetition
When you say: "...methods used by a method under test can only be assumed to work if each of those methods has good tests", my opinion is that if that is an issue, than those private methods belong in another class that is a dependency of the class you are testing, and should be tested in the context of that other class.
Meaning that either there's another unaccounted variable(s) that controls the effect of A in B and C, meaning that we cannot conclude anything from the experiment.
Yes and no is not acceptable...
Reproducibility is one of the main principles of the scientific method (those papers shouldn't even been accepted if they don't contain enough information about how to reproduce the experiments they describe)
If an experiment is so complex that it can be compared to redoing someone else's thesis it can be either that the thesis is very simple or the experiment is so complex that it probably proves nothing.
This has the consequence of making the methods smaller since they are narrow in scope.
It's easier to understand a well named method with a few lines of code (and believe me, it's easier to properly name it than a method with a lot of code, since the former is focused in one task and it is easy to come up with a name that describes that task; and the latter, where the method does so many things that there's no way you can name it properly [have you ever found methods with names like DoWork and then 100 lines, I'd say that is a code-smell].