Umair
1.9K posts





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.











What happened to Android Studio? How do I get rid of this awful lag that happens in the code editor and the terminal? I avoided upgrading for a long time and now I get this.





slop creep is what happens when you turn your brain off and hand the thinking to coding agents each individual change is fine, but all together, you have a pile of crap we're witnessing this happen in real-time across everything boristane.com/blog/slop-cree…


First batch of 50 seats filling 👏👏 This project got me especially excited for some reason. It’s a way to push myself to learn and explore too. Like a learning group. Sometimes we need this type of things to make a change 🙂








