x2tyfi
The biggest challenges that most of us networking people have are around velocity (how fast we can build and scale networks) and how effectively we can operate them (avoid defects, fix them fast when something breaks).
LLMs are great in both areas. AI helps with deployment challenges by speeding up tooling development and the creation of workflows on orchestration platforms. A manual process step today, say - reserving an IP address in an IP DB — is automated the next day instead of on a backlog for years. This post is an example of that (config-gen/config-deploy).
Operations use-cases are more interesting, IMO, and address the “too many signals” problems that we face. Network substrate telemetry, overlay telemetry, service host metrics, service metrics, customer metrics, recent change data, prior alarms - the list goes on. Being a network operator is not for the faint of heart and is under-mentioned on high stress job lists. AI makes AMAZINGLY good network operations triage agents, since they are able to immediately process so many signals.
Exciting times!
I also re-investigated containerization - weighing Docker Swarm vs K3s - and settled on Docker Swarm.
I’ve hated it ever since. Swarm is a PITA to use and has all kinds of failure modes that are different than regular old Docker Compose.
I’ve considered migrating again - either to Kubernetes, or just back to plain Docker - but haven’t done it. Maybe I should look at Uncloud?
My first website was a geocities site back in ~1999, which was dedicated to StarCraft. I wish I could find it now; I remember it being really aesthetically pleasing - it would be funny to see how it held up.
It’s never good when your primary ISP’s only connection out to the world is via satellite
* 2018: $99 to $119
* 2022: $119 to $139
We should expect a price hike from $139 to $159 in 2026, assuming the trend continues.
If it’s before, then you can easily tie consciousness and free will together. If not, we are effectively watching videos of our bodies operate. Oh - and there is no spoon.
I look at it in a similar light to nutritional guidelines.
For most large businesses, 90%+ of major network events are caused by internally-driven network config changes.
Depending on how far along the business is towards automation, a proportion of the 90% can be attributed to a human going “off script” - I.e.: making a change that had not been reviewed.
My biggest/only concern - which they gloss over, mostly — is security. Combining networks puts added responsibility on every family that joins. What if friend-X’s kid downloads a virus-riddled torrent, which is capable of multiplying across hosts?
Your own hosts/perimeter can always be protected, but there’s a loss of control with this setup.
The only use case I can imagine is a legacy game which performs a server search by broadcasting/scanning the local network. And even then - most of the time these games had server browsers.
And when you achieve that was-lower-then-higher-but-now-lower-again temperature, it should be more juicy
1. finish temperature (as mentioned in this article) 2. peak temperature
In these tests, the finish temperature and peak temperature were the same - he sliced while carryover cooking was still climbing. However, when resting, most people achieve a peak temperature (due to carryover cooking), then roll down the other side of the curve to a lowered temperature.
As you imply, a longer rest - in conjunction with protein pulled at just the right time - can likely result with both the perfect (to taste) peak temperature, and a lower (and more juicy) slicing temperature
Network Engineering design docs can be somewhat formulaic structurally, making the LLMs job simpler. I imagine in the near future we’ll just ask them to follow doc templates or reference other designs within a RAG system to ensure there aren’t gaps in the doc, etc.
When I came back to the recruiter, I asked how much room she had to negotiate, and asked if she could put me “in the middle of the band”. She immediately said yes and it resulted in a bump of $75k/yr or so.
The thing to remember is that recruiters key metrics are about hires. They desperately want to get people in the door, especially after going through all of the effort to schedule interviews. They will happily help you out within reason.