• 0 Posts
  • 30 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle




  • It requires continuous expansive improvements. It is like real world. Building a system robust to frauds works on the short term, but on the mid and long term is impossibile. That is why laws change, evolve, we have governments and so on. Because system reacts to your rules and algorithms, making them less effective.

    And these continous expensive improvements are done daily, but it is a difficult job


  • It is not at the moment. Models are built on the assumption of stability, i.e. that what they are modelling doesn’t change over time, doesn’t evolve. This is clearly untrue, and cheating is a way the environment evolves. Only way to consider that, is to create a on-line continous learning algorithm. Currently this exists and is called reinforcement learning. Main issue is that methods to account for an evolving environment are still under active research. In the sense that methods to address this issue are not yet available.

    It is an extremely difficult task tbf






  • People isn’t considering that documentation has greatly improved over time, languages and frameworks have become more abstract, user-friendly, modern code is mostly self explanatory, good documentation has become the priority of all open source projects, well documented open source languages and frameworks have become the norm.

    Less people asking programming related questions can be explained by programming being an easier and less problematic experience nowadays, that is true.








  • I read it, and I read the messages from the devs. The communication issue I am trying to point is also highlighted in the comments: if the decision on merging a PR is uniquely dictated by financial benefits of IBM, ignoring the broader benefits of the community, the message is that red hat is looking for free labor and it is not really interested in anything else. Which is absolutely the case, as we all know, but writing it down after the recent events is another PR issue, as red hat justified controversial decisions on the lack of contributions from downstream.

    The Italian dev tried to put it down as “we have to follow our service management processes that are messy, tedious and expensive” but he didn’t address the problems in the original message. The contributor himself felt like they asked his contribution just to reject it because of purely financial reasons without any additional details. It is a new PR incident