How do we use AI in QA? Lately, conversations surrounding AI have entered the testing space. In presentations, meetings, and roadmaps, the same question almost inevitably appears.
As manual QA professionals with over a decade of experience, we’ve found one thing to be true: AI can assist, but the final decision must remain with us.
This article explores how AI supports manual testing while human judgment stays central to quality decisions.
More and more, it is about defining intent, guiding AI systems, and staying in control of the outcomes they produce. This shift is already changing how software is built and how the developer’s role is evolving.
In this article, we are going to explore what this transition means, the development paradigms that are shaping it, and also the risks of losing control if AI is used without enough experience and oversight.
As Kubernetes evolves, so does external traffic management. NGINX Ingress Controller, the standard for many setups, will reach end-of-life in March 2026 and stop receiving updates or fixes.
This means that all clusters must start implementing new strategies for managing external traffic.
This article identifies the key impacts of the deprecation as well as the main challenges and possible solutions. It will conclude by establishing why Envoy Gateway is a great candidate for continuing forward.
For years, web applications are no longer defined only by how well they perform on a stable network connection.
People work on trains, elevators, factory floors, and other places where connectivity is unstable or unavailable. In today’s cloud-based world, applications constantly interact with services, distributed systems, and enterprise platforms. Under these conditions, traditional web applications fail fast: user actions block, requests time out, integrations break, and work is lost.
Software development is a constantly evolving field that strives to meet market demands. In today’s landscape, scalability and the ability to ship fast, atomic updates are critical, as users expect quick fixes and zero downtime.
A solid architecture is essential; but, as in life, there is no “silver bullet” or one-size-fits-all solution in software engineering. Engineers must understand the trade-offs and choose the right tools for the problem.
