George Marmaridis

Ever thought shareReplay in RxJS is your go-to solution for caching emissions and reuse? Think again! 😬 While it can be a handy tool, it comes with its own set of pitfalls that might lead our reactive journey astray. 🚦 Here's where shareReplay can trip you up: when you use it without understanding its cache behavior. It caches emissions indefinitely by default, which can lead to unexpected memory leaks and retain obsolete data. The result? Your app’s performance might take a hit, especially in long-lived applications. Consider this scenario: ```javascript import { Observable } from 'rxjs'; import { shareReplay } from 'rxjs/operators'; const source$ = new Observable(observer => { observer.next(Math.random()); }).pipe( shareReplay(1) // Beware! Cached indefinitely! ); source$.subscribe(val => console.log('Subscriber One: ', val)); source$.subscribe(val => console.log('Subscriber Two: ', val)); ``` In the code above, shareReplay is caching the same numerical value even though it appears to be recalculated. While this works fine in simple usages, imagine how much stale or memory-intensive data your application could hold onto in a complex environment. Have you encountered any surprising behaviors with shareReplay? How did you mitigate the pitfalls of indefinite caching? Let's share our experiences below! 👇 #RxJS #shareReplayPitfalls #ReactiveProgramming #JavaScript #WebDevelopment

1

🚀 Freelance vs Full-time Software Development in Germany - When to choose what In Germany's technology market, both freelance developers and permanent employees play important roles. The right choice depends on your business needs. ✅ Freelancers are the better choice when ⚡You need very specific expertise for a clearly defined project or technology stack ⚡Speed is important, since freelancers can usually start quickly without long hiring processes ⚡Your workload is project-based and does not justify a permanent hire ⚡You want flexibility to scale teams up or down without long-term obligations 👩‍💻 Permanent employees are the better choice when ⚡You want to build long-term product knowledge and strong company culture ⚡Continuity in core systems is essential ⚡The role requires deep integration with the business and its processes In short: 👉 Choose a freelancer for focus, speed, and flexibility 👉 Choose a permanent employee for stability, culture, and continuity The value lies in knowing which model fits your current challenge. #Freelance #SoftwareDevelopment #TechHiring #ITFreelance

38

What is Unidirectional Data Flow? In the iOS world, we’ve been hearing a lot about unidirectional data flow lately. Sounds very technical, but the concept is actually pretty familiar in everyday life. Imagine you’re ordering a coffee: • You say “Latte” → that’s the action • The barista processes your request → logic/reducer • The coffee gets prepared → state is updated • The drink is served → UI renders The important part: the process only goes one way. After you get your coffee, you don’t throw the cup back and say “also make it a cappuccino!” :) The flow always follows the same direction. Apps work the same way: → user triggers something → business logic handles it → state changes → UI updates This makes the system: ✓ more predictable ✓ easier to test ✓ less error-prone ✓ easier to scale That’s why frameworks like SwiftUI, TCA, Redux, React and Elm are built on unidirectional data flow. Especially in large codebases, you really want to avoid the “who changed this state?” mystery. #iOSDevelopment #Swift #SwiftUI #TCA #TheComposableArchitecture #UnidirectionalDataFlow #StateManagement #FunctionalProgramming #ReactiveProgramming #SoftwareArchitecture #MobileEngineering #TechLeadership #ScalableSystems

4

🚀 Two days before WhatTheStack kicks off, I’m running a crash course in building apps that survive the real world. Real-World React: The Architectural Playbook for Performance, Resilience & Scalability is built around React and Next.js as our shared language, but it’s not exclusive. I’ve had Vue, Svelte, and Angular devs attend, and most of the concepts we’ll cover are framework-agnostic and apply to any modern frontend stack. We’ll dig into: - Architecture patterns that implicitly boost performance - The real story behind React reconciliation (and anti-patterns to avoid) - Resilience engineering for modern frontends - DORA metrics and delivery velocity at scale - Building post-deployment confidence so you can ship without fear This isn’t about pixel-perfect UIs, it’s about patterns, decisions, and trade-offs that keep apps fast, resilient, and scalable when they’re serving millions, not just running locally. 🎯 If you work in frontend and want to level up your architecture game, this is for you.

5

CSS Advent Calendar - Day 9 – Container Queries Container Queries are the feature we missed for years. With them, components become truly independent – no longer oriented to the viewport, but to their own context. This fundamentally changes the architecture of frontends. Responsive design becomes more local, modular, and scalable. Container Queries are not just another feature. They are a turning point. #CSS-Advent-Calendar #CSS #Web-Development https://lnkd.in/e_dZU97d

1

1 Comment

