Pamela Canchanya

🚀 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

𝗧𝗵𝗲 𝗯𝗲𝘀𝘁 𝗴𝗶𝗳𝘁 𝘆𝗼𝘂 𝗰𝗮𝗻 𝗴𝗶𝘃𝗲 𝗮 𝘀𝗽𝗲𝗮𝗸𝗲𝗿 𝗶𝘀𝗻’𝘁 𝗮𝗽𝗽𝗹𝗮𝘂𝘀𝗲, 𝗶𝘁’𝘀 𝗳𝗲𝗲𝗱𝗯𝗮𝗰𝗸. After my sessions at the International JavaScript Conference Munich, I got the feedback summary this week. Both talks scored really well: 🟩 𝗖𝗮𝗰𝗵𝗶𝗻𝗴, 𝗣𝗮𝘆𝗹𝗼𝗮𝗱𝘀, 𝗮𝗻𝗱 𝗢𝘁𝗵𝗲𝗿 𝗗𝗮𝗿𝗸 𝗔𝗿𝘁𝘀: 𝗢𝗽𝘁𝗶𝗺𝗶𝘇𝗶𝗻𝗴 𝗨𝗫 𝗶𝗻 𝗦𝘂𝗯𝗼𝗽𝘁𝗶𝗺𝗮𝗹 𝗖𝗼𝗻𝗱𝗶𝘁𝗶𝗼𝗻𝘀 • Quality: 4.67 / 5 • Knowledge: 5 / 5 • Comment: “A bit overloaded with information.” 🟦 𝗙𝗿𝗼𝗺 𝗙𝗿𝗮𝗴𝗶𝗹𝗲 𝘁𝗼 𝗙𝘂𝘁𝘂𝗿𝗲-𝗣𝗿𝗼𝗼𝗳: 𝗦𝗼𝗹𝘃𝗶𝗻𝗴 𝗪𝗲𝗯 𝗠𝗼𝗻𝗲𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 • Quality: 5 / 5 • Knowledge: 5 / 5 It’s always nice to see high numbers; it means the work, preparation, and energy paid off. But the most valuable part was that small comment: “A bit overloaded with information.” I actually love that. It’s true, I tend to pour a lot into my talks because I want people to walk away with something practical. The tradeoff is that sometimes it becomes dense. That single line says more to me than a perfect score ever could. It’s what helps me get better. Feedback like this is 𝘂𝗻𝗱𝗲𝗿𝗿𝗮𝘁𝗲𝗱. Most people don’t realize how little of it speakers actually get after a talk. You stand on stage, share your work, and often walk away without knowing what really landed and what didn’t. When someone takes 20 seconds to write one honest sentence, it gives you a mirror. It shapes your next talk, your style, your pacing, and your focus. So if you’ve ever attended a meetup, workshop, or conference talk, take that moment to leave feedback. Whether it’s praise, confusion, or critique, it all helps. And to everyone who came to my sessions in Munich, thank you. You showed up, listened, asked, challenged, and cared enough to respond. That’s what makes these communities worth being part of. #IJS #PublicSpeaking #Conferences #EngineeringCulture #Feedback #ContinuousImprovement #Learning #DeveloperCommunity

21

3 Kommentare

It is always an immense pleasure to share the stage with Giorgio Polvara. For the second consecutive year, we co-hosted a workshop at #BuildCon2025, the annual conference of the Builders team at TravelPerk. As Giorgio said, our workshop, "Keep it Clean: modern practices for frontend excellence", focused on a core principle: software architectures degrade over time, and it's our job to keep them clean. We reflected on the key lessons learned while maintaining and evolving our applications to avoid the "big ball of mud." This included exploring some counterintuitive insights we've gained, such as learning when to duplicate code and when to abstract it, or discovering alternatives to layered architecture that simplify code base splitting. These moments of shared reflection and learning, as Giorgio mentioned, are truly what help us grow stronger as a team. Thanks to everyone who joined for the great discussion! #BuildCon2025 #FrontendExcellence #SoftwareArchitecture #EngineeringLife #TravelPerk

29

The new Cluecumber report library version 3.12.0 for Cucumber json reporting is out. This release brings updated dependencies, bug fixes and fresh new features for rerun test scenarios and exception display. https://lnkd.in/evr2-nZR

