bellwether

Typically, in a RwLock, once a Writer locks, Readers are blocked, until the Writer unlocks. Similarly, a Writer lock waits until all current Readers unlock too, so you get contention on both sides. RwLock only lets multiple concurrent Readers lock against themselves, but any mixture causes full locking.

In this article, the locks are mutually exclusive. Reads are not blocked by Writes, and vice-versa, but Writers would block against other Writers.

The downside is that Readers need to check which "version" of the data they read, to see if it was modified during the operation by a Writer--since Writers do not block for Readers like they do with RwLock.

It's elegant because, in most scenarios, Readers will not need to re-read because the version won't change mid-run between an optimistic read lock and its unlock. In the cases where that does happen, your code needs to handle retrying the read / loop logic, which is why the article argues for a compiler mechanism to enforce that check and avoid "foot gun" scenarios.

Exciting! For search purposes, would this be Motionlang, a la Golang?

Love things like this!

Your resume is not a biography, it's a sale pitch. Tailor multiple versions of it, one for each specific type of job you are applying for, and drop the things that won't help you close the sale.

I'm a hands-on full stack engineer with a passion for product research, management, and development. I can do everything from Figma mockups, to database schema design, to backend and frontend development, to cloud infrastructure and scaling.

Does anyone need collaboration on a DeFi, web3 smart contract, or other FinTech project? If so, please reach out to me (email is in profile).

Love this!!

This is a bad rule and even worse advice.

Love this idea, can’t wait to try it out!

Love the ingenuity and thank you for the performance comparison on Cloudflare Workers vs AWS Lambda. I personally wouldn’t consider what you built a Geolocation service, but glad it solved your use case!

This is a law suit over Google Analytics and JavaScript based tracking, not browser based tracking in Incognito mode.

I've never seen this in any company I've worked at.

Personally, if I saw members on my team looking for work, I would want to understand that decision: is it for personal reasons, is it because they felt unable to grow, is it because of salary, or is it because they find the work no longer meaningful?

There are plenty of reasons to move on from a role. Firing someone for wanting something that aligns better with their future is beyond petty imo.