My key lessons learned from 𝐀𝐦𝐚𝐳𝐨𝐧 @ AWS Summit in Hamburg 🗒️ 👥 𝐓𝐫𝐞𝐚𝐭 𝐞𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐬 𝐚𝐬 𝐜𝐥𝐢𝐞𝐧𝐭𝐬 Listen to what they need, remove friction, and give them tools that make their lives easier. Happy engineers build better systems. 🛠️ 𝐓𝐞𝐚𝐦 𝐚𝐮𝐭𝐨𝐧𝐨𝐦𝐲 & 𝐨𝐰𝐧𝐞𝐫𝐬𝐡𝐢𝐩 – Amazon teams choose their own tech and design approaches. What matters is performance and clear API contracts with other squads. ♻️  𝐑𝐞𝐮𝐬𝐞 𝐰𝐡𝐚𝐭’𝐬 𝐚𝐥𝐫𝐞𝐚𝐝𝐲 𝐭𝐡𝐞𝐫𝐞 – Don’t write boilerplate for common needs. All services require monitoring, patching, etc. — no need to reinvent the wheel every time. 📦 𝐎𝐧𝐞-𝐛𝐨𝐱 𝐝𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭  New versions are first deployed to a single instance to catch issues early. Goal: minimize impact on users if something goes wrong. #AWS #Engineering #SoftwareEngineering

56

2 Comments

API Documentation Lessons from Munich. Attended a very good talk at API Days Munich by Birgit B. and Jens Fischer from OTTO. The familiar problem: Sprint nearly done, features coded, then suddenly everyone's asking questions about the API. Unclear structure, inconsistent naming, feedback coming too late in the process. Their approach: Treat API specs as the first user interface, not documentation debt. Results: Less rework, fewer support tickets, faster adoption. Teams actually collaborated instead of throwing specs over the fence. The reality check moment: One of the speakers shared: "I poured my heart into this spec so users could understand it, and now I'm asked to merge it as-is just to unblock a deployment? That hurts." This hit home. How often do we rush deployments at the expense of actually usable APIs? The line that stuck: "If it's hard to explain, it's probably hard to use." Anyone else dealing with API doc chaos? How are you handling it? #APIDesign #TechWriting #APIDocs #DevEx #APIArchitecture #APIDays #Munich

6

2 Comments

My Legacy Code survey is still open, and some early patterns are emerging: → 62% define legacy by "technology that's no longer actively developed", not by age → Most common argument that convinced business to modernize? 75% because of "security incident" More data = better insights. Link the the survey https://lnkd.in/d8VeSsVK

3

⏰ LESS THAN 2 WEEKS LEFT: 1-2 IT companies in Vienna needed for Burnout Prevention Pilot Deadline: November 11th, 2025 Your best developers aren't leaving because of better offers. They're leaving because they're exhausted. As a former Agile coach who worked in IT teams for years, I watched high performers burn out not from lack of skills, but from systems that weren't built to sustain them. I'm launching a heavily discounted pilot (70-80% off) to prove what's possible when companies prioritize people alongside performance. This pilot is designed for IT teams that are either: ✅ Underperforming and need to rebuild momentum ✅ High-performing but showing early burnout warning signs What You'll Get: • Teams that deliver consistently without burning out • Reduced sick days and turnover—retain the talent you've invested in • Stronger psychological safety—people speak up, share ideas, stay engaged • Measurable improvements in both performance and well-being • A sustainability roadmap so results don't disappear after 2 months What I Need From You: • Access to your team for assessments and sessions • Time commitment for workshops and feedback • Leadership buy-in and willingness to implement change • Genuine commitment to improvement Why the discount? Because I'm building case studies that prove prevention works better than replacement. But I'm only taking 1-2 companies. Applications close November 11th. If you're an IT leader in Vienna ready to invest in sustainable performance, let's talk. 👉 Book your discovery call: https://lnkd.in/dbh3x-nK 🌐 Learn more: https://b-wareness.com #BurnoutPrevention #ITLeadership #Vienna #TeamWellbeing #WorkplaceWellness #Bwareness

3

Just shared a new Medium article: Clean Code Design Principles : DRY, KISS, YAGNI https://lnkd.in/dBWZd2ej I’ve been writing software for over 10 years now, and if there’s one thing I’ve learned, it’s that clean code isn’t just about elegance it’s about survival. Through countless projects, late-night debugging sessions, and team collaborations, three principles have stood the test of time for me: DRY, KISS, and YAGNI. These aren’t just trendy acronyms they’re the kind of habits that make your code readable, maintainable, and actually enjoyable to work with.

19

* My Experience with PREEVision in BCM Development * Recently, I had the opportunity to use PREEVision by VECTOR Informatik for Body Control Module (BCM) development — covering the journey from System Engineering ➝ Software Engineering. Working hands-on with the tool gave me some clear insights into its strengths and limitations. ✅ Pros: End-to-end modeling support (Requirements, Functions, SW, HW, Wiring, Diagnostics) Strong AUTOSAR Classic & Adaptive integration Centralized database → consistency across teams and domains Good for large-scale collaboration in E/E architecture projects. ⚠️ Cons: High learning curve for beginners. Performance can be challenging with very large models. 💡 Takeaway: PREEVision is a powerful tool for managing complex E/E architectures like BCMs. When used with the right methodology, it greatly improves traceability, consistency, and collaboration. But it also demands training, discipline, and process maturity to get the best value. I think it is best tool to OEMs for maintain the overall Vehicle Architecture. Thank You Verolt, SAGAR ANTURKAR for this great opportunity. Still Exploring more into PREEVision.

51

1 Comment