Gareth Edwards

Check your chapter image for a screenshot of the heat map in action and try it yourself by following the link in the newsletter. It's now time for Sponsored News. DevOps is now multiplayer. We're excited to see Adam Jacob and team make the next frontier of DevOps automation generally available. DevOps is now multiplayer and real-time.

Check your chapter image for a screenshot of the heat map in action and try it yourself by following the link in the newsletter. It's now time for Sponsored News. DevOps is now multiplayer. We're excited to see Adam Jacob and team make the next frontier of DevOps automation generally available. DevOps is now multiplayer and real-time.

You can define and manage your infra as a living architecture with everyone that needs to be involved playing their role in parallel. DevOps was never a solo game, so why should you remain siloed in PRs and merge requests just waiting? That's the old way. You also have full programmability. You can write small, reactive functions to model new services in minutes.

You can define and manage your infra as a living architecture with everyone that needs to be involved playing their role in parallel. DevOps was never a solo game, so why should you remain siloed in PRs and merge requests just waiting? That's the old way. You also have full programmability. You can write small, reactive functions to model new services in minutes.

You can customize existing models to conform to organizational security policies and contribute back to the community if you'd like. All of this from within the app. Plus, full batteries are included. Everything your team needs to run a production infrastructure is in the box. There is no need for other platforms, glue code, or state file management. Everyone is on the same page all the time.

You can customize existing models to conform to organizational security policies and contribute back to the community if you'd like. All of this from within the app. Plus, full batteries are included. Everything your team needs to run a production infrastructure is in the box. There is no need for other platforms, glue code, or state file management. Everyone is on the same page all the time.

The icing on the cake is always up-to-date change sets. Just like Git, change sets essentially fork the entire hypergraph of functions. This allows teams to propose changes, validate the safety and security of their configurations, and keep things up to date as the environment changes. To experience DevOps in multiplayer mode, go to systeminit.com.

The icing on the cake is always up-to-date change sets. Just like Git, change sets essentially fork the entire hypergraph of functions. This allows teams to propose changes, validate the safety and security of their configurations, and keep things up to date as the environment changes. To experience DevOps in multiplayer mode, go to systeminit.com.

They have a generous free tier, so please try it out yourself. Once again, that's systeminit.com. The disappearance of an internet domain, also known as nomo.io. This piece by Gareth Edwards highlights just how fragile the internet really is.

They have a generous free tier, so please try it out yourself. Once again, that's systeminit.com. The disappearance of an internet domain, also known as nomo.io. This piece by Gareth Edwards highlights just how fragile the internet really is.

Quote, On October 3rd, the British government announced that it was giving up sovereignty over a small tropical atoll in the Indian Ocean known as the Chagos Islands. The islands would be handed over to the neighboring island country of Mauritius, about 1,100 miles off the southeastern coast of Africa. The story did not make the tech press, but perhaps it should have.

Quote, On October 3rd, the British government announced that it was giving up sovereignty over a small tropical atoll in the Indian Ocean known as the Chagos Islands. The islands would be handed over to the neighboring island country of Mauritius, about 1,100 miles off the southeastern coast of Africa. The story did not make the tech press, but perhaps it should have.

The decision to transfer the islands to their new owner will result in the loss of one of the tech and gaming industry's preferred top-level domains, .io. End quote. Once the treaty is signed, the British Indian Ocean Territory will cease to exist. Will the .io domain go with it? Probably not. There's too much value tied up in it for that to happen, in my opinion. But it certainly could.

The decision to transfer the islands to their new owner will result in the loss of one of the tech and gaming industry's preferred top-level domains, .io. End quote. Once the treaty is signed, the British Indian Ocean Territory will cease to exist. Will the .io domain go with it? Probably not. There's too much value tied up in it for that to happen, in my opinion. But it certainly could.

And that's kind of scary, isn't it? Cognitive load is what matters. Warning, I'm highly tempted to quote this entire article. I will do my best not to, but you've been warned. Quote, there are so many buzzwords and best practices out there, but let's focus on something more fundamental. What matters is the amount of confusion developers feel when going through the code.

And that's kind of scary, isn't it? Cognitive load is what matters. Warning, I'm highly tempted to quote this entire article. I will do my best not to, but you've been warned. Quote, there are so many buzzwords and best practices out there, but let's focus on something more fundamental. What matters is the amount of confusion developers feel when going through the code.

Confusion costs time and money. Confusion is caused by high cognitive load. It's not some fancy abstract concept but rather a fundamental human constraint. Since we spend far more time reading and understanding code than writing it, we should constantly ask ourselves whether we are embedding excessive cognitive load into our code. End quote. All right, that's it. I'm stopping right there.

Confusion costs time and money. Confusion is caused by high cognitive load. It's not some fancy abstract concept but rather a fundamental human constraint. Since we spend far more time reading and understanding code than writing it, we should constantly ask ourselves whether we are embedding excessive cognitive load into our code. End quote. All right, that's it. I'm stopping right there.

Just go read it. The overarching point is that we should reduce the cognitive load in our projects as much as possible. But how? That is the news for now. But also scan the companion newsletter for even more stories worth your attention. Like Chris Wanstroth on life after GitHub. Can you get root with only a cigarette lighter? Spoiler alert, yes. A sweet Firefox theme for the TUI enthusiast.

Just go read it. The overarching point is that we should reduce the cognitive load in our projects as much as possible. But how? That is the news for now. But also scan the companion newsletter for even more stories worth your attention. Like Chris Wanstroth on life after GitHub. Can you get root with only a cigarette lighter? Spoiler alert, yes. A sweet Firefox theme for the TUI enthusiast.