Systems | Development | Analytics | API | Testing

Let me take you on a journey—not into some far-off sci-fi future, but into a tomorrow that’s just around the corner. Imagine this: you walk into your workplace and some of your “colleagues” are no longer human. They’re not robots in the traditional sense, but agents—autonomous software entities, each trained on vast datasets, equipped with decision-making power, and capable of performing economic, civic, and operational tasks at scale.

Test case design constantly adopts new languages, architectures, and methodologies. But in the last few years, the pressure to scale while ensuring quality in a smart way, without overly increasing efforts, has changed the narrative. AI has entered the scene, promising to systematize decisions, reduce redundancy, and even create tests from scratch. Some teams have already experimented with AI, while others observe with skepticism.

Chatbots are quickly becoming more sophisticated and integrated into business workflows, enhancing productivity and scalability. However, they also expand the attack surface for organizations. This new exploitation vector requires data engineers and security teams to incorporate various security guardrails when building their gen AI architecture. In this blog post, we discuss the risk of data leakage through AI chatbots.

In March 2024, the European Union passed the AI Act. This sweeping regulation reshapes how organizations deploy and manage AI systems. The law addresses AI risks that could affect both individuals and businesses, from hiring biases to critical infrastructure failures. Similar rules have started taking shape across the world, including several state-based regulations in the US. But the regulation is only the floor. We all share the responsibility of creating a safe, responsible AI future.

Devoxx Poland 2025 felt different. Not because of revolutionary new frameworks or another "this changes everything" moment, but because of what didn't happen. The conference had an unusual dose of pragmatism, skepticism, and – dare we say it – common sense. Maybe it's because developers are asking the right questions: "Does this solve a problem?" and "What happens when this inevitably breaks?" Here's what emerged from the sessions we watched, and the people we spoke to.

The era of generative AI is upon us, and large language models (LLMs) like Claude are demonstrating incredible potential to revolutionize how businesses operate and interact with customers. However, to truly unlock this potential, AI needs secure and standardized access to the wealth of information and services locked within enterprise systems. This is where standards such as Model Context Protocol (MCP) come in, offering a powerful way to make enterprise resources AI-consumable.