Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.
After 3 years, 47 releases, Ark VCS has finally reached 1.0! 🎉
https://t.co/7gHuTR5LBC
It's a big release, with features that I've never seen to any version control system out of the box, like built-in changelist build status.
If you're tired of #perforce and #git, get it from https://t.co/u2zs8UNDfP!
#gamedev #indiegamedev #softwaredevelopment
@Ambiera The fun part: If you want multiple licenses, for example for your kid: You need yet another MS account (afaik). So, you have to have another email, sign-up a MS account, that adds like another 5 steps with verification, nagging etc.
Create Types on Demand and Cecilifier: https://t.co/FXQ1qDptaB. Part of the #CSharp advent: https://t.co/NVzPSogU6C . Thanks @adrianoverona for Cecilifier.
#csadvent is now open for sign-ups! Check out how it works: https://t.co/IOvB1ztwx9
... then claim a day. If you've got an idea for some good, fun, useful, and/or cool #csharp content, you should sign up. 50 total slots open right now.
Every-time I debug a Maven or SBT build I got reminded how understandable https://t.co/Jeiu7Rhtaa builds are.
Mill build stays my 'least-hated' build system, which is a good sign for a build system ;) #Java#Scala