meet.js Wrocław 2026-05-12

DATA/DATE: May 12th / 12 maja 2026

GODZINA/HOUR: 17:30

MIEJSCE/VENUE: Klubokawiarnia Mleczarnia, ul. Włodkowica 5, Wrocław (poziom -1)

WSTĘP/ENTRY: wolny/free

JĘZYK/LANGUAGE: event prowadzony będzie po polsku i po angielsku / the event will be conducted in Polish and English

Już 12-go maja, we wtorek, w kultowej wrocławskiej Mleczarni odbędzie się kolejny meetJS Wrocław, tym razem we współpracy z MasterBorn!

Ramowa agenda:

• 17:30 - warm-up
• 18:00 - intro
• ~18:10 - Artur Wojnar - Software Architecture: The Bad Parts
• ~18:55 - przerwa na piwo/beer / kawę/coffee / herbatę/tea
• ~19:10 - ​Szymon Biduła - The same team yet different: how JS stack is powerfully adaptive in AI world
• ~19:55 - przerwa na piwo/beer / kawę/coffee / herbatę/tea
• do ostatniego uczestnika - networking / integracja :)

---

Artur Wojnar - Software Architecture: The Bad Parts

Description
In this talk, I will demonstrate how so-called good practices combined with a shallow understanding of the domain can create a dangerous illusion of control.
Using a real-world example from the Connected Health domain—specifically, liver cancer risk alerting—I will show how a noun-driven design approach leads to excessive coupling and brittle systems.
The talk will explore common architectural pitfalls such as context violations, database coupling, domain leakage, and mixing read and write models. I will also challenge a popular industry belief by explaining why Clean/Hexagonal Architecture is not an architecture.
Attendees will leave with a clearer understanding of how design decisions shape system behavior—and how easily “best practices” can fail when the domain is misunderstood.
The talk is based on this article.
I’ll be presenting the Miro board and Visual Studio Code. Tech stack is NodeJS/TypeScript/PostgreSQL.

Bio
A software engineer with 15 years of experience, currently working as a hands-on Solutions Architect and consultant, helping development teams deliver better products. He focuses on collaboratively designing solutions with clients—evaluating ideas, assessing risks, and translating them into technical requirements aligned with business goals.

---

​Szymon Biduła - The same team yet different: how JS stack is powerfully adaptive in AI world

Abstract
There is a saying that you should be careful what you wish for. We are a unicorn FinTech startup, 4+ years in production, processing $200M+ USD. As we grew 50% year-over-year, NodeJS was our engine - a stack notorious for its philosophy of freedom and anarchy.
But we started to pay the bill. Weekly post-mortems, 16% of workload for bug fixing, and another 20% for research, if the feature is even possible. The dream was becoming a maintenance nightmare.
Then, we started a side project: same domain, same people, but accelerated with AI. We found we could deliver fast and keep NPS positive. By applying principles from the side gig, the main project recovered.
The lesson? A solid JS core can be cloned and boosted by AI in ways other stacks (like Ruby) struggled to match. This is a testimony to JavaScript’s power to adapt to radically different environments.

About me
So old that remembering when going to the cloud and being agile was the hot thing. In my youth I have been scanning brains using fMRI, then I switched to creating applications for portfolio managers dealing with multi-billion portfolios. Currently, architecting Fintech solutions for US-based clients. Privately, a fan of Star Trek and vinyl collector.