Stefan Miklosovic

At adaptTo() 2025, our Tooling track highlights how automation can streamline AEM operations. In this session, you'll see how the ACM Tool enables permissions and content updates as code—making repeatable tasks faster, safer, and more reliable.    Krystian Panek & Tomasz Sobczyk (VML) introduce ACM (AEM Content Manager), a powerful open-source tool designed to automate content migrations and permission management across all AEM environments. Built with modern technologies like React Spectrum and Sling jobs, ACM offers a stable, developer-friendly experience that replaces tools like Groovy Console and AECU with a unified, scriptable interface for managing large-scale tasks efficiently.    Join us at adaptTo() 👉

44

1 Comment

I'm happy to announce the initial open source release of peppol-sk — a Java library for converting Peppol e-invoices (UBL 2.1 Invoice and CreditNote) into Slovakia's Tax Data Documents (TDD) for tax reporting. This v0.1.0 release targets the Peppol SK member review TDD specification and provides ready-to-use building blocks for anyone working on Peppol integration in Slovakia: * A builder API to construct SK TDD documents from UBL invoices * JAXB-based data model for reading and writing TDD XML * Built-in Schematron validation * A set of reusable test files for verification The library is Apache 2.0 licensed, requires Java 17+, and is already available on Maven Central. As Slovakia moves forward with Peppol adoption and mandatory e-invoicing, having open source tooling available from day one lowers the barrier for Service Providers, ERP vendors, and integrators to support the Slovak TDD requirements without starting from scratch. The backing specification is the current SK TDD draft published at https://lnkd.in/dJ4M4kMe — feedback during the member review phase is welcome. GitHub: https://lnkd.in/duTeC4qY #Peppol #eInvoicing #Slovakia #OpenSource #eDelivery #TaxReporting

93

3 Comments

Many software projects become expensive not because the technology is hard, but because the problem was not clear from the start.   At Scalo, we believe the real work begins before the first line of code. We spend time talking, asking questions, and trying to see the world the way our clients see it.   As Łukasz Pol, our Head of Business Development, emphasizes:  “Technology matters, but understanding matters more. We listen first, so every solution we build actually solves the right problem.”   This mindset helps us: ➡️ Avoid building features that nobody uses ➡️ Reduce rework caused by unclear expectations ➡️ Focus on outcomes, not just on delivery   If you are planning a new project or scaling an existing one, reach out to Scalo. We will help you verify the “why” before you invest in the “how”.

10

Why a Software Engineer with 6+ years of experience decided to build a "simple calculator." Years of working at companies taught me one thing: complexity is easy. Simplicity is the hardest thing to build. A while ago, while helping my wife organize her business, I went looking for a CRM. I expected to find a tool that would make her life easier. Instead, I found "cockpits." Screens overloaded with features, mandatory fields, and a steep learning curve. Even for me, a developer, it felt like a chore. For a practitioner who just wants to focus on their craft, it’s a barrier. It reminded me of an old conversation with a friend about finding a simple calculator app. He told me then: "If you can't find one, build your own." So, I did. I’m now the Product & Tech Lead at generalOne, and we’ve spent the last few months stripping away the noise to build FIVIA. FIVIA isn't a "revolutionary AI-powered enterprise suite." It’s a digital operational memory. It’s a tool for practitioners—masseurs, tutors, engineers—who need to remember what matters without spending an hour on data entry. The Strategy: Global from Day 1: Supporting 40 languages because professional clarity should be accessible to everyone. Architecture over Bloat: No corporate "features" that no one uses. Privacy First: Your data belongs to you, not the platform. I built this for my wife. I’m sharing it now because I believe every professional deserves a tool that feels as natural as a paper notebook, but with the power of modern architecture. Explore what we are building: FIVIA: https://fivia.app Our Philosophy: https://lnkd.in/dppGmWdu — Tim Rebesh, Founder of FIVIA #FIVIA #SoftwareEngineering #ProductDesign #Minimalism #BuildInPublic #generalOne #SoloFounder

25

