QGEMS Hosts North East .NET Developers Meetup on March 24th

Thoroughly enjoyed the 'North East .NET Meet Up' this evening. I was really intrigued by Adam Parker ideas around breaking conventional wisdom surrounding Clean Architecture — stripping out many of the conventional libraries associated with typical clean architectural patterns (e.g. MediatR, FluentValidation etc.), and removing abstraction layers where possible (interfaces etc.), whilst providing evidence of performance gains through benchmarking. He also acknowledged the trade-off when deviating from established design patterns (big team/enterprise culture etc.), recognising that it’s a big ship to steer. From a personal perspective, I've been a big fan of conventional Clean Architecture for a long time as I find it to be organised, consistent, encapsulates the SOLID principles, and facilitates volatility with minimum fuss. However, I do like the idea of performance gains and opportunities to de‑obfuscate code where possible, so I look forward to exploring some of Adam’s examples in his GitHub repo. I also thought Mark Thompson talk on encryption in a post‑quantum computing world was a real eye‑opener. He definitely brought home the future risks associated with current asymmetric encryption algorithms due to the advancement of quantum computing and its capacity to potentially derive private keys from public keys in the not‑so‑distant future (i.e. within the next 5 years). Combined with ongoing “Harvest Now, Decrypt Later” activities being performed as we speak — the stowing away of encrypted data for later decryption by “who knows?” — this presents an imminent threat to data security and underpins the accelerated movement toward quantum‑proof algorithms. I thought both speakers were impressive, so well done them. Credit to Qasim Asghar for pulling everything together (and it was also great to meet you) and to QGEM for hosting and supporting. Having been largely focused in cloud development and infrastructure, security and DevSecOps governance for a while, it was nice to re-engage in some .NET dev/architectural conversation — and I can honestly say I’m very much looking forward to the next event! #dotnet #CleanArchitecture #SoftwareArchitecture #PerformanceEngineering #CodingPractices #Developers #TechCommunity #CyberSecurity #QuantumComputing #PostQuantum #Encryption

"Developers are now part of the attack surface" - by Tanya Janca Something we must talk about, definitively. Appsec meets platform engineering. https://lnkd.in/dZufD2Yz

Latency spikes are not random. They are time-aligned. And i’ve been measuring them wrong. In Day17 of the Collapse Lab, I stopped looking at how big spikes are and started looking at when they happen. Not averages. Not distributions. Temporal alignment. Instead of continuous tracing (which contaminates the system), I moved to a low-disturbance, high-resolution heartbeat model and aligned four timelines: - heartbeat spike timestamps - system phase transitions - probe start and end windows - temporal distance between events What came out was not noise. Spikes cluster. And they cluster near phase boundaries. Not during steady load. Not randomly across time. At transitions. That’s the uncomfortable part. Because in production systems, this means: Your dashboards look stable Your load tests pass Your averages are clean And then the system destabilizes exactly when state changes. Retries. Recovery. Re-initialization. That’s where the system starts to slip. Not because of load. Because of state transitions interacting with time. What this suggests (and I’m challenging this openly): If you’re not analyzing latency relative to system phases, you’re blind to the actual failure mechanism. Most monitoring stacks don’t even have the concept to express this. Open question to engineers: Have you ever seen latency spikes that: - don’t reproduce under load tests - appear random in logs - but consistently happen during recovery or transitions? Because I’m starting to think they’re not random at all. Full experiment, scripts, and raw logs here: https://lnkd.in/d4Phkbwx #SystemQA #Linux #Observability #DistributedSystems #Debugging #Performance #SRE #Backend #Engineering #ChaosEngineering #Reliability #Latency #Israel #TechIsrael

After building dozens of n8n workflows, these are the 5 nodes I use in almost every build: **1. HTTP Request** Your bridge to any API in the world. If a service has a REST API, this node connects to it. Master this and you can integrate almost anything. **2. Set** Transforms and shapes your data between steps. Rename fields, combine values, create new properties. The silent workhorse of any workflow. **3. IF** The decision-maker. Routes your workflow down different paths based on conditions. Every real automation has branching logic — this node handles it. **4. Code** When built-in nodes aren't enough, write JavaScript or Python directly. This is what separates n8n from Zapier — you can always drop into code. **5. Webhook** Makes your workflow respond to external events in real time. Instead of polling, other services push data to your n8n workflow instantly. These 5 nodes cover 80% of what you'll build. Save this post — come back when you get stuck. #n8n #Automation #Tutorial #NoCode #TechFinSpecial

