Authors

Alex Chen

20 posts

Alex Chen has spent ten years building frontend systems at scale, across both product companies and consultancy work. Alex's writing focuses on React patterns, JavaScript internals, and the decisions that separate maintainable codebases from ones that fight back. The articles are opinionated by design — not because there's only one right answer, but because vague advice doesn't help you ship. Alex writes for engineers who already know the basics and want to level up how they think, not just what they know.

Dev Okonkwo

0 posts

Dev Okonkwo came to web development without a CS degree, learning through tutorials, documentation, and a lot of trial and error. That path — longer and messier than a bootcamp or university — gave Dev a clear memory of what's actually confusing for beginners, and a commitment to writing the explanations that didn't exist when they were needed. Dev's articles cover HTML, web fundamentals, and the concepts that experienced developers often forget weren't obvious when they first learned them.

Jordan Reef

0 posts

Jordan Reef is a software engineer who specializes in integrating large language models into production applications. After spending two years building internal AI tooling at a mid-size SaaS company, Jordan now consults independently and documents the gap between AI demos and AI products. Jordan writes for engineers who are tired of hype and want practical implementation guides.

Kai Lindström

0 posts

Kai Lindström spent five years as a software engineer before pivoting to content strategy and growth, first in-house at a developer tools company and then independently. Kai's work sits at the intersection of SEO, content marketing, and the specific challenges of building an audience as a technical person — where the instinct to go deep conflicts with the need to be findable. Kai writes for developers who want to build something beyond their day job, with an honest account of what works, what doesn't, and what the numbers actually look like.

Mira Halsted

0 posts

Mira Halsted spent twelve years as a software engineer and engineering lead before moving into technical writing full-time. Her work focused on scaling frontend infrastructure at companies where "just works on my machine" wasn't good enough — building monorepos, standardizing toolchains, and making CI pipelines fast enough that engineers actually trust them. Mira writes for engineers who are responsible for more than their own code and need to make decisions that affect the whole team.

Muhammad Athar

12 posts

Muhammad Athar is the founder and engineer behind DesignDev.io. With a background in full-stack development, he built and runs the platform the other writers publish on — which means he's usually the first person to actually implement everything they cover. His articles fill the gaps: the concepts that appear without explanation in advanced tutorials, the "wait, what does that actually do?" moments that intermediate developers hit when reading senior-level content. If Alex Chen writes the pattern and you want to understand the primitive underneath it, Muhammad's article is the next one to read.

Priya Nolan

0 posts

Priya Nolan has been building and breaking infrastructure for nine years, working across fintech and e-commerce at companies ranging from 5 to 500 engineers. Priya's articles are written specifically for software engineers who aren't infrastructure specialists but need to be competent enough to ship and operate their own services. Expect plain English, real configurations, and an honest accounting of what each tool actually costs — in time and money.

Ren Calloway

0 posts

Ren Calloway spent a decade as a software engineer before going independent in 2020. Since then, Ren has consulted for over 30 clients across product, fintech, and agency work — and has written honestly about what that transition looks like: the income volatility, the contract negotiation, the skill gaps, and the parts that are genuinely better. Ren's writing is for developers at a crossroads who want information, not motivation.

Sam Vickers

0 posts

Sam Vickers has spent eight years building APIs and backend systems across startups and mid-market companies. Sam's writing focuses on the unsexy decisions that determine whether a system scales: schema design, error handling, auth architecture, and choosing the right database for the right job. If you're looking for the flashy framework tutorial, look elsewhere. If you want to understand why the decision matters, you're in the right place.

Sena Aruoba

1 post

Sena Aruoba works at the boundary between design and engineering — equally comfortable in Figma and a stylesheet, and deeply invested in the gap between them. With a background in visual design and front-of-the-frontend development, Sena's writing focuses on CSS craft, design system architecture, and the accessibility work that makes interfaces genuinely usable for everyone. Sena's articles are for engineers who want their work to look intentional, not just functional.