cauch

34 ms·

241.
by cauch 2y ago
> Because you advocated that very point. You: "some data is better not to share too" SOME data. SOME. You've concluded, incorrectly, that I was pretending that sharing data is not useful all the time, which is not at all w
242.
by cauch 2y ago
Rolling eyes. > Especially if the author shares neither the data or the code What are you talking about. In this example, why do you invent they are not sharing the data? That's the whole point. > A study that is replicated using
243.
by cauch 2y ago
I will not answer to everything because what's the point. Yes, sharing the code can be one way to find bugs, I've said that already. Yes, sharing the code can help bootstrap another team, I've said that already. What people d
244.
by cauch 2y ago
I'm not sure what you are saying. The peer review process works relatively well in the large majority of the scientific fields. There are problems but they are pretty anecdotal and are far from counterbalancing the advantages. The prev
245.
by cauch 2y ago
Maybe for the audience here, it is useful to consider that peer review is a bit like scrum. It's a good idea, but it does not mean that everyone who say they do scrum does it properly. And when, in some situation, it does not work, it
246.
by cauch 2y ago
I'm sorry that the area you are exercising in is rotten and does not have the minimum scientific standard. But please, do not reach conclusion that are blatantly incorrect in areas you don't know. The problem is not really "a
247.
by cauch 2y ago
That's my point: people here link the replication crisis to "not sharing the code", which is ridiculous. If you just click on a button to run the code written by the other team, you haven't replicated anything. If you re
248.
by cauch 2y ago
> Just that sharing the code is way better And I disagree with that and think that you are overestimating the gain brought by sharing the code and are underestimating the possible problems that sharing the code bring. At CERN, there are
249.
by cauch 2y ago
If it is massaged into desired results, then it will be invalidated by facts quite easily. Inversely, obfuscating things is also easy if you just provide the whole package and just say "see, you click on the button and you get the same
250.
by cauch 2y ago
But they will not make the same mistakes. If you ask two persons to build a software, they can use the same logic and build the same algorithm, but what are the chances they will do exactly the same bugs. Also, your argument seems to be &qu
251.
by cauch 2y ago
That does not change anything to my point: saying "just stop reading a novel whenever you want" is not incompatible with "essays should get to the point". Even if you are right, you still acknowledge that you need a &quo
252.
by cauch 2y ago
Sharing the code may also share the incorrect implementation biases. It's a bit like saying that to help reproduce the experiment, the experimental tools used to reach the conclusion should be shared too. But reproducing the experiment
253.
by cauch 2y ago
I understand for a novel or something. But for an essay, not finishing it is sometimes not finishing the argument and therefore not understanding the point at all. I guess the article's point is that an essay is presenting one idea in
254.
by cauch 2y ago
What is your point? The article says that the letter specifically mentioned examples where Musk failed to act with scientific integrity. It details the situation, which happens to be linked with right-wing stuffs. It obviously does not say
255.
by cauch 2y ago
If it was Musk's intent (but I doubt it was the case, because it does not fit with a lot of other things that Musk did or said that show he is aiming at Faucci role in vaccine discussions), he should have acted to avoid poisoning the d
256.
by cauch 2y ago
> If the RS doesn't expel people for their politics, then it doesn't make sense to expel Musk for, essentially, concerns about his politics. But the article does not talk about Musk's political opinion per se. The concerns
257.
by cauch 2y ago
yeah, that's my point. You are making it even clearer to demonstrate that all is reduced to framing "you are either democrat or republican".
258.
by cauch 2y ago
> which clearly There are plenty of theories of what happened. For example, Harris did target the center and the not-convinced-by-Trump republicans a lot, which is probably what alienated her voter base more than saying something that wa
259.
by cauch 2y ago
The fact that someone like Trump was given as choice is a result of a failure of "the man" from the start. It's just too easy to pretend it is not your fault if your society, the one that you are building with your neighbours
260.
by cauch 2y ago
What a very balanced opinion that will not at all reenforce my idea that some devs are just idiots blaming managers for everything. Managers that micromanage are idiots. If they would have been a dev, they would have been a dev that explain
261.
by cauch 2y ago
I agree with you. But it was not what I was talking about when I was talking about useless direction and trying to solve non-problem. The situation you describe is indeed a management and leadership failure. But if you don't have manag
262.
by cauch 2y ago
Well, humans are humans, and after all, it's very very clear when you scan Hacker News comments that a lot of devs are just having the assumption that managers are useless fakers that bring nothing. It would be very hypocritical to pre
263.
by cauch 2y ago
Not sure of your point. When I read the rest of your comment, it seems like you agree with me: saying you did not progress as a dev is not such a big deal for non-devs (3 in 4), and when it was, it was because the reasons are surprising (ha
264.
by cauch 2y ago
> Unfortunately, the people signing our paychecks do care From your experience of a dev, not a non-dev who manage devs? Noted. My point is that I have observed, with my own eyes, devs BELIEVING they need to do the dance in front of a giv
265.
by cauch 2y ago
Obviously, I don't say "nothing to report" in every meeting. The reality is that sometimes you need to readjust, and sometimes not, and it is impossible to know before hand and confronting your forecast with the observations.
266.
by cauch 2y ago
Cf. my other comments: the developers would go into useless directions and solve non-problems the same way that if you predict tomorrow weather, and then predict after-tomorrow weather, and then predict after-after-tomorrow weather, ... you
267.
by cauch 2y ago
Agreed, but in practice, I think needing to wait for sprint planning is very time-wasting and in practice not efficient. If a dev has worked 3 days in the wrong direction, they will naturally try to salvage some of the bad things, or even t
268.
by cauch 2y ago
In other discussion, people complain about the "flow" and how they should not be interrupted. I guess different people works differently.
269.
by cauch 2y ago
While I agree, it is also very common that it's the culture inside the dev team that leads to this situation. Dev culture tends to idolize unicorns and 10x coders (more than management who has absolutely no reason to care about the sta
270.
by cauch 2y ago
cf. my other comments. The fact that point forecasting deviate from observations the more you go on without readjusting is not a failure of organisation, it's a fundamental and logical law of nature. It's a bit worrying that peopl

More ›