public

8451 bookmarks
Custom sorting
MICHAEL JACKSON on Twitter: "Honestly, it makes a ton of sense for Microsoft to buy GitHub. After this acquisition, they will control: - VS Code - TypeScript - Electron - GitHub This puts them pretty much front and center of the modern development stack f
MICHAEL JACKSON on Twitter: "Honestly, it makes a ton of sense for Microsoft to buy GitHub. After this acquisition, they will control: - VS Code - TypeScript - Electron - GitHub This puts them pretty much front and center of the modern development stack f
·twitter.com·
MICHAEL JACKSON on Twitter: "Honestly, it makes a ton of sense for Microsoft to buy GitHub. After this acquisition, they will control: - VS Code - TypeScript - Electron - GitHub This puts them pretty much front and center of the modern development stack f
Twitter
Twitter
@johnbarton on the other hand, maybe I'll be unable to buy any new kindle books on my current account post July-1st…
·twitter.com·
Twitter
Rust review: The borrow checker - Julio Merino
Rust review: The borrow checker - Julio Merino
You can think of the borrow checker as a validator for a locking system: immutable references are shared read locks and mutable references are exclusive write locks. Under this mental model, accessing data via two independent write locks is not a safe thing to do, and modifying data via a write lock while there are readers alive is not safe either
·julio.meroh.net·
Rust review: The borrow checker - Julio Merino
Pinboard: Frequently Asked Questions
Pinboard: Frequently Asked Questions
I had no idea @Pinboard could archive my tweet history, with the option to mine it for links - sound super handy
·pinboard.in·
Pinboard: Frequently Asked Questions
Fear and Loathing in Legacy Code - Typemock
Fear and Loathing in Legacy Code - Typemock

Why is legacy code an issue however we define it? You’d probably offer responses talking about risk, high defect rates, and unpredictable deployments. You might also talk about slow times to market and difficulty responding to changing business needs.

All of this is true. But none of this, I would argue, poses the largest risk to your organization.

Instead, it’s the fear that poses the large risk. Well not the fear itself, but rather the problems that the fear creates—the human problems

·typemock.com·
Fear and Loathing in Legacy Code - Typemock