The software ecosystem experienced a brief but significant breach on March 24, 2026 that went almost unnoticed, underscoring how fragile even well-established development pipelines have become. As a result of a threat actor operating under the name...

Our recent publication in the premium ACM Transactions on Software Engineering and Methodology (TOSEM): C2|Q⟩: A Robust Framework for Bridging Classical and Quantum Software Development. https://lnkd.in/dsjGcTQR This work introduces a modular and automated framework that bridges classical problem specifications with executable quantum programs, helping lower the barrier for classical developers to leverage quantum computing. This work is the result of collaborative, multidisciplinary teamwork by Boshuai Ye, Peng Liang, Matti Silveri, Teemu Pihkakoski, Muhammad Azeem Akbar, and Lauri Malmi

In 2022, I walked back to my desk at noon and noticed something small, but alarming. A simple text file—one I strictly close after every single use—was open. As an expert engineer who has worked extensively on complex telecom core systems Ericsson equipment , I knew that engineering is built on discipline. My intuition immediately kicked in. I didn’t just close the file and move on. I dove into the forensic reality: 🔍 Analysing explorer.exe activity. 🔍 Deep diving into registry keys (regedit). 🔍 Scrutinizing the system logs. The data didn’t lie: my workstation had been accessed at 12:34 PM. The hardest part wasn’t the technical breach itself. It was the "smile of betrayal" from a colleague when I realized what had happened. Manual checks were never going to be enough. I needed a "Digital Fortress." I needed to build my own solution. This is how that challenge became my catalyst: 1️⃣ Return to Fundamentals: I realized manual routines fail. I returned to the bedrock of logic and mathematics. 2️⃣ The Developer Mindset: I brushed up on Pascal and C, then dove deep into Python via Coursera. I stopped thinking like a power user and started thinking like a software architect. 3️⃣ Proactive Automation: I built my reactive findings into a proactive application designed to automate integrity checks. Today, I’m launching this tool for everyone in the community. Whether you are in Network Engineering, DevSecOps, or just want to secure your workstation, I hope this helps you stay proactive. Key Takeaway: Not everyone who challenges you is trying to stop you. Sometimes, they are just the unexpected spark you need to upgrade your life. (I’ve also shared the open-source code on GitHub for anyone looking to build upon it or audit the integrity—link in the first comment! 👇) #CyberSecurity #SystemAutomation #PowerShell #SoftwareEngineering #TechStory #Infosec #CareerGrowth #NetworkEngineering #Python #CareerGrowth #Mindset #NetDevOps #Ericsson

One of our Aliit members, Tushar Pamnani, just published something I would love every developer ecosystem leader to read 👀 Not because it's a glowing review of building on Midnight. It actually... isn't. It's honest, which is rarer, and let's be real, these days that's all the more valuable. He names the friction: no hosted proof server that also respects the privacy model, cryptic compiler error messages, a Lace wallet API he had to reverse-engineer by inspecting window objects in the browser console. These are real. They're tracked. And the fact that they're now public is useful, not embarrassing. He also names what works: engineers in the Discord engaging with real problems at 3am, an ecosystem intimate enough that good work gets noticed immediately, and a language (Compact) that forces you to actually understand zero-knowledge cryptography rather than letting you abstract over it. What strikes me most is what he built to fill the gaps: midnight-wallet-kit on npm, mn-scaffold for project scaffolding, a PR to our official create-mn-app repo upgrading the hello-world template to SDK v8, and a docs PR clarifying the CLI flow that every new builder stumbles on. He didn't wait for us to fix it. He fixed it and documented it for the next person. That's what the Aliit Fellowship is supposed to produce. People who treat the ecosystem as something they're responsible for, not just something they're consuming. If you're evaluating whether to build on Midnight, read his post first. It's the clearest picture of where we are right now, and what building here actually costs and returns. Full post here: https://lnkd.in/e7avETRZ