Magnus Krona

🚀 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

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

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

🚀 New Release: gulp-jmkcoder-msbuild v0.2.2 I’m excited to announce the availability of gulp-jmkcoder-msbuild, a modernized Gulp plugin that streamlines MSBuild integration for developers. 🔧 What’s new? Support for the newly released MSBuild 18 Graceful fallback to earlier versions (from 1.0 through 17.0) Simplified configuration — just specify the version, and the plugin resolves the right path automatically Designed for CI/CD pipelines and developer productivity tooling This release continues the mission of making build automation developer-friendly, resilient, and future-proof. Whether you’re working with legacy .NET Framework projects or the latest Visual Studio builds, gulp-jmkcoder-msbuild ensures your workflow stays consistent. 👉 Available now on npm: npm install --save-dev gulp-jmkcoder-msbuild 📖 Learn more: https://lnkd.in/etZ4Ws9e #gulp #gulpmsbuild #msbuild

5

🚀 Why E2E Testing with Playwright Matters I was recently testing our “Create Fixed Shift Template” feature, and I ran into a tricky issue. Even though certain items were clearly visible on the UI, Playwright sometimes couldn’t detect them, causing the test to fail. At first, it was puzzling everything looked fine to the eye, but the assertions kept breaking. 💡 What was going on? After reviewing the CI/CD test video recordings carefully and paying attention to minor details, I realized the problem was UI lag when rendering a large number of shifts at once. In production, users usually have fewer shifts, so this never happens there. ⚡ How I solved it: I implemented a pagination and virtualization so that only the visible items are rendered at a time. The results were immediate: 1. Tests became stable. ✅ 2. UI performance improved. ⚡ 3. Users got a smooth and responsive experience, which also builds trust in the system. 💪 ✅ Takeaways: 1. E2E tests catch issues that unit tests often miss. 2. Virtualizing large lists and rendering only visible items boosts the user trust, while keeping the app fast. E2E testing isn’t just about catching bugs it’s about ensuring your users have a smooth, consistent, and trustworthy experience every time they interact with your product. #Playwright #E2ETesting #ReactJS #UserExperience #CodingBestPractices

19

5 kommentarer

What happens when your Vaadin component needs to go beyond what the server-driven model offers — but you really don't want to write JavaScript? You write Java for the browser instead. In the new blog post, Matti Tahvonen explores four different approaches to running Java directly in the browser and integrating them with Vaadin Flow: 🟦 GWT (the classic source-to-JS transpiler), 🟦 TeaVM (bytecode-to-JS/WASM), 🟦 CheerpJ (a full JVM running in the browser), 🟦 and the experimental GraalVM-to-WebAssembly pipeline shipping with GraalVM 25. To make the comparison concrete, Matti rebuilt a Tetris game with each approach — same game logic in Java, same Vaadin Flow wrapper, four very different toolchains. The result is a practical look at how each one handles artifact size, startup time, code reuse, JS interoperability, and developer experience. The takeaway isn't that you should abandon Vaadin's server-side model. It's that when you need to push specific components or views to the client — for offline support, reduced latency, or less server traffic — you now have real options to do it without leaving Java. All four implementations, including the demo app and source code, are available to try. Read the full comparison 👇 https://lnkd.in/d9rkZTAn #Java #Vaadin #WebDevelopment #WebAssembly

37

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

🚨 MAUI Assembly Linker Frustration 🚨 If you’re working with .NET MAUI, chances are you’ve already wrestled with the assembly linker. Sometimes it just breaks overnight—without any changes in code—especially on Android builds. The result? A flood of unexpected exceptions, right when you’re trying to generate a release APK. 😤 What’s even more frustrating is how fragile it feels… but here’s the catch: 👉 The simplest “fix” is often just rebuilding the entire project. Suddenly, the errors vanish as if nothing ever happened. While that workaround helps, it raises a bigger concern: the linker in MAUI still feels unreliable and inconsistent, which can be a real headache during production builds. I hope Microsoft puts more focus on stabilizing this, because MAUI is a powerful framework—but issues like this can block developer confidence. Have you faced similar linker nightmares in your MAUI projects? What’s your go-to workaround? #dotnetMAUI #Xamarin #Android #AppDevelopment #DeveloperExperience

1

Day 1 – Understanding the Cascade Many frontend teams underestimate how much time they could save by better understanding the CSS Cascade. The Cascade is not just a set of rules, but the core mechanism that determines how browsers make decisions. Those who understand how Importance, Origin, and Specificity interact write CSS that is more consistent, predictable, and resilient in the long run. The Cascade is not an opponent to be outsmarted – it is a system to work with. Solid CSS starts not with frameworks or tools, but with understanding these foundations. #CSS-Advent-Calendar #CSS #Web-Development https://lnkd.in/ePCBq6Us

