Comments by "p11" (@porky1118) on "DRY Software Patterns u0026 Microservices" video.

  1. Sometimes, when a function is very general and will most likely not need module specific changes, it would make sense to share it between multiple modules.
    3
  2.  @zerettino  No, general is not technical. It means it's not special purpose. It has many use cases. It can be used in many circumstances. If you recognize some pattern in many of your modules, which could be generalized, and will still work if the modules change, it makes sense to put them into a module used by both. Even if it will cause a lot of coupling, that's not a huge problem. You can still refactor by just copying the affected function(s). So it shouldn't be too bad.
    3
  3. I kind of hate these acronyms for programming principles. I always think "Oh, another weird business technique, I'm not interested in". And most of the time, when I find out, what one means, it's either common stuff, I do anyway, because not doing it that way would be stupid (for example DRY), or it does not apply to the languages I'm using (like SOLID mostly).
    1
  4. 8:00 That's basically what I do with my projects. If I see some functionality, that might be useful for other programs as well, or when I need it for another program and don't want to rewrite it, I create a new repo, add this submodule of the existing program into that repo and let the other program use it. When I find a bug in my new repo or have ideas for improvement, or if I need to extend it to work with one of my programs depending on it, I have to upgrade the repo, but not all programs, which depend on it. Sometimes I do, sometimes I don't, most of the time I at least plan to upgrade to a newer version some day. Especially when using Rust, it's easy to have different programs using different versions of the same library.
    1
  5. 3:50 Only three of the lines are repeated. The last one is always different. It might be useful to only put the three same lines into a new function.
    1