WiL (World Innovation Lab)’s Post

Product Launch Announcement: We're excited to announce that Parallel branching is now available in beta! Parallel is multi-path branching operator that allows you to create multiple execution branches with optional filtering rules. By default, workflow steps are executed serially and in sequence — only one step can run at a time. Parallel execution unlocks the ability to run steps concurrently. Unlike Switch and If/Else, the order in which rules are defined will not affect the path of execution. This offers the capability to: - Create non-linear workflows that execute steps in parallel branches - Define when branches run — always, conditionally or never (to disable a branch) - Merge and continue execution in the parent flow after the branching operation As another example: If you need to make multiple LLM queries that are not dependent on one another, you can now make them in parallel and then reference the responses in the parent flow. (You may also optionally apply filtering rules to control when each branch executes.) Check out our docs to learn more, and let us know if you have any feedback in our Slack Community Docs - https://lnkd.in/eG8E7x4Z Slack - https://lnkd.in/eBZXHQ7M What will be the first thing you build with Parallel?

I preach a lot about Zenhub here on LinkedIn... But the reality is that we've been a part of the problem when it comes to why so many teams hate using project management tools. What problem is that? The fact that, in 2024, updating PM tools is still largely a manual task and that something as simple as updating a "field" on a ticket still often involves manual work for devs and PMs. Here's a thought exercise... If you had to guess, what's the average amount of time that it takes an individual to update a single field on an issue? 5 seconds? 10 seconds? More than 10 seconds? We looked into the numbers, and on average, it takes an individual on average about 12 seconds to update a single piece of metadata on an issue. That might not sound like much in the moment, but when you consider teams are doing this dozens of times a day (for multiple fields)...it adds up. No wonder no one likes using PM tools... That's why over the past year, we've been investing so much time and effort in building out more automation at the team level to help cut down on these manual, repetitive tasks. Today, we're excited to announce our latest automation, aimed at eliminating the need to manually update Issue metadata as work flows through the different development stages: Smart Pipelines. Check out the launch below, and let us know what you'd like to see us automate next! #agile #projectmanagement #scrum #kanban #WIPlimits #automation #AI #github #zenhub #developers

🚀 Discover the secrets behind automating deploys at scale with Slack! 💡 Dive into the challenges of deploying changes in a monolithic service and explore how ReleaseBot, armed with z scores and dynamic thresholds, ensures safer, faster, and more confident deployments. https://lnkd.in/dE9zJC6h

In our quest to answer the question "Can you measure developer productivity?", Daniel Horton and I trying to break this down into three major themes - Understanding productivity, how software development adds value to an organization, and why is everyone so obsessed with developer productivity - Exploring developer productivity frameworks, what we see people doing, and what is a good model - Moving past developer productivity with developer experience In this video we try to understand; - Why are CTOs being pushing for developer productivity - What are CEO/CFOs becoming more impatient with software delivery - What are the reasons why your company might be pushing for developer productivity #developerproductivity #developerexperience #softwaredevelopment

In my blog #TechTacoFriday I frequently receive questions from readers and viewers about how to optimize and streamline their workflows. Recently, one such question came in that I believe resonates with many people managing workspaces in DevOps environments: "I have 3 workspaces dev, test, prod, my dev workspace is synced with main branch so when I change something in my pbip file and commit it to main branch, so it shows updates in source control and every time I have to go to workspace and click push button. I want to automate this process [...]." This question addresses a common pain point: the need to repeatedly push updates manually in a workspace every time changes are made. In this article, I’ll walk you through my suggested approach to automating this process using Fabric's 'Update From Git' REST API, which updates the workspace with commits pushed to the connected branch. This solution ensures a smoother workflow with less manual intervention. Check the article here https://lnkd.in/ercpCG4B or go directly to the demo, I prepared a youtube video as well for this one 😁 https://lnkd.in/epwa-Qx8

