Crier1002

I'm interested in knowing more about how companies typically gauge the freshness of their codebase dependencies. putting all the nuances/details aside, i think we can all agree that having a codebase with most dependencies that are over 8 years old is a pretty clear indication that it's way overdue for an update, right?

i was thinking, would it be helpful to keep track of how far behind each dependency is in terms of minor, patch, and major updates? but this seems a bit too complex to explain to the management. i'm trying to figure out the best way to explain this to management so they understand why it's important to stay current. any ideas on how we can measure improvements? maybe we should agree on a few key factors to track our progress and see if we're getting better or worse.

i just love the details on this one. thanks for sharing!

depends, if you need to spend time with her, bring her our for dinner, etc.

as someone who is interested in this, i do think that having personal sites on the showcase is a good thing

if you’re on iOS, i found that the focus feature + screen time limit is pretty good at this. basically you can block out any notifications that you want for a set period of time. but yea, it still doesnt stop you from physically reaching out to your phone

this is a great article! I love how you explained it. here are my takeaways from it: - Bloom filter is a space-efficient data structure - You're trading off some accuracy (possibility of false positives) for the significantly smaller memory footprint and faster membership checks