20 Matching Annotations
  1. Nov 2021
    1. he leaders of Myanmar don’t really have any ideology beyond nationalism, self-enrichment, and the desire to remain in power.

      This could very well read "the leaders of the United States" and still be true!

    2. They vigorously promoted the superiority of their political system and they objected when it was criticized.

      This cuts both ways. Neoliberals do the exact same thing.

  2. Oct 2021
  3. Sep 2020
    1. So don’t throw object-oriented programming out of your toolbox in the next few years. But make sure that it’s not the only tool you have.

      This makes total sense in any context. I make things out of wood and I recently learned not to use the same saw for all types of cuts. I guess I could have applied some of my software engineering skills to this particular problem!

    2. The most likely scenario is that object-oriented programming will stay around for another decade or so.

      Beware of the predictions you make!

    3. Paradigms are a bit like religions. They’re good in moderation — arguably, Jesus, Mohamed and Buddha said some pretty cool stuff. But if you follow them to the last little detail, you might end up making the lives of yourself and of people around you quite miserable.

      Preach!

    4. There’s just one problem. The whole point of encapsulation is to keep pieces of data safe from one another and thus make computing more efficient. This doesn’t work without strict hierarchies.

      The author forgot about aggregation and composition.

    5. Well, you can’t do it. At least not in an elegant way. Consider for example the class Copier. (I borrowed this example, as well as some info about the problems presented here, from Charles Scalfani’s viral story Goodbye, Object Oriented Programming.) A copier scans the content of a document and prints it on an empty sheet. So should it be the subclass of Scanner, or of Printer?

      This is only true if you're following things by-the-book without question. It is also making language-dependent assumptions. Java-much?

    6. But don’t take it to the extreme. Sometimes you’re better off writing a new class instead of including masses of dependencies for the sake of DRY (don’t repeat yourself).

      Don't take it to the extreme, indeed.

    7. Except for the fact that this class may actually be a subclass of another class, so now you need to include the parent class too. Then you realize that the parent class depends on other classes as well, and you end up including heaps of code.

      The idea of reusability does not center around reusing code but instead it stresses the importance of reusing knowledge. Reusing code verbatim is not the logical result of DRY.

    8. In a time where compute resources were a lot scarcer than today, this was a genius idea.

      This seems to imply that it's ok to waste compute resources because they are plentiful. Needless to say, that is an incorrect implication.

  4. Apr 2020
    1. When our data changes, React will efficiently update and re-render our components.

      How efficiently? What happens if the application consists of a very deep or wide tree of components? This could be clarified in a footnote or a link to a section of the docs.

    1. Por ejemplo, preguntar por qué los recursos del sistema de salud van para las EPS, en vez de llegar directamente a los hospitales.

      Esta es la pregunta más importante que hay que hacer, no solamente desde el cuerpo Legislativo sino desde la participación ciudadana.

    2. controvertir o llegar a acuerdos

      ¿Se requiere el factor presencial para controvertir? ¿Se requiere para llegar a acuerdos? Qué visión flaca de la comunicación!

    3. Además del respetable concepto que ya cité, mis análisis y los de mis asesores se apoyan en los artículos 138, 140, 149 y 215 de la Constitución y en la Ley 5ª

      El análisis se basa en información pasada, la Constitución (1991) y la Ley 5a (1992) fueron escritos antes de que se asignara el primer proveedor de servicios de internet del país.

    4. Ahí están trabajando personalmente los Congresos de Estados Unidos, Alemania, Italia y Corea.

      ¿Esto porqué importa? Nada tiene que ver con nuestro proceso de raciocinio lo que haya resultado del de los demás. Hay que buscar soluciones propias!

  5. Jan 2020
    1. but how can companies who still doubt Flutter be convinced that they should at least consider using it?

      This implies that companies choose the technologies used and he has a point. I guess technology creators need to find a way to lure both individual developers as well as companies.

    1. In the world model, I placed lists of monsters for each location, considering their “rarity” so that very rare monsters can only be found in a single location, and so on. The idea being that players could share their findings, creating something of a social aspect to the game (Hey, what monster are you missing? I found Lesense in the Temple of Serkekol!).

      It seems to me like the competitive nature of js13k doesn't let judges invest enough time in each game to be able to experience this type of feature in game design.

  6. Dec 2019
  7. tomassedovic.github.io tomassedovic.github.io
    1. We must pass root as a borrowed value because it would be consumed by the first call to handle_keys otherwise.

      What does it mean to "be consumed" in Rust? Is this a reference to the game?