🚀 We’ve Open-Sourced Originzero! 🌍 Our low-code workspace automation tool, Originzero, is now open-source and available on GitHub! 🎉 We’re calling on everyone passionate about low-code systems and making automation easier for businesses and individuals to contribute to the project. The more nodes we have, the more versatile and powerful the platform becomes. You can also find both developer and user documentation in the GitHub repository to help you get started. If you have ideas or want to discuss improvements, feel free to join the conversation via GitHub Discussions or our Discord server. 💬 By contributing to Originzero, you’re not only supporting the open-source community but also helping to build an ecosystem that simplifies workflow automation. 💡 🔗 Check out the project, contribute, join the discussions, and let’s grow Originzero together! GitHub Repo: https://lnkd.in/d7r3DyT6 Discord: https://lnkd.in/dAABthR8 #OpenSource #LowCode #NoCode #Automation #Originzero #GitHub #WorkflowAutomation #NodeBased #NodeDevelopment #Collaboration #Documentation

Mastering Chaos Engineering is the key to unstoppable software success in today's digital landscape. Embracing failure, building a culture of resilience, and leveraging automation are crucial elements in this journey. Realize the business value of robust systems and stay ahead of the curve by continuously experimenting and learning. From chaos to control, harness the power of chaos to drive innovation and achieve unparalleled success. #ChaosEngineering #SoftwareSuccess #ResilienceInTech

In today's article, Anton Samsonkin, Senior Service Engineer, discusses the topic of application support with Atlassian’s AI-powered solutions. He investigates the most interesting functionality of the #Atlassian Intelligent platform, the ability to launch virtual assistants for your support projects, and shares the case of how the company managed to implement this idea in their product for technical support – “Jira Service Management.” To discover what’s under the hood of the intellectual platform read the new article: https://lnkd.in/edwhHPw9 

Simplified Container Tools in your Workflow 📌 #Lazydocker Commend-Line Management : It is a user- Friendly Terminal tool for All together in one Place . it is Managing images, containers and Volumes. You Are able to view logs, Resources usage, Start , Stop Other Details in one Place. 📌 #Dive Tool : Dive using for analysis your images layer-by-layer , Mainly Focusing on the space of the image and how optimizing it. Additionally it will find the duplicate Layer, unnecessary layers. it will help the application run fast and image lightweight. 📌 #Portainer Tool : It is simple for the Web-based Visualisation tool managing your Docker images and containers. 📌 #WatchTower Tool : Automatic Updates: It checks for new images and pulls them automatically. Restart Updated Containers: Watchtower stops and restarts containers with the updated images. Selective Updates: You can specify containers to exclude or include. Notification Support: Inform you when updates occur. 📌 #Dockly Tool : Provides an efficient and visual way to manage Docker containers and resources. Ideal for users who prefer terminal tools over graphical interfaces. Great for quick debugging and monitoring tasks. 📌 #Dry Tool : Lightweight and fast. No need for a GUI; works entirely in the terminal. Perfect for quick monitoring and debugging tasks.Easy to use for both local and remote Docker environments. 📌 #SlipLane Tool : No Port Collisions: Avoids issues where multiple services attempt to use the same port. Streamlined Development: Makes local development smoother by automating port mapping. Service Isolation: Each service gets its own dynamic port, reducing conflicts. 📌 #Orbstack Tool : Improved Performance: Faster and more efficient than Docker Desktop. macOS Native: Tailored for macOS users, leveraging native features. Easy Setup: Simple to install and use with existing Docker workflows. Lower Overhead: Saves system resources, making it ideal for development on laptops. #Docker #Devops #Container #DevopsCommunity #kubernetes #Devsecops #Dockercommunity #TechXconference

Did you know, no/low-code business rule engines can reduce up to 70% of developmental costs?? Our No/Low code platforms put the subject experts in the forefront of not just strategizing business decisions and rules but also implementation. This means more agile operations, enhanced collaboration, and real-time decision making. Do you believe in a no/low code future? #DecesionEngine #BusinessRuleEngine #ProcessAutomation