🔛 Day 2 of MakeIT 2025 & JCON OpenBlend Slovenia 2025 is underway! We’re starting strong with Markus Kett from MicroStream and his session "Caching Unleashed: Supercharge Your Database Application." Tired of Hibernate bottlenecks and complex database tuning? Markus shares how cutting-edge caching strategies can simplify your stack and dramatically boost performance—making your Java apps faster, leaner, and ready for anything. #MakeIT2025 #JCON2025 #Java #Caching #Performance #CloudNative #DeveloperExperience

13

𝗛𝗼𝘄 𝗰𝗮𝗻 𝗰𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝘁𝗵𝗶𝗻𝗸𝗶𝗻𝗴 𝘀𝗵𝗮𝗽𝗲 𝗔𝗜-𝗲𝗻𝗵𝗮𝗻𝗰𝗲𝗱 𝘁𝗲𝘀𝘁𝗶𝗻𝗴? Michal Buczko gives us a sneak peek in his upcoming talk “𝗖𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝗧𝗵𝗶𝗻𝗸𝗶𝗻𝗴 𝗥𝘂𝗹𝗲𝘀 𝗶𝗻 𝗔𝗜-𝗘𝗻𝗵𝗮𝗻𝗰𝗲𝗱 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗧𝗲𝘀𝘁𝗶𝗻𝗴” at ISTC 2025! As an expert in software quality, Michał will share how to blend critical thinking with AI tools to improve testing precision and decision-making. This session is a game-changer for testers aiming to navigate the complexities of AI-driven workflows with confidence. Check out Michał’s short video to discover why this talk is a must-attend, and join us on 𝗠𝗮𝘆 𝟮𝟭-𝟮𝟮 𝗮𝘁 𝗘𝗹𝗶𝘁𝗲 𝗪𝗼𝗿𝗹𝗱 𝗚𝗿𝗮𝗻𝗱 𝗜𝘀𝘁𝗮𝗻𝗯𝘂𝗹 𝗞𝘂𝗰𝘂𝗸𝘆𝗮𝗹ı 𝗛𝗼𝘁𝗲𝗹 to experience it live! 𝗧𝗶𝗰𝗸𝗲𝘁𝘀 𝗮𝗿𝗲 𝘀𝗲𝗹𝗹𝗶𝗻𝗴 𝗼𝘂𝘁 𝗳𝗮𝘀𝘁—𝘀𝗲𝗰𝘂𝗿𝗲 𝘆𝗼𝘂𝗿𝘀 𝘁𝗼𝗱𝗮𝘆: https://lnkd.in/dW3SifX2 #ISTC2025 #SoftwareTesting #AIinTesting #CriticalThinking

14

70% faster automated testing. Smarter instruments. Stronger security with ZAP automation. Find out how Pavel Petkov, Senior Software Developer, and Andrey Mitev, Principal Developer, deliver real results with smart software solutions for a leading British high-tech instrument manufacturer. #AmdarisBulgaria #SoftwareEngineering #TestAutomation #ZAP #TechExcellence

75

🚀 New IntelliJ IDEA 2025.1.3 Release is Live! The latest update from JetBrains brings key performance and stability improvements to IntelliJ IDEA, making your development workflow even smoother. 🔧 What's new in 2025.1.3? Fixes for key bugs and regressions Enhanced IDE responsiveness Improved Gradle and Kotlin support General UI/UX refinements As a proud JetBrains distributor, we at Aquion are excited to share this with our developer community. Keep your tools updated to take full advantage of the latest enhancements! 📥 Reach out to quotes@aquion.com.au for more information! #JetBrains #IntelliJIDEA #SoftwareDevelopment #DeveloperTools #Aquion

1

💡 Just getting started with programming? Or maybe you’ve been coding for a while and want to solidify your basics? Wojciech Korona - Software Engineer at Playbook Engineering - shares 15 essential tips for beginner programmers. From debugging and clean code to learning fundamentals and leveraging community, these are the practices that truly matter in real-world coding. 👉 Swipe through the slides below and share your own tips in the comments! #TipsForBeginners #SoftwareEngineering #EngineeringCulture #TechCareers #PlaybookEngineering #LifeAtPlaybook

