Chidera (Di Maria) Humphrey

Frontend dev → technical writer | I write tutorials developers finish | @FreeCodeCamp contributor

[Chidera (Di Maria) Humphrey @ChideraCode]

Most SaaS tutorials teach you how to use the product.

Vercel's tutorials teach you how to ship with it.

There's a difference.

I tore down Vercel's Next.js + Prisma guide to see how their content drives activation.

Here's what they do that most companies skip:

[Chidera (Di Maria) Humphrey @ChideraCode]

If you like technical content writing break downs like this, you'll like my newsletter. Every Wednesday, I share practical tips on writing content that developers love.

Subscribe with the link 👇

https://t.co/9TUk0rDlAN

[Chidera (Di Maria) Humphrey @ChideraCode]

I used to think bigger code dumps meant better tutorials.

After writing 20+ articles and studying blogs like Stripe and Vercel, I noticed developers were skimming past my 50-line examples without reading them.

Here's what I changed:🧵

[Chidera (Di Maria) Humphrey @ChideraCode]

Good technical content isn't about showing how much you know.

It's about helping someone make progress.

Chunk the code. Explain the logic. Let the repo do the rest.

[Chidera (Di Maria) Humphrey @ChideraCode]

Found a thread where Next.js developers were asking about API key authentication for route handlers specifically.

Same solution I was already building. Almost nothing written about it in that context.

Built the project in Next.js and wrote for that audience instead.

[Chidera (Di Maria) Humphrey @ChideraCode]

Before I outline any tutorial, I go through Reddit.

Not to validate the topic. To find how developers are actually talking about the problem.

That language tells me how to frame the problem, write the hook, and structure the steps.

[Chidera (Di Maria) Humphrey @ChideraCode]

P.S. I write tutorials like this for developer tool companies. DM me if that's useful.

[Chidera (Di Maria) Humphrey @ChideraCode]

Most of the effort in API key creation rests on the user.

1. Sign up
2. Create a key
3. Copy it into Postman
4. Run a test

What if their key was already there when they signed up?

I wrote about how to auto-provision API keys on signup using Supabase and Zuplo.

Read 👇:

[Chidera (Di Maria) Humphrey @ChideraCode]

https://t.co/UX3kd1zmI1

[Chidera (Di Maria) Humphrey @ChideraCode]

Before I outline any tutorial, I go through Reddit.

Not to validate the topic. To find how developers are actually talking about the problem.

That language tells me how to frame the problem, write the hook, and structure the steps.

[Chidera (Di Maria) Humphrey @ChideraCode]

https://t.co/ijvTcz07kv

[Chidera (Di Maria) Humphrey @ChideraCode]

API key auth is popular for a reason. It's also harder to get right than it looks.

Key provisioning, rotation, and scanning. There's more to a decent implementation than most expect.

Wrote a full guide on adding API key auth to Next.js routes (my first HackerNoon piece 😊)👇

[freeCodeCamp.org @freeCodeCamp]

Creating complex objects can get messy - constructors with too many params, tricky optional arguments, etc.

Well, the builder pattern helps solve these issues by separating object construction from representation.

In this guide, @balawc27 shows you how the pattern works in Python with plenty of code examples.

https://t.co/t2SSFmHT5v

[Chidera (Di Maria) Humphrey @ChideraCode]

@pwaiomoakinwale @TechnicalBben Tech is a broad term. It depends on which part of tech you want to go into.

[Chidera (Di Maria) Humphrey @ChideraCode]

@pwaiomoakinwale @TechnicalBben If you ghostwrite for tech founders or companies, technically you're in tech 😏

[Chidera (Di Maria) Humphrey @ChideraCode]

@Xylon_lew True. The reader is there for how to solve a problem.

[Chidera (Di Maria) Humphrey @ChideraCode]

Most DevTool changelogs are written for engineers who already know what shipped.

Nobody writes them for the developer who almost churned last month.

Your release cadence is already a content cadence. Most teams just never treat it that way.