Dmytro Z.

🚀 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 Comments

Ready to learn some practical DSP? If so, we invite you to join us for tomorrow's The Audio Programmer Meetup! We will be joined by Musik Hack Co-Founder Sam Fischmann. Sam has had great success with well known plugins such as Master Plan and Fuel. We will be talking about useful DSP. Including... ✅ Filter basics, frequency and phase, not just frequency! ✅ Filters, when to use (IIR/FIR/linear/minimum phase/biquad forms/svf) ✅ Filter shapes, when to use (bessel, butterworth, chebychev 1+2 , elliptical/cauer/Linkwitz Riley/clamping) ✅ Filter implications for null tests and parallel processing ✅ Oversampling + aliasing ✅ Desmos for testing and comparing saturation techniques ✅ Saturation myths: Harmonic and inharmonic distortion ✅ Basic compressor/limiter design This will be a great conversation for anyone who is seeking to gain an overall understanding of how DSP algorithms work, and how to use them. Tune in here: https://lnkd.in/e9wxeA9h

57

8 Comments

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

I hope that this encourages organizations to explore inviting programmers into a more participatory role in developing the entire product. I worry that less-experienced programmers will become stuck in these "paid to write good-enough code" jobs and never develop the skill and interest in taking a greater role in product development. Meantime, the programmers who can do this well will all die or, like Justin here, grow tired of the industry, then quit. Not everyone who writes software wants to become a product-oriented entrepreneur. For example: I don't.

21

3 Comments

Together with Erik-Jan Westendorp, we developed a modular extension for Umbraco 16+ that enhances Umbraco Forms cleanly and flexibly. The idea was simple: make forms more powerful without making them more complex. By keeping everything modular, you can enable only what you need and extend it further when required. What the extension helps with: - Extending Umbraco Forms without touching core functionality - Adding reusable, modular building blocks for form logic - Keeping implementations maintainable and future-proof - Making it easier for teams to adapt forms to project-specific needs This kind of work comes from our shared passion for Umbraco and the opportunity at ilionx to apply that knowledge in real client solutions. Curious about the technical details and the thinking behind this approach? Read more here: https://lnkd.in/eTFs_Tvm

25

The amount of knowledge this guy possesses is nothing short of crazy 🔥 If you're a Kotlin dev, you must expand your horizons by moving to Kotlin Multiplatform, and learning to interact with native platforms (like iOS, macOS, Windows, etc) is a critical part of that. Check out Shreyansh's blog to learn more 🚀 #kotlin #jetbrains #programming #multiplatform #crossplatform #kmp #java #interop #c++ #c #jni #jna #ffm

7

The tech sector needs to stop eating its own tail on this. You need junior devs and it's not optional. AI in the hands of a non-programmer is as of yet incapable of producing enterprise level software.

2

Hey, fellow engineers. Does anyone here actually write Contract Tests? Here is the talk about Contract Testing of Websockets, which I made back in 2018 at the Nordic APIs in Stockholm. And back then, it was a hot topic; I was not even the only one speaking about it at the same event. But what I observed within the years since then, while working with different projects, is that this type of testing is still a luxury that not everyone can afford. Do you write Contract Tests with Pact or any other similar software in your company? Btw. the link to the full talk is in the first comment. #testing #QA #unittests #websockets #API

17

6 Comments

🚀 After wanting to do this for MONTHS... I finally hit publish Just published an article giving a clear, practical overview of performance optimizations ⚡️ Not overly academic. Not unnecessarily deep. But the kind of foundation every frontend engineer should understand. I talk about: ⚡️Why apps feel slow 🧠 What actually causes unnecessary re-renders 🔍Where performance bottlenecks usually hide 🛠 Simple optimizations that make a real difference Performance has always been something I care deeply about. There's something satisfying about turning a laggy experience into something that feels instant. This is just the start. 1'1l be sharing more as I continue learning and building. If you're building with React/ React Native, this might be useful👀 #reactjs #reactnative #webdevelopment #mobiledevelopment #developer #poojachawla #cross_platform

2

I’ve been at Pleo for about 8 months now, and one thing that stands out for me is how well our teams deal with maintaining and fixing problems in the system together. In a lot of places, when deadlines slip or something breaks, people go quiet and try to stay under the radar. No one wants to be the one to say “this isn’t working” or “we need help.” At Pleo we use incident.io for incident management, and I‘m still impressed how well the process works. If something’s too big for a smaller group to solve, you can escalate it, and people jump in trying to help. There’s no culture of blame. Just smart, kind engineers who share the load and work together to solve tricky issues. Seeing how difficult some of these problems are and how it sometimes takes days of the best engineers’ brain work to untangle them, I’m not really scared that AI will take these jobs. For me, real software engineering lies here — in the messy, collaborative, human part. Debugging a system you might not have written, but need to maintain. Asking good questions. Disagreeing respectfully. Knowing when to push and when to step back. Using the experience and knowledge of things you have learnt over the years. AI can help, but it doesn’t replace the judgment, trust, and shared ownership that makes engineering teams actually work.

108

5 Comments

Developers don’t become leaders by accident. When I first stepped into leadership, nobody handed me a playbook. I had to piece it together by watching the managers around me — the great ones, the average ones, and the ones who taught me exactly what not to do. That’s when it hit me: the skills that got me here weren’t the skills that would help me succeed next. I had to learn how to: – communicate with clarity – influence without authority – set direction instead of diving into the code – coach instead of fix – deliver outcomes through a team, not through my own keyboard. None of that was obvious at the start. But once you see the shift, you can’t unsee it. If you’re a developer stepping into leadership, you’re not alone — and you don’t have to figure it out the hard way as I did. What have you had to figure out as a manager?

9