ChideraCode's profile picture. Frontend (React/Next.js) Developer & Technical Writer | Helping SaaS teams ship fast websites & developer-focused content.

Email: chidera@chiderahumphrey.com

Chidera (Di Maria) Humphrey

@ChideraCode

Frontend (React/Next.js) Developer & Technical Writer | Helping SaaS teams ship fast websites & developer-focused content. Email: [email protected]

My current AI coding setup in VS Code: · General tasks: Claude · Backend helpers: GitHub Copilot · Frontend/UI: Kombai Each one plays to its strengths. What's your AI setup?


Ever felt like hitting your PC when the AI-generated UI looks different from your design system? Been there. I’ve been using Kombai for a while now, and it’s pretty accurate in matching my design system and component structure. Consistency with minimal manual effort.


Tried different prototyping tools, but the code was never meant for a real, growing codebase. Kombai feels different. It builds directly into my repo, understands my structure, and creates components that actually fit. It's built for production, not just prototypes.


Tried using Gemini for a complex React form state and got spaghetti code that I spent 45 mins refactoring. Recommended by my friend, I switched to Kombai. It used my existing context and built the form state with clean, reusable hooks. Sometimes, you just need a specialist.


I'm working on my first SaaS app (ContentCraft—an AI content repurposer) and am trying out this new AI coding agent, Kombai, and loving it so far.


After my recent app, I'm swapping Gemini CLI for Kombai. The UI generation capability of Kombai is great. Clean code, reusable components, nice folder structure. God, I'm loving this AI coding agent.


After my recent Nextjs website, I'm swapping Gemini CLI for Kombai. The UI generation capability of Kombai is great. Clean code, reusable components, nice folder structure. God, I'm loving this tool.


The best way I’ve learned React/Next.js: Building projects while writing tutorials. It forces me to notice: - Edge cases - Missing doc steps - The “why” behind each choice Do you learn best by building, writing, or working on projects? #buildinpublic


Hot take: docs aren’t enough. Devs want: - Tutorials with real use cases - Content that explains the why - Copy-pasteable examples SaaS companies that win dev mindshare invest in dev-focused content.


Optimizing images boosts website speed and SEO. As a frontend dev, I look for ways to make my websites faster. How I'm optimizing my images: - Cloudinary: hosting images - next-cloudinary: automatic image optimization This combo helped me achieve this page speed score.

ChideraCode's tweet image. Optimizing images boosts website speed and SEO.

As a frontend dev, I look for ways to make my websites faster.

How I'm optimizing my images:
- Cloudinary: hosting images 
- next-cloudinary: automatic image optimization 

This combo helped me achieve this page speed score.
ChideraCode's tweet image. Optimizing images boosts website speed and SEO.

As a frontend dev, I look for ways to make my websites faster.

How I'm optimizing my images:
- Cloudinary: hosting images 
- next-cloudinary: automatic image optimization 

This combo helped me achieve this page speed score.

Writing as a developer has had a great impact on my frontend journey. From gigs to collaboration and even access to cutting-edge tech, the benefits have been great. If you're struggling to get noticed, try tech content writing. #buildinpublic


I’ve been stuck on this error for 2 days now. Tried fixes from articles, Stack Overflow, even GitHub issues, but no luck. This is from my latest project: an AI content repurposer. I’m trying to parse PDFs using the pdf-parse library. Have you run into this before? #nextjs

ChideraCode's tweet image. I’ve been stuck on this error for 2 days now.

Tried fixes from articles, Stack Overflow, even GitHub issues, but no luck.

This is from my latest project: an AI content repurposer.

I’m trying to parse PDFs using the pdf-parse library.

Have you run into this before?

#nextjs
ChideraCode's tweet image. I’ve been stuck on this error for 2 days now.

Tried fixes from articles, Stack Overflow, even GitHub issues, but no luck.

This is from my latest project: an AI content repurposer.

I’m trying to parse PDFs using the pdf-parse library.

Have you run into this before?

#nextjs

Loading...

Something went wrong.


Something went wrong.