Lars Nilsson

🚀 Just Published: @deathbycode/civitas-id-sweden on npm! I’m excited to share that I’ve published @deathbycode/civitas-id-sweden — a JavaScript/TypeScript package for working with Swedish personal identity numbers (personnummer) and coordination numbers. Handling Swedish IDs correctly isn’t trivial — there are validation rules, Luhn (mod10) checks, date logic, coordination number offsets, gender parsing, and formatting nuances that are easy to get wrong. This package aims to make that simple, accurate, and developer-friendly. ✅ Features • Validate Swedish personal identity and coordination numbers • Parse date of birth and gender • Built-in mod10 (Luhn) checks • TypeScript-first API • Lightweight and easy to integrate Whether you’re building fintech apps, internal tools, or identity-aware services — this package helps you confidently handle Swedish IDs with minimal fuss. 🔗 npm: https://lnkd.in/d7V-qjT7 💻 GitHub: https://lnkd.in/dZBZPrdC I’d love your feedback, issues, or contributions — let’s make this even better! 🙌 #javascript #typescript #npm #opensource #sweden #personnummer #developer

14

The only vendor properly addressing the "API Mesh" layer scenarios: - Service Provider <> Consumer - Service Provider <> Service Provider - Consumer <> Consumer So it's 100% Self-Service experience, no matter what is your role in organization. Example implementations: - Platform Mesh: https://platform-mesh.io - High Level Architecture: https://apeirora.eu - kcp: https://www.kcp.io With 100% API First approach. (no Terraform, no OpenTofu, K8s Operators used instead)

I conducted solid research on GitHub Copilot App Modernization Agent and how it can move legacy applications from .NET Framework to .NET 10+ in hours instead of weeks. At the time, it wasn’t implemented. Why? Is AI really capable of guiding us in decisions like this, or is it simply a tool? The priority was clear: we needed to make sure the business logic was working exactly as expected before changing anything at the runtime or framework level. In other words, behavior first — modernization later. After some time, we revisited the topic. We did perform the upgrade, benefited from the research outcomes, but the final decision — from both the client and project perspective — was not to fully replace the solution. Why? Was it because we still don’t fully trust that AI can replace us 100%, so we postponed that step? Once the final results were clear, our role shifted to thinking rationally. Let’s call this an important lesson for any architect or tech lead:  Not every research effort needs to turn immediately into implementation  Not every upgrade means replacement  Sometimes the best technical decision is to avoid moving faster than the business The Copilot Modernization Agent is a very powerful tool:  Clear assessments  Reviewable plans  Execution through small, incremental commits But in the end… Technology serves the decision — not the other way around. If you’re working with legacy .NET systems, the real question isn’t: "When can we upgrade?" It’s: "Is this the right time and the right goal to do it?" #DotNet #SoftwareArchitecture #TechLeadership #GitHubCopilot #LegacySystems

11

Many people tell me that ChatGPT feels different from M365 Copilot — even though it’s powered by the same underlying LLM. Some even claim it’s not the same LLM at all. Let me put it this way: I once owned a Citroën C4 with a BMW engine — the very same engine found in some BMW 3 Series models. From my own experience, I can tell you: the C4 drove very differently than a 3 Series BMW. The C4 felt much more as a comfortable family van. It’s exactly the same here. #M365Copilot is optimized for business use — and it’s not just about GDPR or data residency. It’s also about how the answers are shaped and delivered. This business-focused approach to an LLM is truly unique right now. 🚀

5

3 kommentarer

