Businesses crave cohesion. Teams are outputting huge amounts of code across our organisation. They are writing their own tools and dashboards, skills and MCP servers. Solving the same problems and sprawling ever outward.
Don’t take my word for it. If you’re vibe coding something, take a quick peek at the actual code. Your beautiful looking app that took 5 minutes to build has that AI slop feel when reading the actual code. Lots of loose documents floating around. Great architecture. Probly better than I could’ve written. But every repo has a completely different architecture to each other within the same organisation. It’s actually not even close to human readable.
For most projects that doesn’t matter. Tantamount to looking at lower level code generated by a higher level language. Ever since the dawn of high level languages in the late 80s early 90s we have ignored that lower level. Why shouldn’t this be the same? We don’t open the compiled binary and read it and complain about how messy it is, as long as it runs smoothly it shouldn’t matter and I agree.
But the bot can only have so much in its context window. In a large enough organisation sprawl is bound to happen. Eventually the documentation coming out of all these projects becomes too much for any one person to read. Fragmentation slows down the organisation as a whole. Messages go round in giant loops, inefficiencies are buried.
Programmers aren’t writing code anymore. Now we’re all writing the tools that wrote the code. We’re engaging with platform engineering and looking at a bigger overall picture now.
Passing tools and skills between teams so they can help themselves rather than passing around code. We are considering the whole organisation before we even write any code now. We are drawing more diagrams than ever. Why not skip the code and leave the diagrams?
If you generate Warewolf workflows instead you can reuse workflows from across your organisation. The trick is to make all the important entry point workflows for your team available over MCP. When planning new workflows always connect to other teams’ Warewolf MCP servers. Then your workflows will naturally tend to reuse rather than rebuild.
Once you’ve created your workflows, then share the main entry points securely over Warewolf MCP. They are secured by Entra ID by default but can be made public if you are on a VPN or otherwise firewalled network.
When you log into the web studio at app.warewolf.online you can log in using your work email and see all your Warewolf servers. Make sure you’ve added all the other teams’ servers you work with within your organisation.
Instead of sharing long documents no one could possibly read, the workflows themselves are the documentation. Open other teams’ Warewolf workflows in the Warewolf web studio at app.warewolf.online. Or request a screenshot through MCP.
According to Vanitha Kumar, every organisation is building a new platform in addition to the old CI/CD driven platform. She calls the new platform the agentic developer platform. So instead of building this new platform yourself, just use Warewolf instead.
See https://www.aviator.co/podcast/ai-code-review-vanitha-kumar
Leave A Comment?