7

GraalVM: The Technical Deep-Dive Post Let's dive into a truly groundbreaking use case for GraalVM that is often overlooked: native mobile development. While many see GraalVM as a backend powerhouse, its Ahead-of-Time (AOT) Native Image compilation, in tandem with frameworks like JavaFX and Gluon, offers a direct path to creating high-performance, multi-platform mobile apps. Here's how this powerful synergy works: Write Once, Compile for Many: You develop your application logic in Java/JavaFX, leveraging a mature, robust language ecosystem. AOT Compilation: The native-image tool compiles your entire application, including the JavaFX UI, into a single, platform-specific executable for iOS or Android. This process eliminates the runtime JVM, resulting in a binary that starts instantly and consumes minimal resources. Deploy as a Native App: The final output is a true native app that can be distributed on the App Store and Google Play, delivering the performance and user experience expected from a native application. While challenges like handling dynamic language features (e.g., reflection) exist, the benefits of improved performance and resource efficiency make this a compelling solution for certain mobile development scenarios. It’s a sophisticated approach that combines the best of Java's rich ecosystem with the raw performance of native code. This is a testament to GraalVM's versatility and its potential to redefine application development across the entire stack. #GraalVM #NativeImage #MobileDevelopment #Java #JavaFX #Gluon #SoftwareArchitecture #TechTrends

1

New nuget project. LLM Mock API, a little ASP.NET Core Middleware which lets you mock API endpoints and get it to simulate data using a local LLM (ollama). https://lnkd.in/emsJaj2J - Super Simple: Addmostlylucid.mockllmapi() + Mapmostlylucid.mockllmapi("/api/mock") = instant mock API - Configurable: appsettings.json or inline configuration - Shape Control: Specify exact JSON structure via header, query param, or request body - Real-time Streaming: Server-Sent Events (SSE) support with progressive JSON generation - Highly Variable Data: Each request generates completely different realistic data - All HTTP Methods: Supports GET, POST, PUT, DELETE, PATCH -Wildcard Routing: Any path under your chosen endpoint works For example by just adding: // Add LLMock API services with configuration from appsettings.json builder.Services.AddLLMockApi(builder.Configuration); var app = builder.Build(); // Map LLMock API endpoints at /api/mock app.MapLLMockApi("/api/mock", includeStreaming: true); You can invent an endpoint to get mock data. ### STREAM: POST with shape via header POST {{LLMApi_HostAddress}}/api/mock/stream/orders X-Response-Shape: {"orderId":"string","status":"string","items":[{"sku":"string","qty":0}]} Content-Type: application/json Accept: text/event-stream { "customerId": "cus_789", "items": [ { "sku": "SKU-42", "qty": 3 } ] } Will give you a stream of random but plausible data which meets the JSON (but even in there you can be descriptive about what the element should be). #aspnet

1

Functional JavaScript handles pressure. Yesterday at Functional Programming Sweden , I showed how Functional JS handles data shape, change, and flow to build predictable, scalable architectures — live. https://lnkd.in/dMMapGvS The real enemy in JS isn’t performance — it’s uncontrolled change

1

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

