DEV Community: Ahmed

I created attention for myself (I'm pathetic)

Ahmed — Wed, 24 Jun 2026 00:02:11 +0000

I sent 47 CVs in one year and got exactly zero replies.

Not a single rejection email. Not even a "we decided to go in a different direction." Just pure, deafening silence. I was ghosted by every single company I applied to.

I rewrote my CV from scratch. Then rewrote it again. Changed the format, the font, the structure, the summary. I asked friends to review it. I watched YouTube tutorials at 2 AM. I tailored it to each role. I did everything "right."

Nothing.

For twelve months, I refreshed my inbox like it owed me money. I started questioning whether my applications were even going through. Whether I was invisible. Whether I just was not good enough.

Then something broke inside me. Not in a sad way. In a fed-up way.

I stopped asking "why can I not find an internship" and started asking a sharper question: "why am I being ghosted before a human even reads my CV?"

That question changed everything.

I discovered that most of my CVs were being filtered out by ATS systems before they ever reached a recruiter's desk. The problem was never my skills. It was the translation layer between my experience and what the algorithm wanted to see.

So I built the thing I wished existed during my darkest job-search days.

CV Architect is a SaaS tool that optimizes your CV based on the specific job posting you are targeting. It reads your resume the way an employer would. It checks ATS compatibility. It tells you what is missing before you hit send, so you stop screaming into the void.

I did not set out to build a product. I set out to find an internship. But sometimes the struggle itself becomes the solution if you pay close enough attention.

The site is live. You can try it with your own CV right now. And I genuinely want your feedback, the honest kind, the kind that makes the product better.

What is the longest you have ever been ghosted during a job search?

İş İlanına Uygun CV Nasıl Yazılır? AI ile Optimize Et (Türk İş Arayanlar İçin)

Ahmed — Thu, 18 Jun 2026 17:57:37 +0000

Geçen hafta 50 CV'yi analiz ettim.
Cevap buldum: İşe yarayanların hepsi bir şeyi yapıyor — işe yaramayan yüzde 95'i ise hiç yapmıyor.
O şey nedir? CV'lerini iş ilanına göre optimize etmek.

SORUN: GENEL CV YANLIŞ OYUN
Son 5 yıl halkta sık görülen hata:
❌ Bir CV, yüz iş başvurusu

❌ "Profesyonel", "Yaratıcı", "İletişim becerileri var"

❌ Hiç rakam yok — sadece güzel kelimeler

❌ İlan ne istiyor? "Bilmem, ben bu CV'yi çok seviyorum"
Sonuç? Takılan olmayan başvurular, reddedilen mail'ler.
İnsan kaynakları (HR) ortalama 7 saniye bir CV'ye bakıyor. 7 saniye. Onda ilk gözüne çarpan: CV'nin iş ilanı ile uyumunun olup olmadığı.
Eğer CV genel yazılmışsa, HR "Bu kişi bu rol için mi yazıyor, yoksa rasgele yolluyorsa mı?" düşüncesiyle geçiyor.

ÇÖZÜM: İŞ İLANINA ÖZEL CV
İyi haberle başlayalım:
Genel CV'den iş ilanına uygun CV'ye geçmek sadece 15-20 dakika alıyor.
Ama manuel olarak?

İş ilanını oku (5 dakika)
Önemli kelimeleri işaretle (3 dakika)
CV'ni düzenle (10 dakika)
PDF'i indir (2 dakika)

= 20 dakika per başvuru

Haftalık 20 başvuru yapıyorsan?

= 6-7 saat işi harcaman gerekiyor
Burada AI devreye giriyor.

AI İLE CV OPTİMİZASYONU: GERÇEK BİR ÖRNEK
Şunu hayal et:
İŞ İLANI:

Senior Frontend Developer — React + TypeScript

3+ yıl deneyim
Performance optimization
Team leadership preferred

SENIN CV'NDE (ŞU AN):

"Yazılım geliştirici olarak 4 yıl çalıştım.

Ekipte iyi iletişim kurabilirim.

React biliyorum."
AI OPTİMİZE ETTİ SONRA:

"Senior Frontend Developer — 4 yıl deneyim

React & TypeScript ile 50+ production components geliştirdim
Web sayfasında 45% performance improvement sağladım

(Lighthouse score: 38 → 92)
3 kişilik frontend ekibi lead ettim, code reviews yaptım"

Fark görüyor musun?
İlk hali genel, ikinci hali iş ilanına direkt cevap veriyor.
HR 7 saniye içinde: "Tamam, bu adam biliyordu ne yapıyor." deyip ilgisini çekiyor.

İŞ İLANINA UYGUN CV YAZMA ADIMLARI
ADIM 1: İŞ İLANINI DİKKATLİCE OKU
İlan'da şu kelimeleri bul:

Must-have skills: React, Python, SQL vb.
Nice-to-have: Leadership, Agile vb.
KPI'lar: "Haftalık 100+ request handle et" gibi
Problem çözmek: "Ödeme sistemi yavaşlığını fix ettim" gibi

ADIM 2: SENİN CV'NDEN İLGİLİ KISIMLAR ÇIKAR
Tüm CV'ni gönderme. Sadece iş ilanı ile ilgili olanları vurgula.
Örnek:

İlan React istiyor → JavaScript/Frontend section'ı highlight et
Leadership istiyor → Ekip yönetim tecrübeni ön plana çıkar

ADIM 3: SAYILAR EKLE
❌ YANLIŞ:

"Veritabanı performans iyileştirmesi yaptım"
✅ DOĞRU:

"Sorgu optimize ile veritabanı response time'ı 5 saniyeden 500ms'ye düşürdüm (10x improvement)"
Rakamlar = İspat.
ADIM 4: İŞ İLANINDAKİ DİLİ KULLAN
İlan şu kelimeleri kullanıyorsa senin CV'nde de kullan:

"Agile" sıkça geçiyor → senin CV'ne "Scrum" ekle
"Full-stack" istiyor → sen "Frontend" + "Backend" yaz
"Cloud infrastructure" istiyor → "AWS", "Docker" explicit yaz

HR elektronik tarama (Applicant Tracking System - ATS) yapıyor. CV'nde ilanın kelimeleri varsa sistem seni ön sıraya koyuyor.
ADIM 5: PDF İNDİR, GÖNDER
İş ilanına uygun CV'yi PDF'le indir, başvur.

3 SIK YAPILAN HATA
HATA 1: "DEĞERLER" YERİNE "BAŞARILAR"
❌ "İletişim becerileri var"

✅ "Müşteri problemi çözdüğümde 20% daha fazla positive feedback aldım"
HATA 2: GENEL CV HERKESE GÖNDERME
❌ Pazarlama ilanına Frontend CV gönder

✅ CV'deki pazarlama / business impact kısımlarını highlight et
HATA 3: TARİHİ ATLA
❌ "3 yıl deneyim"

✅ "2021-2024: Senior Developer (3 yıl)"
Tarih = Güvenilirlik.

SONUÇ: 7 SANİYE KURALI
HR'nin ilk 7 saniyesinde CV'nin şunları göstermesi lazım:

İLGİLİ SKİLL'LER — iş ilanında yazanlar
SAYILARLA KANIT — neyi başardığın
TARİH VE BAĞLAM — ne zaman, ne kadar süre
İŞ İLANINA CEVAP — sadece ilgili kısımlar

Eğer bu dört elemanı görebilirse HR 7 saniyede "Tamam, görüşmeye çağırmalıyız" diye karar verir.

İŞTE GERÇEK OYUN: AI KIŞAYETME
Ancak şunu biliyorsun: Manuel olarak her iş ilanı için CV optimize etmek saat harcıyor.
20 başvuru = 6-7 saat.
300 başvuru = 90-105 saat = 3 hafta tam zamanlı.
Kimde var 3 hafta?
Burada AI devreye giriyor. Bir AI tool'u (mesela CV Mimarı) kullanırsan:

İş ilanını yapıştır
"Optimize et" butonuna bas
30 saniye sonra: İlanına uygun CV'n hazır
PDF indir, gönder

Süresi? 2 dakika per başvuru. 20 başvuru = 40 dakika.
Fark hissettin mi?

TÜRKÇE İŞ PİYASASI'NDA GERÇEK SONUÇ
2024'te iş bulma oyunu değişti. Eski kurallar:

Bir CV, 100 başvuru
Umarız biri cevap verir
Kaç tane reddedildi? "Bilmem"

Yeni kural:

50 başvuru, 50 farklı CV (her birine optimize)
Cevap oranı 5x yükseliyor
Hatta iş bulduğun zaman daha iyi pozisyon

Neden? Çünkü HR senin CV'sinde "Bu rol için yazıldı" görüyor.

HAZIRSANİZ: İLK ADIM
CV'nizi optimize etmek 15 dakika alıyor. Hatta AI ile 2 dakika.
Şu an bunu yapan Türkçe tool yok — ben de yaptım. CV Mimarı deniyor.
Deneyimek istersen:

3 ücretsiz kredi ile başla
İş ilanına uygun CV'yi gör
Beğenirsen, paket satın al

Hedef: İş bulana kadar seni desteklemek.
Başvuru yağmuruna hazır mısın?

I created a website specifically for my laziness.

Ahmed — Mon, 08 Jun 2026 22:03:52 +0000

I built an AI tool to write LinkedIn posts.

And nobody cared.

Let me tell you the full story because I think it matters.

Three months ago I was sitting in my apartment at 2 AM, convinced I had found a gap in the market. I was spending hours every week trying to write LinkedIn content for my own brand. Staring at blank screens. Rewriting the same sentence fourteen times. Watching other founders post effortlessly while I struggled to string together three coherent paragraphs.

So I thought, what if I just build something to fix this. An AI-powered web app that helps people create LinkedIn posts faster. Smart templates. Tone selection. Hook generators. The whole package.

I went heads down for weeks. Designed the UI. Built the backend. Integrated the AI models. Tweaked the prompts until the output actually sounded human. I was proud of it. Genuinely proud.

Then I launched it.

Crickets.

Not the dramatic kind where you get hate or pushback. The worse kind. Silence. A few sign-ups from friends who never came back. A couple of polite messages saying it looked cool. Zero paying users in the first two weeks.

Here is what I got wrong and I am sharing this because I see other founders making the same mistakes right now.

First, I built in isolation. I never once asked my target audience what they actually needed. I assumed my own pain point was universal. It was not. Some people wanted help with ideas, not full posts. Some wanted editing, not generation. I built for a version of the customer that only existed in my head.

Second, I launched without distribution. I had no audience. No email list. No community. I just put it out there and expected the product to speak for itself. Products do not speak. People do. And I had nobody speaking for mine.

Third, I underestimated how crowded the space already was. There are dozens of LinkedIn content tools. Some backed by real teams with real budgets. I did not take five minutes to ask myself what makes mine genuinely different. The honest answer at launch was nothing.

So what did I do next.

I stopped building features and started having conversations. I reached out to fifty founders and content creators. I asked them to use the tool and tell me everything that was broken, confusing, or unnecessary. The feedback was brutal and exactly what I needed.

I started posting on LinkedIn myself, using my own tool, sharing the messy behind-the-scenes journey. That raw honesty attracted more users than any feature ever did.

Slowly things started shifting. Not overnight. Not dramatically. But the kind of slow traction that actually means something because it is built on real feedback from real people.

The tool is still early. I am still figuring it out. I am not writing this as a success story. I am writing this as a founder who made every classic mistake in the playbook and is trying to learn from each one in public.

If you are building something right now and you have not talked to a single potential customer this week, close your code editor and open a conversation instead.

That is the lesson I paid for with three months of my time.

What is the biggest mistake you made early in building your product? I would genuinely love to hear it.

I Built a Flutter Package for Turkish-Specific Form Validation

Ahmed — Sat, 06 Jun 2026 11:45:02 +0000

I Built a Flutter Package for Turkish-Specific Form Validation

If you've ever built a Flutter app targeting Turkish users, you know the pain.

You need to validate a TC Kimlik No — there's no package for that. You need to format a Turkish IBAN — you end up writing your own regex. You want a proper ₺1.250,50 currency format — good luck finding something ready-made.

So I built it myself: turkish_validators

What's inside

✅ TC Kimlik No Validation

TC Kimlik No has a real checksum algorithm behind it — it's not just "is it 11 digits." This package validates the full algorithm:

bool isValid = TcKimlik.validate('12345678901');

// Drop it straight into a TextFormField
TextFormField(
  validator: TcKimlik.formValidator,
)

✅ Turkish IBAN (MOD-97)

Validates TR IBANs using the MOD-97 standard and formats them for display:

bool isValid = TurkishIban.validate('TR330006100519786457841326');

String formatted = TurkishIban.format('TR330006100519786457841326');
// → TR33 0006 1005 1978 6457 8413 26

TextFormField(
  validator: TurkishIban.formValidator,
)

✅ Turkish Phone Number

Handles both 0532... and +9053... formats, plus clean formatting for display:

bool isValid = TurkishPhone.validate('05321234567');   // true
bool isValid2 = TurkishPhone.validate('+905321234567'); // true

String formatted = TurkishPhone.format('05321234567');
// → 0532 123 45 67

✅ Turkish Lira Formatting

Proper Turkish number format with dot-as-thousands and comma-as-decimal:

String price = TurkishLira.format(1250.5);
// → ₺1.250,50

String price2 = TurkishLira.format(1250.5, showSymbol: false);
// → 1.250,50

double? amount = TurkishLira.parse('₺1.250,50');
// → 1250.50

Installation

dependencies:
  turkish_validators: ^0.0.3

That's it. No extra dependencies — just Flutter.

Why I built this

I kept rewriting the same validators across different projects. TC Kimlik alone has a non-trivial algorithm that I was copy-pasting between apps. IBAN formatting was always a manual job. At some point it just made sense to package it properly.

The Turkish Flutter ecosystem has a lot of talented developers but not many locale-specific utilities. Hopefully this saves someone a few hours.

DEV Community: Ahmed

I created attention for myself (I'm pathetic)

İş İlanına Uygun CV Nasıl Yazılır? AI ile Optimize Et (Türk İş Arayanlar İçin)

I created a website specifically for my laziness.

I Built a Flutter Package for Turkish-Specific Form Validation

I Built a Flutter Package for Turkish-Specific Form Validation

What's inside

✅ TC Kimlik No Validation

✅ Turkish IBAN (MOD-97)

✅ Turkish Phone Number

✅ Turkish Lira Formatting

Installation

Why I built this

Links