11

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

Last week we hosted the Android Budapest group’s September meetup with two interesting talks about Compose Hot Reload and WebView-related security risks. The first talk on Compose Hot Reload by Márton Braun included both a presentation and a live demo of the feature itself. It is not an easy task to convince Android developers that such a feature can exist without serious bugs. Google has already tried to ship this functionality twice in Android Studio, but most developers turned it off because it often caused unexpected bugs that magically went away once the feature was disabled. This time the feature is coming from JetBrains, who are known for delivering exceptional developer tooling. This is also the case with Compose Hot Reload. The Hot Reload window is very transparent about when code reloads are happening and if any errors are preventing reload. The number of successful reloads is always visible, along with the logs generated by the Gradle tasks involved during recompilation and clear error messages. This level of transparency about the whole process gives us confidence that we can trust the tool to work correctly. And when it does, it can really be a productivity boost rather than an annoyance. The second talk by Balázs Gerlei covered a completely different topic, going back to the ancient world of Views with a discussion on WebViews. WebViews are often the go-to solution when something needs to be added to an app that already exists on the web. It seems to be an okay solution, especially for screens that are less mission-critical like terms and conditions, FAQ pages, or similar static content. Adding a default WebView that opens a specific URL seems like an innocent task, but as Balázs’s talk highlighted, it already comes with its own risks. If the content also requires JavaScript, then a whole other world of exploits becomes possible. Takeaway: If you really need to open a website in your app, use a Custom Tab to do so, or secure your WebView as much as possible; just like Balázs’s SecureWebView library does out of the box.

24

On Tuesday I gave a presentation about Rediscovering Legacy Code at Java Forum Nord. We had so much fun in the Q&A afterwards that we went quite a bit overtime. The hardest question was "I want to fix it but how do I change my project/team/department?" Let's try to answer that. How do I change a team? I like to adapt the model from Atomic Habits, a book about personal improvement. It introduces the four laws of behavior change: 1. (cue) Make it obvious. Explicitly define what the new habits should be.  2. (craving) Make it attractive. Reduce (time) pressure. Stack habits together. Define that you will only "Do (Implement a feature), after I have done (10min of refactoring)". 3. (response) Make it easy. Learn the skills, perhaps from a coach. Reduce/eliminate the blockers of the new habit. If you don't have a good test example, create one. If classes are untestable, change them. 4. (reward) Make it satisfying. Provide immediate reward. Keep a (refactoring/bug) score. Increases the chance that the behavior will be repeated. You can use these laws of behavior change on yourself first. Especially "make it easy." If you can turn something hard into something easy, you now have enough of a foundation to change the team with "Fearless Change". The book introduces a set of patterns to introduce new ideas. * Personal Touch: "To convince people of the value in a new idea, show how it can be personally useful and valuable to them" > Maybe the most important one. * Early Adopter: "Win the support of the people who can be opinion leaders for the new idea." > This can be someone experienced who is generally open to new ideas. * External Validation: "To increase the credibility of the new idea, bring in information from sources external to the organization." > Show what the benefit of the change is. * Champion Skeptic: "Ask for Help from strong opinion leaders, who are skeptical of your new idea, to play the role of 'official skeptic.' Use their comments to improve your effort, even if you don’t change their minds" > Useful later, when you have early adopters already.  * Corridor Politics: "Informally work on decision makers and key influencers before an important vote to make sure they fully understand the consequences of the decision." > Do not bring up controversial ideas in big team meetings. Warm opinion leaders to the idea beforehand, address their criticism and they will come to your aid in the meeting.  * Trial Run: "When the team is not willing to commit to the new idea, suggest that they experiment with it for a short period and study the results."

17

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

Great practical advice for anyone starting with Java 👇 Mihai Zanfir shares what really matters when learning Java for real-world projects — beyond versions, frameworks, tutorials, and applications.

1

🌀 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