Zoltan Kochan

Our PHP Team Lead, Volodymyr Vovnenko, recently raised a question about long-running processes and orchestration in FinTech systems. Within one of our PHP + Symfony projects, our engineering team started evaluating Temporal.io as a way to orchestrate long-running workflows (KYC/AML, payout confirmations, PSP callbacks) with stronger guarantees, better traceability, and a clearer execution flow. Today, our architecture relies on a classic event-driven approach: — Outbox pattern — persisting events in DB and publishing them to a broker — Event choreography — services reacting to each other’s events — Retries & DLQ — handling failures and delayed recoveries While this approach works, it becomes increasingly difficult to maintain transparency, traceability, and guaranteed execution in workflows that may run for hours or even days. Temporal.io, in contrast, offers several potential benefits: — Orchestration instead of choreography — clearer control, versioning, and less event chaos — Built-in retries, timers, and deadlines for long-running processes — Execution history out of the box — always knowing where a workflow got stuck — Native SAGA pattern support with compensation logic We’re curious to hear from the community: 👉 Have you used Temporal.io for orchestration in PHP/Symfony or other ecosystems, and what challenges and results have you seen in production? #PHP #Symfony #Temporal #Saga #Orchestration #FinTech

11

🚀 New Series Alert: Global IT Salary Deep Dives! We are kicking off a brand-new series of articles exploring exactly what tech professionals are earning around the world. To start things off, we are focusing on the .NET ecosystem. Location plays a massive role in compensation, but how does your local market stack up against the global competition? We’ve broken down the data to show what .NET professionals are earning by country. Whether you are looking to relocate, negotiate a raise, or hire top talent, these insights are crucial. 👇 Read the first article in the series here: https://lnkd.in/dWPqbS7s #DotNet #DeveloperSalary #TechSeries #SoftwareEngineering #GlobalTech #Optiveum #Recruitment

8

When developers meet Testers -Developers: it should fit perfectly, the logic is correct 😏 -Testers keep proving that the real world doesn't always follow the same logic🧐 At the end of the day -Developers build solutions -Testers make sure these solutions actually works as expected. This funny video shows exactly that.

5

So you want to run an Eastern European software development agency? Let me tell you what’s changed. Eastern Europe has long been home to excellent engineers, trained in solid higher education systems. In Serbia, my home country, we have great software talent. To meet Western companies’ demand for affordable developers, outsourcing and nearshoring consultancies have flourished here over the past two decades. Business was booming, especially after Covid-19 normalized remote work. Some countries even subsidized employment. But subsidies are fading, and new policies are reshaping the industry. For years, we counted on the U.S. remaining open to service imports. Yet even before the latest administration, shifts were underway. Before 2022, U.S. businesses could immediately deduct R&D costs, giving quick tax relief. From 2022, the TCJA required domestic R&D to be amortized over 5 years, and foreign R&D over 15. This hit cash flow hard. Many think the mass tech layoffs of 2022–23 were due to over-employment, but tax changes played a bigger role. Companies, even at peak profits, couldn’t expense engineers’ wages as before so they decided to lay off. That uncertainty rippled worldwide. Rising interest rates and AI hype only worsened the mood. Then with the new U.S. administration came even bigger changes. First came tariffs, which weakened USD, CAD, and AUD against the EUR. With most of expenses pegged to EUR, agencies working for U.S. clients saw revenues shrink by more than 10% YTD. Then came the “One Big Beautiful Bill Act.” It restored immediate expensing for domestic R&D starting 2025 but kept foreign R&D amortization rules. The administration also introduced a tax on H1B visas to slow talent inflows. Indian outsourcing firms, which relied on sending engineers onsite, will be hit harder than European firms, due to timezones. But that shift may push Indian companies to target Western Europe more aggressively, driving prices down and competition up. Finally, looming over everything is the proposed HIRE Act, which would slap a 25% tax on outsourced services that benefit U.S. consumers. And that cost is non-deductible as expenses. The mother of all outsourcing killers. It still needs to pass both houses of the Congress and hopefully it will not. But ironically, Serbia already has a similar withholding tax on foreign services and licenses (Google, Slack, etc.). The U.S. has just started playing the same protectionism game others have long played. We just weren’t used to it, since our businesses were built on U.S. openness and dollar demand. So, is the situation grim? Yes. But business always adapts. To survive, Eastern European agencies must pivot. Three key paths stand out: - Deliver the highest quality work and the clients will pay if the value is clear. - Shift more focus to domestic and European markets. - Gradually transition into building own products, not just delivering services. Do I see all the angles? What is your take on this?

107

11 Yorum