10

🚀 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

⏰ 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

This is not a Spanish course. It's a survival guide for engineers working in Spanish-speaking teams. Built for: • standups • planning meetings • real pressure situations 👉 https://lnkd.in/eWDCd-tF

3

One of the biggest sources of friction in my career has been a simple question: “Who owns the requirements?” Too often, no one has a clear answer. It happens again and again — vague language, shifting expectations, and requirements that can’t actually be tested. And yet QA is still expected to validate them with confidence. How do you test the untestable? You can’t — not without assumptions. And assumptions introduce risk. This is where tension usually starts: Developers insist, “It isn’t an issue.” QA responds, “There’s no objective definition of correct.” The real problem isn’t the code. It’s the absence of clarity and ownership upstream. Quality Assurance needs more than defect tickets and deadlines. QA needs: - Autonomy to question ambiguity - Direct access to requirement owners - Clear, testable acceptance criteria - Authoritative answers when behavior is uncertain - Without those, QA becomes guesswork. With them, QA becomes risk elimination. Clarity isn’t a luxury in regulated, complex systems — it’s infrastructure.

7

2 Kommentare

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 Kommentare

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 Kommentare

After months of building in silence… it’s finally LIVE. 🚀🔥 Today I’m officially opening dotLog to the world – and no, we’re not just launching a website. We’re building a community for automation testers who learn by DOING, not just watching tutorials. 💻🧪 What is dotLog? ✨ A focused platform to learn Automation Testing with interactive labs and lessons 📚 45+ structured Selenium lessons, from setup to advanced techniques 🧪 Real “practice areas” where you write and run Selenium WebDriver code on real elements 🧩 Free practical labs that simulate real-world testing scenarios 🧠 Deep-dive blog posts on topics like Page Object Model and SOLID in test automation This is for you if you are: 🚀 A manual tester trying to break into automation 🛠️ An SDET who wants cleaner frameworks and better design 🌱 A beginner who’s tired of random, unstructured YouTube videos If you’re one of the people who love platforms like W3Schools or Manara Tech for how simple and practical they are, you’ll feel at home on dotLog. 💚📖 Start here and explore the labs, lessons, and blog 👇 🔗 https://lnkd.in/gREbJBFN If you visit, I’d love your support: ✅ Try at least one lesson or lab 💬 Comment which topic you want next (Playwright, Cypress) 💚 Like, comment, and repost so more testers can join this community 🐞 And if you find any bug, broken flow, or anything that doesn’t work as expected, please reach out to me directly so I can fix it and make dotLog even better for everyone. Your feedback is gold. 💬✨ ⚙️ And this is just the beginning… expect new pushes, improvements, and features almost every day. Stay tuned for what’s coming next. 🚀 We’re not just launching a learning platform… 🌍 We’re building a global QA community that shares knowledge, experiments together, and grows together. #dotLog #SoftwareTesting #AutomationTesting #QACommunity #Selenium #TestAutomation #SDET #LearnByDoing

148

24 Kommentare

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 Kommentar

