After interviewing many junior developers, I have learned that memorising framework trivia rarely makes the strongest impression. I explain what I look for instead: clear reasoning, curiosity, communication and an honest response when you get stuck. With common questions and advice on nerves, this is a look at interviews from the other side of the table.
A code review is a chance to learn, not an exam you have to pass. This guide helps junior developers decide what to look for, ask useful questions and give constructive feedback, including to senior colleagues. You do not need to spot every problem to make a valuable contribution.
Ten small JavaScript helpers, with examples of their inputs, outputs and limits. From removing duplicate values and delaying a task to debouncing and comparing arrays, these one-liners solve familiar problems. The point is readable, useful code: a short expression earns its place only when it makes the behaviour easier to understand.
A successful CIAM login is only part of the story. What does your frontend keep afterwards? I explain the user and transaction stores in oidc-client-ts, implement a TypeScript memory store and cover the trade-offs around redirects, reloads and SSO. In-memory tokens reduce persistence; they do not make an application immune to malicious JavaScript.
Debounce waits for a pause; throttle limits how often work can run while events keep arriving. That difference matters for search fields, scrolling and other frequent interactions. This article explains both techniques with practical use cases, helping you choose the behaviour your interface needs rather than treating them as interchangeable performance tricks.
AI makes writing code faster, but what happens to the experience developers gain by solving problems themselves? I look at how my workflow has changed and why juniors, mediors and seniors face different consequences. Greater output does not automatically mean stronger engineering judgement.
An accessibility audit can turn green while the next feature introduces the same barriers again. I explain why a round of fixes is not enough, and how design, development, content and testing must share responsibility. Accessibility needs to survive the next release, not just the audit.
Frontend tooling was supposed to help us deliver. So why do straightforward websites turn into months of work? Drawing on my experience, I challenge unnecessary frameworks, custom abstractions and premature optimisation, and ask where accessibility and our users went in the process.
My Porsche has an API, so I wanted it in my smart home. This article follows the custom Homebridge plugin I built around Porsche Connect, from discovering the API to exposing sensors and accessories in HomeKit. It includes the setup and polling needed to keep the integration running.