How do you stay consistent without losing your spark? ✨ Lenka Pejchalová, one of our QA teammates, shares a glimpse into her daily flow. Spoiler: being “too organized” at work might be her secret superpower. 🧠 Swipe through her micro-story and if you’re curious to see what a full day in her (QA) life looks like, read the full article on our blog 👉 https://lnkd.in/eRZD-DnB

11

🧪 Testing is not just about finding bugs, it's about building trust. In this video, our Testing Managers Alexandra Rau and our testing automation engineer Sebastian Ira break down some of the most common questions about software testing strategies, from misconceptions to method. They answer: 1️⃣ What’s the biggest misconception about software testing? 2️⃣ Why is it important to have a defined testing strategy? 3️⃣ What is the biggest risk of not having one? 4️⃣ How do we tailor our approach to each project or client? 5️⃣ How do we strike the right balance between automated and manual testing? At POLYGONS, testing isn’t an afterthought, it’s part of building smarter, safer, and more sustainable systems. Watch the full video to hear their insights, and get a peek into how we make quality a core part of everything we deliver. 👉 Curious how we test the future? Follow us for more stories behind the code. #SoftwareTesting #QualityAssurance #TestingStrategy #AIoT #TechLeadership #TeamCulture #WeArePOLYGONS #DigitalTransformation #SoftwareDevelopment #WomenInTech #TestingMatters

32

3 Yorum

🧩 The Real Cost of Bad Documentation in Software Projects In software development, bad documentation isn’t just a small problem; it quietly costs time and money. Poor documentation leads to slower onboarding, more debugging, unclear communication, and delayed projects. At Sparkle Web, we have seen how clear and well-structured documentation improves teamwork, makes maintenance easier, and saves costs in the long run. 💡 Remember: even the best code is useless if no one understands it. Let’s build systems that are not only functional but easy to understand and scale. 👉 Continue reading: https://lnkd.in/d7pjrjyd #sparkleweb #softwaredevelopment #codequality #documentationmatters #techculture #softwareengineering #codereview #webdevelopment #mern #dotnet #flutterdevelopment #cleancode #projectmanagement #knowledgesharing

1

50+ features in production. Nobody knows what's core business. Nobody knows what's actually important. Look, this isn't legacy hell. It's a lack of map. Reading "Learning DDD" by Vlad Khononov on the beach. One DDD concept that works even without full adoption. Subdomain Types: - Core Domain (business value, where you make money) - Supporting Subdomain (helps core, but not core) - Generic Subdomain (auth, logging, utils) Use AI to classify what you have. Specifically: 1. List your main folders/modules 2. Feed to AI (Claude/GPT with long context) 3. Ask: "Which parts are core domain? Supporting? Generic?" 4. Make a map. Excel works. Why? - Know where refactor has highest ROI (core) - Know what to remove (duplicates in generic) - Know what to outsource (generic = libraries) TBH, I'm learning DDD myself. This is a theory I want to test. Will share how it goes. Anyone tried this? What happened?

10

