Articles on JavaScript, React, Next.js, system design, and modern engineering practices, shared in chronological order.
When we talk about security, frontend engineers are often treated as secondary players. This article is not about basic security checklists. It's about subtle, real-world security mistakes frontend engineers make — even at senior levels — and why these mistakes keep repeating across companies.
I started my career as a backend engineer. I used to think the backend was where the “real” complexity lived. We had distributed systems, eventual consistency, and database locks. The frontend? I thought that was just painting buttons and making API calls.
A few years ago, I watched a senior developer in our team spend an entire afternoon writing unit tests for a moderately complex form component. Hours of scanning through props, mocking edge cases, fixing linter issues—it was the kind of work that felt more tedious than impactful.