Networking of the packets kind, data centers; https://xitter.cf/t.co/zBUK2ylcpp
Joined August 2013
- Tweets1K
- Following145
- Followers2K
- Likes653
Dinesh Dutt retweeted
And he shares his witty line about OSPF And IS-IS😎 #CiscoLiveEMEA @Peter_Paluch – at Amsterdam, The Netherlands
Dinesh Dutt retweeted
BLOG: Multi vendor route observability with suzieq and tig stack. This was fun to create a demo telegraf plugin for SuzieQ to check routes within a environment and present them Grafana. The git repo can be found within the blog as well. danielhertzberg.net/posts/su…
Interesting and useful paper.
At SIGCOMM '23 tomorrow, Dan Halperin will present a paper that I can only describe as labor of love.
It describes our key learnings while turning @batfish_ from a research toy to an industrial-strength network verification tool.
dl.acm.org/doi/10.1145/36032…
Dinesh Dutt retweeted
Check out our latest YouTube video! Where we take a deep dive into SuzieQ Enterprise, exploring its features and showing how it stands out from its open-source counterpart. buff.ly/45Y4lds. #NetworkAutomation @SuzieqProject
Had a fun time chatting with @rickjdon
Check out our latest YouTube video! Where we take a deep dive into SuzieQ Enterprise, exploring its features and showing how it stands out from its open-source counterpart. buff.ly/45Y4lds. #NetworkAutomation @SuzieqProject
Dinesh Dutt retweeted
This week in polars new release:
- Streaming unions! (much harder than it sounds).
- Fused arithmetic in the expression engine.
- specialized rolling covariance and correlation expressions. Those are 3.5x faster than a pandas baseline and use 0.5x the amount of memory.
1/2 🧵
Dinesh Dutt retweeted
🔥 If you read one thing about AI this week, let it be Google’s leaked doc
“We have no moat, and neither does OpenAI”
Readers added context they thought people might want to know
Per the source, the internal document is the opinion of a "researcher within Google" and not necessarily Google's view.
semianalysis.com/p/google-we-ha…
Thanks for an amazing session @rickjdon
Just finished recording an incredible Tech Showcase on SuzieQ Enterprise. I thought the community version was good, but oh boy, this is a game-changer! Stay tuned for the recording! #networkautomation @SuzieqProject @ddcumulus
Dinesh Dutt retweeted
In less than seven years, #NetBox has gone from a hobby project to the core product of an independent business, with tens of thousands of deployments worldwide. I cannot imagine where we'll be in just a few more years.
Thank you to everyone who has helped us along the way!
We raised $20 million in Series A funding to make #NetBox the first choice for every networking professional on the planet. netboxlabs.com/blog/announci…
I very much appreciate the invitation to speak! Looking forward to engaging.
Great meetup on its own and with SuzieQ on the agenda I hope to meet you there! lnkd.in/gsBhbGkN
Kudos to you @RitchieVink and the @DataPolars team for such a fast-paced development! I filed a bug on day 1, fix released the same day, followed soon by 0.16.15. it's a pleasure working with you all. Thank you for this gift to the community.
New polars release:
github.com/pola-rs/polars/re…
With
Full out of core support for streaming groupby and unique.
And
Runtime dispatch of SIMD acceleration of min/max and mean kernels. Having a 2-5x speedup for those aggregations.
And much more. Thanks to everybody involved.
So what you're saying @ioshints is there are lies, damned lies, and ChatGPT 😁
[Blog] Worth Reading: The Dangers of Knowing Everything ift.tt/Tpg4Pni
Dinesh Dutt retweeted
I believe network diagrams are a critical part of being a network engineer. Diagrams during the design phase are essential. But manually created diagrams to document state is insane in todays world.
SuzieQ Enterprise actually has a very nice and SUPER fast diagram engine.
I'm starting to use the excellent netlab(github.com/ipspace/netlab) by @ioshints. The multilab plugin is really helpful as I spin up a bunch of different labs to test @SuzieqProject
7/7 The main point underlying across all these is that network engineers need easily consumable network state, and doing that is hard across vendors, versions and time.