• 0 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle




  • Erm. Duplication of code is ok. Removing absolutely every duplicate function is just premature optimization imho.

    If you have two different customers with slightly different workflow then go ahead and create two mostly the same functions. When you will have 4 different customers with slightly different workflow, then its a time for refactoring, maybe extract basic same functionality into separate function/object, maybe introduce dynamic workflow using finite automata, maybe extract these functionality to separate modules… but never do it prematurily.

    Imho, sometimes ,removing of duplication very much increases complexity and code became hard to understand and hard to modify.










  • I understand you point of view, but honestly it will be good to have possibility to quickly check 'commit successor in a graph view from a phone.". I’m working with quite legacy systems (15-20yo) and sometimes, when I have some ideas about resolving some issues it will be good to quickly check backward and forward histories of commits around to verify something…

    Thats not a dealbraker at all but it will be nice to have.


  • Most of the visualization problems are solved by a decent desktop client.

    From article:

    I am told that Git users commonly install third-party graphical viewers for Git, many of which do a better job of showing recent activity on the project. That is great, but these are still more third-party applications that must be installed and managed separately. Many are platform-specific. (One of the better ones, GitUp, only works on Mac, for example.) All require that you first sync your local repository then bring up their graphical interface on your desktop. And even with all that, I still cannot see what I typically want to see without multiple clicks. Checking on project status from a phone while away from the office is not an option.