20 Matching Annotations
  1. Jan 2024
  2. Jul 2023
  3. Jan 2023
    1. we have individual capitalists who try 00:48:45 to make the most profit and this is linked to their capital and productivity so to achieve more in less time and 00:48:57 productivity is linked to energy [Music] the only source of energy to increase profit is carbon oil and gas and this has resulted in a change in our 00:49:15 atmosphere we have to put an entities if we wish to live in our planet can our capitalism do this based on the current data we won't be able to do so 00:49:28 therefore perhaps we should do the following reflection if capitalism is unable to do so either Humanity will die with it or 00:49:42 Humanity will overcome capitalism so that we can live in our planet

      !- Urrego : Key Point - Can capitalism rapidly detour away from fossil fuels? The current data indicates no. So either Humanity does our it drops capitalism

  4. Nov 2022
  5. May 2022
    1. We reduce risk in the shaping process by solving open questions before we commit the project to a time box.

      We don't give a project to a team that still has rabbit holes or tangled interdependencies.

  6. Mar 2022
    1. Ruby Object Mapper (rom-rb) is a fast ruby persistence library with the goal of providing powerful object mapping capabilities without limiting the full power of the underlying datastore.
  7. Jan 2022
  8. Jul 2021
  9. May 2021
  10. Mar 2021
    1. I'm kinda stuck at the moment, going around in circles. Everything is really heavily coupled. I would like to get to the point where no load is called from within processors, but i'm not sure if that's possible. Currently the API and the caching strategies are fighting me at every step of the way. I have a branch where i'm hacking through some refactoring, no light at the end of the tunnel yet though :(
    1. it's super hard to test master because i have no idea which gems need to be updated. is there a guide on how to take a rails 4.2 project to master sprockets without everything mysteriously exploding? ill try to make a repro case but its hard to tell where to even start
  11. Feb 2021
    1. Not all cases can be covered and easily restored. And sometimes when we will reuse this function for different use-cases we will find out that it requires different restore logic.
    2. But why do we return 0? Why not 1? Why not None? And while None in most cases is as bad (or even worse) than the exceptions, turns out we should heavily rely on business logic and use-cases of this function.
    3. So, the sad conclusion is: all problems must be resolved individually depending on a specific usage context. There’s no silver bullet to resolve all ZeroDivisionErrors once and for all. And again, I am not even covering complex IO flows with retry policies and expotential timeouts.
  12. Jan 2021
  13. Nov 2020