barubary

joined 2 years ago
[–] barubary@infosec.exchange 0 points 4 days ago (1 children)

There's a lot of distorted facts here, but the weirdest one to me is "instead of regrouping their efforts (which, I might add, they did, and they got their day in parliament)". The first half just contradicts itself ("instead of doing X, which they did, ..."???) and the second half ("they got their day in parliament") is verifiably, obviously false: The EU petition is still ongoing and collecting signatures. The deadline is July 31.

[–] barubary@infosec.exchange 5 points 1 week ago

@tetris11 @Aedis More like:

isEven() {    case "$1" in        *[02468]) return 0;;        *) return 1;;    esac;}

(If all the line breaks are gone from this code snippet, blame Lemmy. It looks fine here.)

[–] barubary@infosec.exchange 4 points 1 week ago (1 children)

If you were pair programming, your pair could always create a new failing test with the current implementation.

But I'm not pair programming. And you can't always create a new failing test because int is a finite type. There are only about 4 billion cases to handle.

Which might take a while to type up manually, but that's why we have meta-programming: Code that generates code. (In C++ you could even use templates, but you might run into compiler recursion limits.)

More to the point, the risk with TDD is that all development is driven by failing test cases, so a naive approach will end up "overfitting", producing exactly the code required to make a particular set of tests pass and nothing more. "It can't pass all test cases"? It doesn't have to. For TDD, it only needs to pass the tests that have actually been written. You can't test all combinations of all inputs.

(Also, if you changed this function to use modulus, it would handle more cases than before, which is a change in behavior. You're not supposed to do that when refactoring; refactoring should preserve semantics.)

[–] barubary@infosec.exchange 5 points 1 week ago (5 children)

When you say "it can't pass all test cases", what do you imagine the tests look like?

[–] barubary@infosec.exchange 4 points 1 week ago (1 children)

Any ticket system that doesn't even let you copy/paste text snippets in (like, say, a bit of JSON from a log file) without messing up the rendering¹ is terrible.

¹) In two different ways: The rich text editor mangles data one way, but when you submit your comment, Jira mangles it in a different way. You never know what you're going to get.

[–] barubary@infosec.exchange 8 points 2 weeks ago (2 children)

@devilish666 C++ (non-stupid):

#include <stdio.h>
int main() {
puts("Hello, world!");
}

[–] barubary@infosec.exchange 15 points 3 weeks ago

C) It's an obvious joke.

[–] barubary@infosec.exchange 8 points 3 weeks ago (2 children)

s/diplomated/graduate/
s/branche/industry (sector)/

[–] barubary@infosec.exchange 2 points 1 month ago

Isn't that how B worked?

[–] barubary@infosec.exchange 5 points 1 month ago

Similarly, Perl lets you say

my $ret = do {    if (...) {        ...    } else {        ...    }};
[–] barubary@infosec.exchange 1 points 1 month ago (1 children)

To be fair, the C example could be detangled a lot by introducing a typedef:

typedef int Callback_t(int, int);Callback_t *(*fp)(Callback_t *, int);
view more: next ›