I like it, and agree with most of it. One point I differ on is dependencies. My experience is that pinning them makes the eventual upgrade too difficult. I favor regular maintenance and updating of the deps. I think of them as an organism that needs regular care.
i haven't used either but being on Gitlab, Renovatebot looks interesting. Last time I had a say in this, I took the approach of targeting the main framework for regular upgrades, and letting that determine the upgrade version for all other dependencies. This is mostly because dep version updates can be so risky. I'm not sure if auto updates on all deps would work or not but I would like to give it a try.
I like it, and agree with most of it. One point I differ on is dependencies. My experience is that pinning them makes the eventual upgrade too difficult. I favor regular maintenance and updating of the deps. I think of them as an organism that needs regular care.
I completely agree with that. I use tools to automate the process of updating the dependencies like renovatebot or dependabot.
Do you think we can have both?
i haven't used either but being on Gitlab, Renovatebot looks interesting. Last time I had a say in this, I took the approach of targeting the main framework for regular upgrades, and letting that determine the upgrade version for all other dependencies. This is mostly because dep version updates can be so risky. I'm not sure if auto updates on all deps would work or not but I would like to give it a try.
Awesome article Petar, congrats on 10k subs!
Thank you friend!
The project structure is in itself a constrain for new developers to follow the same patterns. It can be the best documentation possible!
Indeed!