What is Green IT– Strategies and trends lined out
Read about how you can help reduce CO2 by creating sustainable IT solutions.

Head of Application Development

17 years
JVM
Application Development
Solution Architecture
Artur is a department head at VirtusLab, with a career spanning diverse roles in automation, robotics, and software development. With extensive experience in Java and the JVM ecosystem, Artur combines deep technical expertise with a results-driven approach to deliver modern, scalable, and reliable solutions for clients of all sizes – from large enterprises to start-ups.
He takes a pragmatic approach to development, balancing technical excellence with a deep understanding of business drivers. His focus on aligning technology with client goals ensures solutions are both impactful and future-proof.
Beyond his technical achievements, Artur is an enthusiastic advocate for Java and its ecosystem. He actively explores the latest trends in the JVM world, sharing insights through his dedicated newsletter – complete with a custom avatar inspired by himself.
Read about how you can help reduce CO2 by creating sustainable IT solutions.

Discover VirtusLab's strategy for digitally transforming critical elements of a legacy system while ensuring the continuity of daily business processes. The journey centers around our partnership with a significant retail industry player, where we revitalized an essential segment of their legacy system.

What is the future of Java? Take a look at Java's strengths and the impact of Java 21 on modern enterprises.

Explore how MCP transforms JVM tools like WildFly and Ghidra into LLM-driven operations, diagnostics, and reverse engineering servers. Discover how agents can now run diagnostics, decompile malware, and even query applications—all via chat.

This first edition curates in-depth, hype-free AI insights for engineers, from the pitfalls of multi-agent systems to the rise of AI-powered browsers. Expect contrarian takes, practical engineering tips, and real-world case studies over fleeting trends.

Tomek Lelek and I wrote Vibe Engineering because we kept seeing the same mistake everywhere: teams confusing the speed of generation with the speed of delivery. Vibe coding, that intuition-first, prompt-driven mode where you accept what the AI gives you without deep verification, is genuinely valuable. It's the digital sketchpad. It's how you turn a foggy idea into a working interface in an afternoon. I use it. You probably should too.

AI adoption gaps stem from a missing common vocabulary. A maturity matrix with five levels and four perspectives helps organizations honestly assess where they truly stand.

This is post #4 in The Agent-Ready SDLC series. In post #1 we laid out the Ferrari-in-a-Fiat-500 problem - the engine is great, the chassis isn't. In post #2 we covered the first bottleneck: context. In post #3 we covered the second: feedback loops. Now we're at the third piece - and it's the one nobody wants to talk about.

This is post #3 in The Agent-Ready SDLC series. In post #1 we laid out the Ferrari-in-a-Fiat-500 problem - the engine is great, the chassis isn't. In post #2 we covered the first bottleneck: context. Now we're at the second bottleneck - the one that sits between your agent and reality.

Open any README in your repository. That flagship one. The one that's 800 lines long with a "Getting Started" section written in 2022. Read it with fresh eyes - as if you were a new developer, or better yet - as an AI agent who's never been to a standup, never seen Slack, never heard the legend of why we don't touch the InvoiceReconciler class in the payment service. Now ask yourself one question: based on this README, can you safely modify anything in this service?

You've probably heard about the first METR study from July 2025 - it made the rounds at every conference and every newsletter. 16 experienced open-source developers, a proper randomized controlled trial (not a vendor survey), and the result: 19% slower with AI. In this article, Artur argues that the problem lies in the environment, not the model. Read on to find out exactly.

