jeyididya.com

Right, let's talk about this hero section. The GOOD news? It does the ONE thing most developer portfolios completely botch — it tells me what you do in ONE sentence without making me want to gouge my eyes out. I build backend systems that ship cleanly and stay maintainable. THAT is a headline, not the usual passionate problem-solver who loves clean code DRIVEL I see on every other dev portfolio. The green accent on ship cleanly against that dark background? Sharp. Like a proper garnish — small but it WORKS.

The stats block — 14 projects, 3+ years, Django/FastAPI, Mobile+Web — gives me context immediately. Four CTAs above the fold (Telegram, Email, Resume, plus contact in the nav) covering every way a client might want to reach you. That's SMART mise en place.

But here's where I start throwing pans. WHERE IS YOUR FACE?! You're asking people to hand you the keys to their production database and you won't even show them what you look like? That's like a chef refusing to come out of the kitchen when the restaurant's ON FIRE. A human photo above the fold is the single most powerful trust signal on a portfolio page, and you've got NOTHING. You're a ghost asking for a bank transfer!

The CTA buttons say Telegram and Email — those are DESTINATIONS, not ACTIONS. That's like labeling a restaurant door Wood instead of Enter. Where's Hire Me? Where's Start a Project? You're making the client do the mental work of figuring out what clicking that button MEANS.

And the Ethiopia/Addis Ababa angle — THAT is actually your secret weapon! Local market expertise, specific timezone, real businesses you've served. But it's shoved into a tiny badge like you're embarrassed about it. Weaponize that! That's your truffle, and you're hiding it under the salad. Seriously?!

Now HERE'S the thing that actually surprised me — the copywriting on this portfolio is genuinely better than what I see on most developer sites. And I've seen a LOT of developer sites. Most of them read like someone fed a thesaurus into a blender. Yours? You actually TELL STORIES.

Every project has a Problem/Built/Outcome structure. Delivered in under a month and published on Google Play. Shipped in 2 months with browsing, ratings, and review flows. These are RESULTS, not just a list of frameworks you've touched. That's like showing me the finished dish instead of just listing ingredients. The How I Work section — I communicate clearly, deliver on time, and write code that the next engineer can actually read — is PUNCHY. Client-focused. No waffle. I respect that.

BUT — and this is a BIG but, like finding a hair in your soup — the copy has a fundamental identity crisis. Is this written for developers or for CLIENTS? Because the skills section lists Flask, Redis, FFmpeg, Docker like it's a shopping list at a tech supermarket. The coffee shop owner who needs a POS system doesn't know what FFmpeg IS, and frankly, they shouldn't HAVE to! You're serving raw ingredients to people who ordered a finished meal!

The Best Fit and Good Problems sections are the BEST client-facing copy on this entire page — Backend-heavy MVPs and internal tools, Payment, ticketing, POS, reporting — THAT'S what a client needs to see first! And where have you buried it? HALFWAY DOWN THE PAGE after a wall of technical jargon. That's like putting your signature dish on page 47 of the menu!

The About section — I started coding in 2019 and quickly found my passion in backend engineering — the invisible plumbing that makes software work at scale — look, invisible plumbing is a decent metaphor but it's been done to DEATH in dev circles. More importantly, your origin story is about YOU, not about what it MEANS for the client. I started coding in 2019 is a feature. Turn it into a benefit or it's just autobiography nobody asked for.

The tone throughout is confident without being arrogant, grammar is clean, length is right. Your project descriptions are the filet mignon of this page — now make the rest of the copy match that quality!