cjfd

50 ms·

601.
by cjfd 7y ago
We might also consider that if x is larger than a few weeks y might well be negative.....
602.
by cjfd 7y ago
I don't really believe this although it seems rather hard to prove which side of this debate is right. Presumably it also depends on circumstances. I think any sort of messy or bad code immediately slows down developers. The truism tha
603.
by cjfd 7y ago
While very occasionally useful I think technical debt issues mostly should not exist. Improving code quality should be considered part of any issue that a person takes up. Any code that relates to the issue should also be viewed as a potent
604.
by cjfd 7y ago
The high level point that is of great importance is that if one wants a computer program to function in a reliable way one needs simple and understandable algorithms/components. Nowadays even the processor is no longer simple and assem
605.
by cjfd 7y ago
O dear.... Am I happy that I never studied computer 'science'..... On the other hand, there must be smart computer science students and/or smart places of education where actual learning about processor caches and the like ta
606.
by cjfd 7y ago
Okay, that does sound like a workable solution.
607.
by cjfd 7y ago
The haskell situation sounds like generally a good thing but I am not sure I would like it very much if this also applies to logging.... It does not sound like great fun to have to change the signature of a function when it needs to log som
608.
by cjfd 7y ago
The so-called best practices are wrong sometimes. Or maybe they just talk about generic cases. In which case they often are wrong as well. Having the same code twice can already be highly problematic if it is a longer stretch of code. It is
609.
by cjfd 7y ago
In logic non-existing objects have all properties, including contradictory ones. This follows from the fact that in propositional calculus from a contradiction (or from False) everything can be concluded. I.e., P /\ ~ P -> Q. One co
610.
by cjfd 7y ago
I suppose that is quite possible. I still like the idea though. Like, if they are going to engage in scoundrelism it needs to be as blatant as possible. Now we are stealing from the sick. That kind of thing.
611.
by cjfd 7y ago
Actually, there is a market solution to this problem. I cannot claim to have thought this up, it was discussed in an episode of econtalk. Don't remember the person that was interviewed. The idea is that big pharma companies have to pub
612.
by cjfd 7y ago
Whether or not the tech companies have too much power does not sound like the most relevant question here. The lack of power of citizens of communicate privately is the more worrisome thing. And maybe some random person is right to say that
613.
by cjfd 7y ago
It all depends on the situation. The simplest possible situation of mostly just having a master branch also can work quite well. When you have specialized testers that test a candidate release you start to need release branches. Feature bra
614.
by cjfd 7y ago
The operator precedence rules that are discussed here are a bit tricky and programmers could be excused to have to think a few secs before knowing how it was again. Therefore, it is better to use parentheses for these tricky cases. On the o
615.
by cjfd 7y ago
By fixing everything that goes wrong noticeably and by having no idea that many features are currently actually not working as they are supposed to? To actually create reliable software currently the best bet is to have automated tests for
616.
by cjfd 7y ago
The thing I would worry about here is that perhaps not all of your tasks have the same performance demands. There may be tasks related to RPC that should run as quickly as possible and tasks related to computation that could take a long tim
617.
by cjfd 7y ago
This is completely the wrong attitude. Code should be correct, not fail-safe. All of the safety hatches that people tend to introduce make the code less predictable and eventual problems tend to arise far away from where they originated, ma
618.
by cjfd 7y ago
I am sorry but what you are saying really does not make much sense to me. You say quality gates are bad and instead we should have unit tests, acceptance tests and so on. Actually, unit tests and acceptance tests are examples of quality gat
619.
by cjfd 7y ago
Your tests? You should despise tests if you want to be consistent with the attitude described in your first post. In the mean time I will just keep using my strongly typed language and, of course, also automated tests. Thank you very much.
620.
by cjfd 7y ago
I can't say I spelled every letter in the article but it says so many strange and wrong things I would not give it any benefit of the doubt of the sort of 'but it cannot really actually say that, right?'
621.
by cjfd 7y ago
Ah, now I understand what you are trying to say. Yes, the 'it' in my post is indeed referring to software engineering. It is not so much that they are doing software engineering wrong due to changing requirements as that the chang
622.
by cjfd 7y ago
One can talk about MTBF and MTTR but not all failures are created equal so maybe not all attempts to do statistics about them make sense. The main class of failures that I am worrying about regarding the MTTR is the very same observable pro
623.
by cjfd 7y ago
I think I disagree with this about 100%. Sure, production is what it is all about in the end. But how do you know the letters you just typed are going to be any good in production? They might just crash and burn there. That is why we need a
624.
by cjfd 7y ago
One area where this becomes apparent is that in complex and layered system at least some of the bahaviours of a single layer do not make sense in terms of the system as a whole. Often it is wrong to attempt to let a layer on its own do the
625.
by cjfd 7y ago
No, it is just that your post sounded to me like you were saying that it is a problem that the requirements are not coming from the software engineers. My post attempts to say that this is not a problem and that it actually is how it should
626.
by cjfd 7y ago
No, they do not come from the software engineers. It is like being a DJ who is taking requests. You are not playing music for yourself but for other people. It the DJs task to make them sound good. On the other hand, one sometimes also need
627.
by cjfd 7y ago
Yes, that is very true. If changing and complex requirements are a problem, you are doing it wrong. This is the main reason why code quality must be as high as possible. It is the best chance there is to be able to accommodate new and chang
628.
by cjfd 7y ago
Ow, but looking at the docs they still do not seem to support delete yet.
629.
by cjfd 7y ago
Ah, that is interesting. My experiences were before 2018 and I had not kept an eye on it, so I did not know this.
630.
by cjfd 7y ago
Sure, it is simple and that is why people use it. But I have also run into hard problems using it. Deleting and renaming columns is not supported natively. On the internet one can find procedures to do that but they generally do not take fo

More ›