Welcome to GitHub All-Stars, our biweekly series where we pick a trending or freshly minted open-source project and put it under the microscope. We focus on new, relatively unknown gems - not another breakdown of the latest React release (because let's be honest, the world has enough of those). This time, we're looking at a project that lives at an unusual intersection of prepper culture, self-hosting enthusiasm, and edge computing philosophy. And it just exploded on Hacker News.

What if the biggest blocker to AI-driven development isn’t the AI itself but everything around it? Artur Skowroński, our Head of Application Development, talks about the most common issues enterprises have stumbled upon over the last few years, and how VirtusLab is working to remove them. This is a sneak peek into VISDOM: a platform designed for a world where AI produces massive amounts of code, and organizations need a way to truly understand, trust, and manage it. Read on to discover how it all comes together.

This is GitHub All-Stars - a series about open-source gems that deserve a closer look, before they become tomorrow's mainstream. Today, we're looking at a project that tackles what is arguably the most expensive waste in the entire AI-assisted coding workflow: context window abuse.

This post is about the practical challenges of getting GPU-targeting code tested in environments without GPU hardware - specifically GitHub Actions. The project behind it uses Project Babylon / HAT (an experimental OpenJDK fork that compiles Java to GPU kernels), but the lessons apply to anyone doing OpenCL, CUDA, or heterogeneous compute work in CI.

Today's project dropped on Hacker News frontpage just days ago and instantly sparked one of the most interesting security discussions I've seen in a while. We're looking at Matchlock by Jingkai He - a CLI tool for running AI agents in ephemeral microVMs with network allowlisting and secret injection via MITM proxy. Built to answer a question that every developer running claude --dangerously-skip-permissions should be asking: "What's the worst that could happen?"

In this series, every other Wednesday, I pick one trending repo and take it apart piece by piece. This week, I pulled out one key component of the entire GasTown engine, the thing without which the agents are basically useless. That component is Beads.

Every other Wednesday we pick one trending project and break it down into its core pieces. Not another React framework or even an agent framework - but something fresh, something that helps us understand where our industry is heading. Today’s pick: BloopAI/vibe-kanban. A tool written in Rust that tries to bring order to the chaos of working with coding agents.

I've always claimed there's no better way to learn anything than to build something with your own hands... and the second best way is to do a Code Review of someone else's code. Today, we are taking on a project that made waves on Twitter (or X) and GitHub, not so much because of the complexity of the code, but because of the philosophy behind it, and above all, because of its author, Andrej Karpathy. And in this article, we'll discuss his AI consensus mechanism called llm-council.

Every other Wednesday, we’ll pick one trending repository from the previous week and give it some focused attention by preparing a tutorial, article, or code review – learning from its creators in the process. Today, we’re taking a look at a project that tackles one of the most embarrassing yet universal problems in our industry: f/git-rewrite-commits.

In our “GitHub All-Stars” series, we take “new or little-known” open-source gems that solve real engineering problems and put them under the microscope. Today, we’re looking at toon —a tool that directly tackles the financial and performance overhead of data serialization in the age of AI.

This week, we’re diving into a project that tackles one of the most fundamental problems in the world of science and engineering: the frustrating gap between the theory described in a research paper and its practical implementation. Anyone who’s ever tried to reproduce results from a paper knows the pain. The code, if it’s even available, is often a tangled mess of one-off scripts and Jupyter notebooks - making reproducibility, the cornerstone of science, more of an art than a craft.

This newsletter is a monthly, noise-free roundup of AI developments that truly matter to engineers and tech leaders — practical, skeptical, and ready for implementation. Instead of chasing every new model or “top 50 tools” list, we focus on what will stand the test of time and genuinely change how we build software. This month, we’re diving into agents — a concept that’s finally moving beyond experimentation and maturing into a true engineering discipline.

There is a fundamental gap in understanding our own productivity, for those who feel an inner need to close it, creates an opportunity for Dayflow - a project that aims to redefine how we perceive and analyze our screen time - for the good or the bad. Dayflow is not yet another time tracker - it’s an ambitious attempt to build a “semantic timeline,” or, to use the project’s own metaphor, “a git log for your day”.

In this article, we’ll break spec-kit project down to its core components. We’ll explore its philosophy, architecture, and the powerful engineering patterns behind it to understand how GitHub is transforming chaotic “vibe coding” into a structured software development process.

In this edition of GitHub All-Stars, we look at a key building block of agentic applications - UI- and how Human-in-the-Loop can be implemented in practice. Let’s be honest: despite the marketing, no agent solution is perfect, and there will always be moments when we, the protein-based organisms, are needed. That’s why any application that aims to solve the problem realistically has to face this challenge head-on.

Every Wednesday, we’ll pick one trending repository from the previous week and give it attention, preparing a tutorial, article, or code review—learning from its creators along the way. Today, we’re taking a fresh project from Google engineers to the bench: Google/langextract.

Every morning, I scan Hacker News, newsletters, research, and weird corners of the web before preschool drop-off. I collect the gems that don’t make the headlines but teach useful lessons or spark technical ideas. Now I’m sharing them here. My rules are simple: no chasing every new model, no “top 50” lists, and no breathless marketing. Read on for this edition’s hand-picked stories and lessons. If that sounds like your kind of newsletter, welcome to issue two.

As part of our GitHub All-Stars series, where we examine open-source gems, I stumbled upon a project that strikes at the heart of one of the most fundamental problems in modern AI. After analyzing deepagents and its system-level approach to reasoning, the natural next step was to examine how we solve the problem… of memory.

I’ve always claimed there’s no better way to learn anything than by building something yourself… and the second-best way is reviewing someone else’s code. From now on, every Wednesday we’ll pick one trending repo from the previous week and give it some attention: a tutorial, an article, or a code review - learning directly from its authors.

Java has come a long way on ARM. Runtime improvements, smarter garbage collectors, and better vector performance now make it a solid fit. CI/CD pipelines work without extra effort. This guide walks through: - real-world benchmarks - examples from AWS and Google Cloud - gives hands-on advice for tooling, deployment, and compatibility If you're weighing cost, speed, or sustainability, this will help you judge whether a move to ARM makes sense—and how to pull it off cleanly.