Playwright with JavaScript vs Java/Python. What should you choose? Most people jump into Playwright with JavaScript. But the better question is: What fits your team and ecosystem? ⸻ Playwright with JavaScript / TypeScript 👉 Best when: • Frontend-heavy applications • Fast setup and execution needed • Team already comfortable with JS ✅ Advantages: • Native support (Playwright is built for JS) • Faster updates & community support • Cleaner async handling ⸻ Playwright with Java / Python 👉 Best when: • Backend-heavy systems • Existing Java/Python automation ecosystem • Team already skilled in these languages ✅ Advantages: • Easy integration with existing frameworks • Better alignment with backend teams • Reuse of utilities and infra ⸻ The mistake I see: Choosing language based on trend, not team strength and system needs. ⸻ Playwright is the tool. Language is the interface. The best choice is the one that your team can scale and maintain comfortably. <~hashtag #𝑷𝒍𝒂𝒚𝒘𝒓𝒊𝒈𝒉𝒕 hashtag #𝑻𝒆𝒔𝒕𝒊𝒏𝒈~> 𝑷𝒍𝒂𝒚𝒘𝒓𝒊𝒈𝒉𝒕 𝒘𝒊𝒕𝒉 𝑱𝒂𝒗𝒂𝑺𝒄𝒓𝒊𝒑𝒕& 𝑻𝒚𝒑𝒆𝑺𝒄𝒓𝒊𝒑𝒕 ( 𝑨𝑰 𝒊𝒏 𝑻𝒆𝒔𝒕𝒊𝒏𝒈, 𝑮𝒆𝒏𝑨𝑰, 𝑷𝒓𝒐𝒎𝒑𝒕 𝑬𝒏𝒈𝒊𝒏𝒆𝒆𝒓𝒊𝒏𝒈)—𝑻𝒓𝒂𝒊𝒏𝒊𝒏𝒈 𝑺𝒕𝒂𝒓𝒕𝒔 𝒇𝒓𝒐𝒎 13𝒕𝒉 𝑨𝒑𝒓𝒊𝒍 𝑹𝒆𝒈𝒊𝒔𝒕𝒆𝒓 𝒏𝒐𝒘 𝒕𝒐 𝒂𝒕𝒕𝒆𝒏𝒅 𝑭𝒓𝒆𝒆 𝑫𝒆𝒎𝒐: https://lnkd.in/dR3gr3-4 𝑶𝑹 𝑱𝒐𝒊𝒏 𝒕𝒉𝒆 𝑾𝒉𝒂𝒕𝒔𝑨𝒑𝒑 𝒈𝒓𝒐𝒖𝒑 𝒇𝒐𝒓 𝒕𝒉𝒆 𝒍𝒂𝒕𝒆𝒔𝒕 𝑼𝒑𝒅𝒂𝒕𝒆: https://lnkd.in/dD4rDpwZ : Follow Pavan Gaikwad for more helpful content.

2

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

This is the part of my career, where I feel like it's time to throw away my CS degree (or, perhaps, eat it). Because, Claude Code beat me 😳 At IN2 Digital Innovations GmbH, we use Java for pretty much all applications, including, cases where it might not be the best tool for the job. One of our content parsing services is the backbone of much of what we do, and while it's doing a great job, its memory consumption is far from great. Typical Java, one would say. Of course, there are JVM tweaks and dark magic tricks we could apply, but at the cost of making the service difficult to comprehend and maintain. My internal gut feeling kept telling me that using something Go for the parser would be a natural fit for a service of such a specific domain that must stay responsive despite the load we throw at it. However, rewriting it from scratch wasn't something I would dedicate a year on. This is where Claude Code entered the picture. With around two days of work, and a bit of re-prompting trial-and-error, it came up with a service that is on par with its Java counterpart in terms of features. The big gain, however, is the drop in memory consumption. While we are still performance testing it in the wild, it shows nearly 2/3 less memory consumption, and that's not even the most optimal it can get. Removing unnecessary allocations, and with the latest additions to Go, I believe we can squeeze it even further, guaranteeing high performance at a lower memory (and carbon) footprint. If you've ever wished you could replace your legacy software with a more optimal version of it, now is the time. Or you could get in touch with us! #claudecode #programming #java #golang

8

2 Kommentare

Forget hiring "rockstar engineers" one by one. That's how you build a band. Not a symphony. The German software mindset often sees risk in remote teams. It wants individual CVs, verified line by line. But a single world-class developer in isolation? They can only move as fast as their own keyboard. **Squads change the equation.** We deploy them as pre-built, autonomous units of 3-4 engineers. A Product Owner, Senior Developer, QA Specialist, and DevOps Engineer—already fluent in working together. The result isn't just additive. It's multiplicative. One squad we embedded achieved in 8 weeks what a client's internal team projected for 6 months. Their velocity wasn't 30% higher. It was 180% 𝐡𝐢𝐠𝐡𝐞𝐫. Because innovation isn't coded in solitude. It's sparked in the friction between architecture and UX, between build speed and test rigor. A squad doesn't just write software. It generates a culture of accountability, rapid learning, and continuous delivery from day one. You're not buying individual hours. You're acquiring a complete, battle-tested delivery engine. That's the venture mindset: betting on a cohesive system, not just hoping brilliant individuals will magically coalesce. Your competitor isn't hiring faster. They're deploying smarter. **Are you evaluating talent individually, or are you evaluating how talent works together?**

1