S5 v1: Rust rewrite, CLI tools, and encrypted p2p networking

A while back I posted this error management dashboard I use to manage n8n errors. Since people really liked it and were interested in building their own, I figured I'd show how you could build one using Zite! In the video I also delve deep into some of the inner workings of the system to show you how you can trigger backend workflows from n8n and other interesting tidbits for troubleshooting issues. Link below!

Here are 7 must-have command-line tools for developers, including Btop for resource monitoring, FD for lightning-fast file finding, ASDF for version management, and Tower's very own git-flow-next! 😉 https://lnkd.in/dyYB2kf9

Stop using network config tools from 2006. Seriously! If you're still running Oxidized or Rancid in 2025, We have questions: ❌ Why are you managing production networks with tools that have NO UI authentication? ❌ Why are you dealing with security vulnerabilities that will never get patched? ❌ Why are you explaining to your CISO why your NCM looks like a Linux terminal from 1999? You deserve better. Your network deserves better. Today, we're announcing rConfig V8 Core development – and it's FREE. Here's what we're building: 🎨 A UI that doesn't make you want to cry 🔐 Security built-in, not bolted-on as an afterthought ⚡ Modern architecture (Laravel 12, shadcn/ui) 🔓 100% Open Source, so easy to use! The old guard had their time. Oxidized peaked in 2015. Rancid is literally older than some engineers using it. Meanwhile, we're building what network automation should look like in 2025. 👉 GitHub Issue with full roadmap: https://lnkd.in/enpPFh2U ⭐ Star the repo – watch us build this in real-time 💬 Shape the future – we're listening to what YOU need Development is happening NOW in the shadcn-feature branch. The question isn't "why switch?" The question is "why are you still using tools that stopped caring about you a decade ago?" Time to upgrade. #NetworkEngineering #DevOps #OpenSource #NetworkAutomation #Infrastructure

Most developers stick to client-side pagination even for huge datasets. Here's a simple server side approach with tRPC + Prisma. Thoughts?

Tired of debugging your MCP servers blindly? Meet 𝗠𝗖𝗣 𝗜𝗻𝘀𝗽𝗲𝗰𝘁𝗼𝗿 — a visual tool built to make testing and debugging MCP servers effortless. Here’s what makes it worth a try: 🐞 Interactive React UI — test and inspect responses in real time. ⚡ Zero setup — run instantly with a single npx command. 🤖 CLI mode — perfect for automation and scripting. 🔒 Secure by design — your data stays protected. Stop guessing what’s happening inside your MCP server. Start inspecting it visually, securely, and fast. 🔗 Explore it here: github(dot)com/modelcontextprotocol/inspector ♻️ Found this helpful? Pass it along to another builder. #MCPInspector #DevTools #OpenSource #Debugging #Innovation

even when asking Claude 3.7 reasoning model for a code refactor such as replacing the common network-based MCP server to that which uses STDIO it doesn't do what you expect it to In my example, it doesn't use official MCP package for the transport but rather goes hardcore with Node.js readline module

The CD Dependency Tree is now out of beta. V1 was released yesterday with improved accessibility and links from practices to quick-start guides. I also added a link in the menu to make reporting bugs and features easy. Find it useful? There's a link to buy me a bourbon. Link to the tree in the comments.

Engineers are feeling the heat with Claude’s new stack: Agent Skills, sub-agents, slash commands, MCP servers… it’s a lot. After a week of testing, here’s the big realization: Agent Skills aren’t meant to replace, they’re meant to compose. Think of the ecosystem like this: - Slash Commands → manual triggers for one-off jobs. - MCP Servers → connect to external tools or APIs. - Sub-Agents → isolate or parallelize tasks. - Skills → teach your agent what to do automatically when patterns repeat. If you can build it once, make it a command. If you do it often, make it a Skill.

I once spent hours debugging a backend issue… only to realize my .env variable name didn’t match in the server file 😅 Lesson: Always check your environment variables first. Sometimes, small mistakes teach big lessons.

Along with several bug fixes, XCCacheAgent v1.1 introduces the new “Contextual Errors” feature - making it easier to troubleshoot build failures. Check it out here 👉 https://lnkd.in/ghBaTuh3 What do you think of the new feature?