Kacper R.

Just listened to Michal Ostruszka on "Better Software Design" podcast discussing event delivery patterns, and one insight really hit home: Most developers (myself included) jump straight to complex messaging patterns because they're "cool" or "trending." It's hard to say cool, without thinking distributed systems. Apparently, here's the crash course in messaging reality: ❌ "The network is reliable" (it's not) ❌ "Messages always arrive in order" (they don't) ❌ "One message = one delivery" (prepare for duplicates) The pragmatic approach:  1. Start with Fire & Forget + monitoring 2. Add complexity only when manual intervention becomes unmanageable 3. Choose patterns based on business impact, not technical coolness Before implementing that shiny new Outbox pattern, it's worth to ask: "Will this failure happen once a year or once a minute?". 🎧 Worth a listen: https://lnkd.in/dt9fcJbE

6

1 komentarz

The dark side of Domain-Driven Design: When architectural purity becomes a liability Imagine this scenario: A team starts with a simple user registration feature. Six months later, they have 37 classes to create a user account. Six DTOs for name, email, and password. A domain event system that publishes events nobody consumes. They followed every DDD pattern in the book. They created aggregates for entities with no invariants. They built repositories with specification patterns for simple CRUD. Event sourcing for data that never changed. The result? A codebase so complex that adding a new field requires touching 12 files. Unit tests that take 3 minutes to start. New developers who spend their first week just trying to understand where business logic lives. This is what happens when DDD is followed dogmatically. --- THE PRAGMATIC APPROACH I've written a guide on doing DDD without the bloat, drawing from patterns I've observed across the industry. The core principle: Architecture serves the code, not the other way around. Here's the decision framework: ✅ Use DDD when: - Complex business rules with multiple workflow paths - Long-term projects (2+ years) with evolving requirements   - Multiple teams contributing to the same codebase ❌ Don't use DDD when: - Simple CRUD with no complex rules - Rapid prototypes or MVPs - Team is unfamiliar with the patterns --- START SIMPLE, EVOLVE AS NEEDED Don't architect for year 3 on day 1: Phase 1: Transaction Script (Weeks 1-4) Phase 2: Anemic Domain Model (Months 2-3) Phase 3: Rich Domain Model (Months 4-6) Phase 4: Full DDD (Year 1+, only if needed) Your domain layer should have zero dependencies on frameworks. No Spring. No JPA. No HTTP. Just pure business logic. Dependencies flow inward: Presentation → Application → Domain           ↑ Infrastructure ─────┘ --- KNOW WHEN TO SIMPLIFY The best engineers aren't the ones who apply every pattern. They're the ones who know which patterns to skip. Red flags of over-engineering: - Aggregates protecting nothing but trivial state changes - Use cases that do nothing but delegate to repositories - "Simple" changes require touching 5+ files I've compiled everything into a comprehensive guide covering migration strategies, testing approaches, common pitfalls, and practical Java 25 examples. The goal isn't architectural purity. It's building software that bends without breaking. "Good architecture allows you to change your mind without changing the world." Stop building cathedrals for vanity. Build houses people can actually live in. 🔗 Read the full guide: https://lnkd.in/dZndu-Ax

2

Test automation redefined 💥 Our Polish .NET team — Bartosz Fijałkowski, Michał Kłos, Rafał Kaczka and Piotr Wachowski — has built a brand-new feature for Wynxx: the Functional Tester UI. It turns natural-language gherkin test scenarios into fully executable code within seconds. Powered by AI agents and integrated with the MCP server, it delivers real-time diagnostics, automatic test generation, and a direct translation of manual test cases into working playwright or cypress. It’s another great example of how local GFT engineering teams drive global innovation – from an idea born in client meetings to a production-ready solution used worldwide.   Read the full story 👇 🔗 https://lnkd.in/dFYFV_Jj #GFT #Wynxx #AI #Automation #Innovation #SoftwareDevelopment #DotNet #Testing

23

1 komentarz

Yesterday I had a pleasure to talk at Xebia about evolutionary architecture - how to build for today but also not to close doors for tomorrow 🙌

14

.NET engineers – not sure where to focus next? Here’s a practical take based on our current projects and new client demand.   I spoke with Evgeny Kapylski, who leads the .NET group at Vention Poland, to break down the patterns we see across our work.   Watch the video to understand what will keep you competitive in the next 6 months 👇

36

We often talk about "instant" performance, but the numbers tell a different story. I spent yesterday evening at the Node.js Warsaw XXIII meetup. Great vibes (and snacks!) 🍕 , but the standout was the talk by Mattias Hansson on system latency. He used a brilliant visualization: if a CPU cycle is as fast as a blink of an eye, the difference between reading data from a local SSD versus fetching it from the Cloud is staggering. It’s easy to forget the sheer scale of that gap when you're just looking at lines of code. The key takeaway? During work with high level IT technologies, we’re used to everything feeling "instant." But true optimization happens when you respect the physical reality of hardware. Sending a single bit to the Cloud involves a relatively astronomical delay when compared to a local database read—to say nothing of the CPU-Memory cycle. It was a solid reality check on why smart caching and minimizing external round-trips are still the kings of performance. Great talk, and see you on next MeetUps! 👏 #NodeJS #WarsawNodeJS

20

2 komentarze

From “What if?” to “Here’s how” A few months ago, our team at Intetics asked ourselves: How can we help innovators move faster from idea to execution? The answer: WearArchitex I recorded a brief demo so you can see how simple it actually is: 1️⃣ Click the link in this post 2️⃣ Type your IoT or wearable concept 3️⃣ Add your email 4️⃣ Hit “Generate Report” Voila! In just 5 minutes, get a complete architecture - diagrams, traceability, and tech stack recommendations. As simple as that - give it a try → https://lnkd.in/gqN6Q8Cb #Wearables #IoTSolutions #SmartOperations

20

1 komentarz

Hey Friends and Tech Enthusiasts! 👋 We’re excited to invite you to a free and practical webinar hosted by Adiuvo in collaboration with our awesome partners from SoDA, the largest software development association in Poland. 🔍 Topic: Real-World Go Refactoring: Lessons Learned 📅 Don’t miss this deep dive into real use cases, insights, and live Q&A!   What’s on the agenda? ✅ When, why, and how to refactor real-life projects ✅ Case Studies:  🔹 Rewriting a large-scale Java app in Go  🔹 Migrating from Python to Go in a fast-growing startup ✅ Key statistics and decision-making tips ✅ Interactive Q&A – bring your questions!   👥 Who should join? This is open to everyone - developers, architects, CTOs, and anyone curious about Go, software architecture, or backend scalability.   📌 Register here: 👉 https://lnkd.in/d3JqMnRF Just complete the registration, and you’ll receive the access link to the webinar directly via email. Let’s learn and grow together. See you there! 🙌

5

💡 Most IT projects don’t fail because of poor code. They fail because they’re not really needed. 🚀 At the Solution Designer Meetup on 18 November in Warsaw, I’ll share my top tips on how to: 🧭 Focus on solving the right problem, not designing the dream solution ⚙️ Build MVPs that can actually go live and scale 👥 Create products that people genuinely need and use 📚 Apply lessons learned from real projects Together with other experts, we’ll share stories, best practices, and lessons learned - the wins, the misses, and the things we wish we’d known sooner. If you’re into building solutions that truly make an impact, come join us! 🙌 👉 https://lnkd.in/dV8CEmym #SolutionDesign #TechTalk #ProductDesign #Innovation #WarsawMeetup

65

1 komentarz

Our Head of Development, Andrzej Wysoczanski, has just released the Effective Delivery newsletter #7. It’s about how much time engineers waste on tasks that don’t bring business value. Some common traps they fall into include: ☕ Unproductive meetings 📚 Useless documentation ⚒️ Overengineering 💯 Perfectionism Check out the new release!

4

1 komentarz

Sanity and Contentful share the same goal: easier content management. But they get there in very different ways 🏎️ Jakub Dakowicz explains what separates them and why those differences count. 🎥 Watch the full video in the comments.

1

1 komentarz

Two years ago, together with my colleagues Sebastian Dąbkowski, Wojciech Kasa, Artur Kruszewski, I made one of the best professional decisions in my career. We decided to participate in the O'Reilly Architectural Kata organized by Mark Richards and Neal Ford. It was not just another competition. It was a real battlefield for architects. A space where ideas are challenged, trade-offs are exposed, and your thinking is tested under pressure. 🏆 And yes, we won :) Being selected by a jury composed of experienced practitioners and respected voices in the architecture community (Jacqui Read, Diana Montalion, Sergey Zinchenko, Andrew Harmel Law) and made that moment even more special. 🙏 But the real value was not the trophy. It was the exercise itself. Architectural thinking is not something you gain from reading books alone. It is a skill. And like every skill, it requires practice. Architectural Kata forces you to • make decisions with incomplete information • defend trade-offs • articulate quality attributes • think in systems, not components • communicate clearly under time pressure If you want to grow as an architect, you have to practice thinking architecturally. Exercises like Kata are one of the best ways to do it. Architecture is not a title. It is a muscle. And muscles need training. 💪

34

3 komentarze

🌍 𝗧𝗵𝗲 𝗥𝗶𝘀𝗲 𝗼𝗳 𝗚𝗿𝗲𝗲𝗻 𝗜𝗧: 𝗪𝗵𝘆 𝗜𝘁’𝘀 𝗠𝗼𝗿𝗲 𝗧𝗵𝗮𝗻 𝗮 𝗧𝗿𝗲𝗻𝗱 As technology leaders, we often talk about speed, scalability, and innovation. But there’s another “S” we need to prioritize: sustainability. At 𝗠𝗮𝗶𝗻𝘀𝗼𝗳𝘁, where our teams of Polish software engineers help global clients build the future, we’ve seen firsthand how IT can be both a driver of progress and a significant consumer of energy and resources. This is why the rise of 𝗚𝗿𝗲𝗲𝗻 𝗜𝗧 matters — not as a buzzword, but as a responsibility. Green IT is about more than energy-efficient servers or paperless offices. It’s a mindset — designing, coding, and deploying technology that minimizes waste, optimizes performance, and contributes to a cleaner planet. When we develop smarter systems, we can: ✅ Reduce energy consumption through optimized software and cloud solutions ✅ Support clients in adopting sustainable architectures and scalable infrastructure ✅ Use AI and automation to improve efficiency and cut unnecessary resource use ✅ Extend the lifecycle of hardware through responsible procurement and recycling Poland’s tech community has a tremendous opportunity here. With our engineering talent, we can lead the shift toward sustainable innovation — building solutions that are not only powerful, but purposeful. Because the future of IT isn’t just faster. It’s 𝗴𝗿𝗲𝗲𝗻𝗲𝗿. #GreenIT #Sustainability #TechForGood #SoftwareDevelopment #Outsourcing #PolandTech #Innovation

11

1 komentarz

Last Thursday I had the chance to speak at the Engineering Leaders Community meetup in Prague. Three speakers, great energy, and a very honest discussion about engineering leadership. My topic was simple: why hiring leaders doesn’t scale and how we can spot and grow leadership talent inside engineering teams, even in lean organizations with high complexity. I shared a few lessons from the last five years building our engineering organization, growing from 1 → 100 people in new engineering center of excellence while integrating existing teams and growing to 200+: leadership shows up in behaviour, not job titles self-awareness beats raw technical skill people need a safe space to express ideas initiative and courage matter more than perfect answers and small teams with clear ownership are the best place to discover emerging talent I was genuinely happy to hear from several attendees that my talk “hit home.” One person said it was the best talk they heard in ten years, which is both flattering and a reminder that real experiences resonate more than theory. Thanks to the organizers, Marian Kamenistak and Anna Kožuch and to everyone who joined. Always good to see that the engineering community cares about growing the next generation of leaders, not just shipping features.

51

2 komentarze

I've had quite a few people ask for slides from my recent presentation on the relationship between skills data, AI, and business strategy. So here it is. In it, you'll see screenshots from some of EPAM's internal systems illustrating a few of the many, many ways we use skills data to hire, develop, retain, and engage our global workforce. LMK if you have questions! #skillsbasedorganization #AIinHR #peopleanalytics #futureofwork

208

25 komentarzy

The discussion at the recent ASPIRE Poland Leaders Summit at Muzeum Sztuki Współczesnej w Krakowie MOCAK helped me clarify thoughts around something I believe many of us are experiencing. In the AI race, most of our focus is on #speed: automation, productivity, efficiency, acceleration. We keep building systems with more and more buttons designed to increase velocity. But in the middle of it all, there is a #humanintheloop, unnamed, undefined, yet still essential. And honestly, in many critical areas, we probably shouldn’t try to eliminate it. But the question that arises is what role are we really designing for that human? Are we actually making their work easier and freeing them to focus on more strategic thinking? Or are we just turning them into a "hamster in a wheel", running faster and faster to keep up with systems optimized for speed, not for human sustainability? Which #future are we moving toward? How much #faster can YOU run, and at whose expense? Can we really #haveitall ? #AI #Human #dajmiwszystko

46

2 komentarze

Yesterday I spoke at Devoxx Poland in #Krakow about #GarbageCollection and it was fun 😁 As always before a session I‘ve modified my slides and I was able to make it through 188 slides in 50min…that was tight and I directly reduced the number of slides again after my session. It’s really not that easy to adapt the number of slides to the available time, esp. if you will find sessions with lengths of 20, 25, 30, 40, 45, 50 and 60 minutes. I wish conferences could stick to the 45min format 🤷🏼‍♂️ The #TrashTalk tries to cover memory management, esp. garbage collection in the #Java #Virtual #Machine (#JVM). It’s not a deep dive on this topic but more an intro and overview session that should provide everything you need to know to get a better understanding about garbage collection. Once you understand the principles and know how the collectors in #OpenJDK work, you should be able to make a more educated decision when it comes to selecting the right collector for your application. Collectors are programs that have their use case and requirements. E.g. a fully concurrent collector runs (as the name implies) concurrently to your application which means it will require CPU and memory resources that won’t be available for your application. Meaning to say, you will probably see a drop in application performance when switching from a non-concurrent to a concurrent collector on the same machine (depending on the available CPU and memory). That also means, systems and their software are different and it needs monitoring + tuning to find and configure a garbage collector for your application. So my advice is…do not simply use something because someone else is using it 😁

68

2 komentarze

Why do some 1:1 meetings genuinely help engineers grow, while others feel like a routine checkbox? 💭 In our recent “Career insights” article, Iryna Kostiuk, People Partner at Pwrteams Poland, shares practical insights into how strong software engineers use 1:1s to build shared understanding, surface risks early and connect everyday work with long-term development. If you work in tech and want your 1:1s to actually move things forward, this one’s worth your time. 👉 Swipe through the slides for highlights and find the full article in the link in the comments. #PwrteamsPoland #CareerInsights #SoftwareEngineers #CareerTips #EffectiveMeetings

8

1 komentarz