You want to build sleek, dynamic, cross-platform UIs with Qt Quick and QML, but don’t know where to start? Qt6 QML For Beginners is your practical, hands-on guide to creating beautiful apps for mobile, embedded, and desktop—even if you’ve never used Qt before. Inside, you’ll learn: ✨ Signals, slots, and property bindings ✨ Reusable custom QML components ✨ Animations states and transitions that bring your UI to life ✨ Using Qt Quick Controls for rapid prototyping ✨ Fetching and displaying web data in your apps ✨ And much more! ✅ Beginner-friendly, no prior Qt or C++ needed. ✅ Step-by-step demos to learn fast. ✅ Lifetime updates included. Thousands of developers are already using it to bring their apps to life. Ready to join them? 👉 Grab your copy: https://lnkd.in/dRBYV6r3 #Qt #QML #QtQuick #CrossPlatform #UIDesign #MobileDevelopment #EmbeddedSystems #DesktopApps #LearnToCode #SoftwareDevelopment #QtLearning

9

🎉 TMAP Turns 30! TMAP is Sogeti’s body of knowledge for Quality Engineering & Testing in IT delivery and builds on practical experience from thousands of experts. Over the last 30 years it has evolved and changed, and remains a trusted authority on QE&T. 🎬 Today Rik Marselis shares with us how it all began in 1995 ahead of the latest book ‘Amplified Quality Engineering’ – which launches next week.

79

3 kommentarer

Feature Flag Use Case: Safe A/B Testing Scenario: You built two different checkout flows and want to test which converts better. Without feature flags: - Build both versions separately - Deploy one, measure for weeks - Rebuild and deploy second version - Compare results (months later) With FlagSwift: - Deploy both versions at once - Show Version A to specific users - Show Version B to the other users - Measure in real-time - Winner becomes default in 5 seconds Real testing = real users, real data, real decisions. This is why companies like Stripe, Netflix, and Airbnb use feature flags for every major change. flagswift.com

1

Is your release cycle stuck in manual-testing quicksand? Many companies waste countless hours on repetitive regression testing, leading to slow releases and higher costs. The solution isn't just more testers it's a smarter framework. At QACORE, we don't just write scripts; we build rock-solid Test Frameworks and implement End-to-End Automation designed for scale. This ensures: ✅ Faster feedback loops ✅ Reliable, non-flaky tests ✅ True CI/CD integration The result? Quality is accelerated, not sacrificed. Stop treating testing as a roadblock and start using it as an accelerator. What's the #1 bottleneck in your current QA process? Let us know below! #TestAutomation #SDET #TestFramework #RegressionTesting #CI/CD #QACore

5

Most developers spend their time optimizing code, but the real issue often lies elsewhere. The biggest bottleneck in software development is unclear requirements not bad code. Before you start writing, make sure you can explain the problem clearly. If you can’t, don’t code it yet. A few minutes spent clarifying can save days of debugging.

27

3 kommentarer

Laerdal Medical needed more than basic ERP software. They needed a single platform built for manufacturers, one that could simplify operations across four global factories and scale with their ambitions. With IFS, they gained: 🎯End-to-end visibility across procurement, supply chain, manufacturing and finance 🎯Out of the box capabilities that reduced the need for costly customizations 🎯Flexibility to support new business models like subscriptions and rentals 🎯Greater transparency and efficiency for every user across the business See how Laerdal Medical is building a scalable, connected foundation for global growth: https://ifs.link/0Fkxir

20

As a software engineer, one sometimes has to handle localisation. Thankfully we have ISO-3166 and ISO-639 to help us with country- and language-codes. There is room for confusion though... sv-SE = Swedish in Sweden (quite common) se-SV = Northern Sami in El Salvador (probably not as common) 😏 

5

Second speaker for the Malmö meetup is locked. We are happy to have Emma De Silva back again, this time with security in focus. Read more below and signup at https://luma.com/0tqpue31 ---- *Think Like an Adversary: OPSEC for Laravel Developers* Brief: Most Laravel security talks stop at the code. This one goes further. Drawing from real-world corporate cybersecurity experience and formal operations security training, this talk takes developers beyond framework-level defenses and into the organizational and infrastructure thinking that determines whether a breach is a minor incident or a disaster. Whether you're a solo founder deploying your first SaaS or part of an enterprise team, these OPSEC principles protect your Laravel app where the framework can't.

4