Writing one component is easy. Conditionally rendering two different ones is still not hard. But what if you face an "n" number of permutations. "n" number of different UI elements and scattered business logic? Switch statements all over the place. Might not sound scary when we write the code. What about your future self? Cognitive load fires off the roof. Maintaining your code? Onboarding new devs? Good luck. Sounds all too familiar? Let's see a possible solution how to tame complexity. How to tackle a large number (possibly infinite) of branches in a frontend codebase without losing our sanity.

A reflection on how what I've learnt about Svelte in the last few weeks fits into the context of what I've learnt in the last 30 years of software development.

Although perhaps more suited to those new to Svelte or Svelte-curious, it will hopefully also still be of interest to a wider audience.

There have been many react component patterns used over the years to facilitate the composition of frontend software.

However, React has evolved over the years especially with the introduction of hooks and context. Newer ways to do things clash with the so-called "older ones". In my talk, I want to take a relook the patterns from the perspective of a developer's needs for implementation, be it extracting logic, combining props, handling hierarchy, or inverting control of state.

Once the need is established, it is helpful to compare the new and the old patterns, if they exist, for the same goal and understand the pros and cons of each.

We love building new features, but what about the other side of frontend development? Keeping your codebase healthy, managing tech debt, and optimizing performance are just as important. How do you start deleting code, tracking the right metrics, and collaborating with other teams to keep things fast and clean?In this talk, I’ll share practical tips and stories from working on a long-standing website layered with years of web history and various technologies. If you're ready to dive into the essential work of maintaining a frontend, this one’s for you!