It is super awesome to see the push towards the zero-cost abstractions in .NET. We all know about spans, but there specifically designed for high performance and require the code changes to migrate to them. But now, due to de-abstraction feature in .NET 10 we can eliminate all the overhead in the existing cases. For instance, if you have Enumerable.Any with a delegate that captures instance state, the runtime can stack-alloc it, and (if it's small) to inline it. This will achieve the performance of a manual code that obtains span out of a list and "inlines" the delegate logic into the loop itself! More info on that? Here: https://lnkd.in/ejpa3546 And as always, thanks for sharing this post!

45

🚀 ToughTech continues at Toughlex! This time, we welcome 🌍Šarūnas Kavaliauskas, Software Architect, with his talk “Domain Driven Design in Code.” If you’ve ever been unsure what DDD really means - or how it helps you write better, more maintainable code - this session is for you. Šarūnas will share how to stop modeling by habit and instead start from domain rules to shape aggregates, boundaries, and behavior. 💡 Walk away with a practical, repeatable approach to turn messy requirements into clear models and simpler, more reliable systems. #ToughTech #Toughlex #DomainDrivenDesign #SoftwareArchitecture #Engineering

35

3 Yorum

Writing unit tests is easy. Writing meaningful ones is not. That’s why this topic matters for developers at any stage and on any project. Our colleague Petar Kanev, .NET Engineer, shares one of the most important things every developer should know about unit testing. It’s a detail that often gets overlooked — and one that matters more than it seems. What else do you think a .NET developer should know in 2026? #DotNet #UnitTesting

5

🌀 What’s really happening in .NET today? We’re not talking hype. This is hands-on insight from someone who just migrated a production project to .NET 8. We spoke with Yahor Halubchyk, a senior .NET engineer at Vention, to get a grounded take on current trends, migrations, and what’s worth paying attention to. ⚙️ .NET 8 has become the default. It’s stable, fast, and LTS-backed. Upgrading from earlier versions is usually a matter of days. As for .NET 9 — most teams are skipping it and waiting for 10, which promises smart memory handling and auto-optimizations for collections and performance. 🧱 Still on .NET Framework? Brace yourself. If your project’s on modern .NET (formerly Core), migration is straightforward. But if you're stuck on .NET Framework 4.8, you're likely looking at a full rewrite. The architecture is different, and most libraries just won’t work out of the box. 🧩 Third-party libraries are the real bottleneck. Yahor put it simply: “If you're on the standard Microsoft stack, migration is smooth. But if you’re using MongoDB, niche ORMs, or older open-source packages, expect to dig through source code and open GitHub issues.” 📉 Blazor and Razor? Still niche. They’re rarely used in production. React and Angular dominate the frontend. Blazor might work in edge cases, like when sensitive business logic has to stay server-side, but it’s not the go-to. 🤖 AI + .NET: not just buzz — it’s useful. GitHub Copilot struggles with complex logic. But GPT-4? Surprisingly solid. Yahor’s team uses it to generate SQL queries, unit tests, and advanced search logic, especially when given proper context. 🧠 .NET itself? It’s more than a language — it’s an engineering mindset. Think architecture, optimization, concurrency. The learning curve is steep, but so are the opportunities. As Yahor puts it: “If you have real experience, you can jump straight into a project and deliver. For juniors, we offer solid growth.” 📌 We're hiring: 🔹 Senior .NET Developer — https://lnkd.in/digGyN3s 🔹 Intern .NET — https://lnkd.in/dqAM8NPQ

25

Unlocking Industrial AI Together 🚀 Great insights from our partner Spyrosoft on the future of Edge AI and embedded intelligence. At Qt Group, we see the same momentum across the industrial space: manufacturers are accelerating their AI adoption, but they need reliable, scalable, and secure software foundations to make it real. That’s exactly where the Qt + Spyrosoft partnership delivers value. Together, we help industrial companies: 🧠 Operationalize Industrial AI from prototype to production ⚙️ Build high‑performance embedded systems with modern UX and real‑time capabilities 🔗 Integrate AI seamlessly into existing architectures—from edge devices to cloud ecosystems 🔒 Ensure safety, maintainability, and long‑term support, which are critical in industrial environments Whether it’s advanced robotics, smart machines, or next‑generation HMIs, our combined expertise enables customers to innovate faster while reducing risk. Proud to see this collaboration driving real impact in Industrial Automation. Thanks to the Spyrosoft team for pushing the ecosystem forward! #IndustrialAI #EdgeAI #QtForDeviceCreation #EmbeddedSystems #SmartManufacturing #Robotics

4

If you’re getting started with Java, it’s easy to feel overwhelmed by versions, frameworks, endless tutorials, and different applications.💻 Mihai Zanfir, Java Engineer at Coherent Solutions, shares what actually matters when learning Java for real-world projects. 👇Swipe through for practical guidance #java #javaengineer #coherentsolutions #thecoherentway

6

The oddly ignored reality of .NET development in 2026: You're not just writing C# anymore. Instead, as a modern .NET developer, you have to be something of a Swiss Army knife. I remember working on a feature that included: - Implementing a scheduled job to populate the DB with data - Using that data in a Power BI report - Using Azure DevOps and Azure Functions to deploy the report to 100s of customers worldwide For 1 feature, I needed 4 different skills. This is what backend .NET development looks like in 2026: 1) You still need the fundamentals: - Building REST APIs that don't break under load - Writing Entity Framework queries that perform well - Understanding async/await without creating deadlocks 2) But the job has expanded into cloud architecture: - Choosing between Azure App Services, Container Apps, or Azure Functions - Designing database schemas for CosmosDB vs SQL Server - Setting up Service Bus for reliable messaging 3) DevOps isn't optional anymore: - Your CI/CD pipeline needs to deploy without manual intervention - Containerization with Docker is expected, not a nice-to-have - You're responsible for monitoring and logging 4) And security? That's on you too: - Implementing OAuth 2.0 flows correctly - Understanding Microsoft Entra ID integration - Knowing how to protect sensitive data Oh, and make sure to add a bit of AI. This shift from "code writer" to "system builder" is both wild and exciting. At college, I was googling: "How do I implement X feature?" These days, I ask AI: "What are the long-term implications of this architectural decision?" They say: When you have a hammer, everything looks like a nail. But when it comes to .NET skills: Being a Swiss Army knife developer is not optional anymore.

31

2 Yorum