New episode: Mattias Karlsson on Cake Build—escaping YAML chaos for C# clarity 🎯 This conversation explored Cake (C# Make), a build orchestration framework offering an alternative to traditional YAML-based build pipelines. The key insight: using a strongly-typed language like C# for build definition provides greater clarity, debuggability, and consistency. 𝗪𝗵𝗮𝘁 𝗖𝗮𝗸𝗲 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗱𝗼𝗲𝘀: It doesn't replace MSBuild, the .NET CLI, or your CI/CD system. It orchestrates them, simplifying complex workflows and offering a more developer-friendly experience. You write workflows in C# instead of YAML, PowerShell, or Bash. Cross-platform, works identically on Mac, Windows, Linux, or in containers 💭 𝗧𝗵𝗲 𝗱𝗲𝗯𝘂𝗴𝗴𝗶𝗻𝗴 𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲 𝘁𝗵𝗮𝘁 𝗰𝗵𝗮𝗻𝗴𝗲𝘀 𝗲𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴: Unlike YAML pipelines requiring push-to-runner cycles to identify issues, Cake allows loading scripts into Visual Studio or Code, setting breakpoints, and stepping through the build process locally. This dramatically speeds up development and troubleshooting. Test everything locally before pushing. 𝗣𝗹𝗮𝘁𝗳𝗼𝗿𝗺 𝗮𝗯𝘀𝘁𝗿𝗮𝗰𝘁𝗶𝗼𝗻𝘀 𝗵𝗮𝗻𝗱𝗹𝗲 𝗰𝗼𝗺𝗽𝗹𝗲𝘅𝗶𝘁𝘆: Cake handles file path differences between Windows and Linux. Forward slash versus backslash? Handled. Environment variable separators? Handled. Path construction that works everywhere? Handled. You write once, run anywhere. The heavy lifting for cross-platform compatibility is done for you. 𝗦𝘁𝗿𝗼𝗻𝗴𝗹𝘆-𝘁𝘆𝗽𝗲𝗱 𝗺𝗲𝗮𝗻𝘀 𝗰𝗼𝗺𝗽𝗶𝗹𝗲𝗿-𝘃𝗲𝗿𝗶𝗳𝗶𝗲𝗱: Fully typed classes for tool arguments. You don't need to remember if parameters are integers or strings. You don't need to memorise which arguments can be combined. If it compiles, it runs. The compiler catches errors before you push. 𝗧𝗵𝗲 𝗖𝗮𝗸𝗲 𝗦𝗗𝗞 𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲: Introduced in November 2025, Cake SDK enables single-file executables, smooth .NET ecosystem integration, and leverages .NET 10's file-based applications. Full Visual Studio Code support out of the box. Works with C# Dev Kit. Publish as containers, .NET tools, or platform-specific executables. Mattias on the learning curve: "Start with something really simple and then evolve. You don't need to replace everything at once." Available now: https://lnkd.in/ek45HzT3 #DotNet #DevOps #BuildAutomation

2

⭐ Book Review: Learn Model Context Protocol with TypeScript by Christoffer Noring “Learn Model Context Protocol with TypeScript” is one of the most practical and forward-looking technical guides available today for developers building AI-powered applications. Christoffer Noring does an exceptional job explaining why MCP (Model Context Protocol) matters, how it evolved, and how it solves real engineering challenges in modern AI systems. The book starts by grounding the reader in the historical background and purpose of MCP, clearly showing why standardized context, structured tool integration, and safe capability execution are essential for today’s LLM-driven applications. From there, it transitions into a deep but accessible breakdown of the MCP architecture, protocol design, hosts, servers, clients, capabilities, and communication layers (STDIO & SSE). The real value shines in the hands-on chapters: Building and testing STDIO servers, including resource and tool development Implementing real-time SSE servers for streaming interactions Streamable HTTP techniques to scale MCP servers for web and cloud consumption Clean architecture patterns for production-ready server design Developing bespoke clients/agents, including LLM-integrated clients Consuming MCP servers through IDEs like Claude Desktop and VS Code The advanced chapters elevate this book beyond a basic tutorial. Topics such as elicitation techniques, sampling strategies, secure communication, authentication/authorization, and production deployment help readers understand how to design robust, scalable, and safe AI workflows — not just prototypes. By the end, the reader gains a complete mental model of MCP and a practical blueprint for building enterprise-strength AI systems that are maintainable, modular, and secure. Some areas could be strengthened with more end-to-end real-world examples and architectural diagrams to tie concepts together. More guidance on common pitfalls, debugging, and error handling would benefit beginners. TypeScript best practices around MCP patterns could be expanded further. And while production topics are covered, deeper deployment examples would make the book even more practical. Verdict: This is a must-read for AI engineers, TypeScript developers, and architects who want to build reliable, extensible, and future-proof agent-based systems. Christoffer delivers both conceptual clarity and hands-on implementation detail — making this one of the strongest resources available for developers working with MCP today. Thanks to Anamika Singh getting this on my radar! Thanks #packt# for this book 😀 #ModelContextProtocol #MCP #TypeScript #AIEngineering #AIDevelopment #LLMTools #AgentDevelopment #StreamingAPIs #Claude #OpenAI #SoftwareArchitecture #AIWorkflowDesign #ServerDevelopment #TechLeadership #AIStandards #ChristofferNoring #BookReview #Developers #LearningJourney #ModernAI #FutureOfDevelopment

11

A simple practice, big impact. Martin Nilsson recently shared a great idea: Let developers be the first line of test. Before merging code, a colleague spends just five minutes manually testing and reviewing. That tiny step can: - Catch obvious bugs early - Free up testers for more complex challenges - Improve collaboration and knowledge sharing The result? Stronger code, better teamwork, and higher quality. Curious how this works in practice? 👉 Read the full blog post here: https://lnkd.in/dS8Spx6r

19

4 kommentarer