Open Metrics

Site Statistics

An overview of my blog posts, projects, and tech stack.

Short answer

This dashboard reports open metrics read from the site's own database: 378 published blog posts, 40 projects and 296 GitHub stars. Every card states its source, window and last refresh; this snapshot is as of Nov 1, 2026, 2:24 PM. Core Web Vitals figures are the p75 of real field measurements.

Blog Posts
378
Projects
40
Technologies
90
Years of Experience
12
Comparisons
110
English Translations
187

These numbers are read from the site database and refresh every 5 minutes. Nov 1, 2026, 2:24 PM

0

Blog Posts

source
Source
Site database (PostgreSQL)
Location
blog_posts.status = 'published'
Window
point-in-time count
Sample
the count itself
Last refresh
Nov 1, 2026, 2:24 PM

0

Projects

source
Source
Site database (PostgreSQL)
Location
projects.status = 'published'
Window
point-in-time count
Sample
the count itself
Last refresh
Nov 1, 2026, 2:24 PM

0

Technologies

source
Source
Site database (PostgreSQL)
Location
projects.technologies — tekil değer (status = 'published')
Window
point-in-time count
Sample
40
Last refresh
Nov 1, 2026, 2:24 PM

0

Years of Experience

source
Source
Source file in the repository
Location
src/lib/constants/about.ts → TIMELINE (en eski iş yılı)
Window
point-in-time count
Sample
the count itself
Last refresh
Nov 1, 2026, 2:24 PM

0

Comparisons

source
Source
Source file in the repository
Location
src/lib/comparisons-data.ts → COMPARISONS.length
Window
point-in-time count
Sample
the count itself
Last refresh
Nov 1, 2026, 2:24 PM

0

English Translations

source
Source
Site database (PostgreSQL)
Location
blog_translations.locale = 'en' AND status = 'published'
Window
point-in-time count
Sample
the count itself
Last refresh
Nov 1, 2026, 2:24 PM

0

Categories

source
Source
Site database (PostgreSQL)
Location
blog_posts GROUP BY category (status = 'published')
Window
point-in-time count
Sample
the count itself
Last refresh
Nov 1, 2026, 2:24 PM

0

GitHub Stars

source
Source
GitHub snapshot (build time)
Location
public/github-data.json → totalStars
Window
point-in-time count
Sample
the count itself
Last refresh
Nov 1, 2026, 8:05 AM

Blog Categories

source
Source
Site database (PostgreSQL)
Location
blog_posts GROUP BY category (status = 'published')
Window
point-in-time count
Sample
the count itself
Last refresh
Nov 1, 2026, 2:24 PM
378posts

Grouping rule: categories are ranked by post count, the top 8 each get their own slice and the rest are summed into a single “Other” slice — no post is left out of the chart.

Posts by category
CategoryPostsShare
AI10026.5%
iOS4712.4%
Flutter215.6%
SwiftUI195%
Business184.8%
Android174.5%
Cross-Platform174.5%
Swift164.2%
Other (27)12332.5%

Core Web Vitals (p75 · last 7 days)

source
Source
analytics-api field measurements
Location
analytics-api /vitals → lcp_p75 · inp_p75 · cls_p75
Window
last 7 days
Sample
65
Last refresh
Nov 1, 2026, 2:24 PM

LCP

1339ms

INP

152ms

CLS

0.020

65 samples

Language Distribution

source
Source
GitHub snapshot (build time)
Location
public/github-data.json → languages (dil → depo sayısı)
Window
point-in-time count
Sample
the count itself
Last refresh
Nov 1, 2026, 8:05 AM
  • Swift
    54
  • TypeScript
    10
  • Dart
    3
  • JavaScript
    1
  • Ruby
    1

This chart shows the NUMBER OF REPOSITORIES per dominant language, not lines of code. I do not publish self-scored skill percentages.

I can set up this measurement discipline in your project

Every figure above is read from a live source and states where it comes from. If you want the same discipline for performance, architecture and measurement in your mobile or web product, leave a short brief.

  • 378 posts
  • 40 projects
  • LCP p75 1,339 ms (n=65)
Muhittin is one of the best in Turkey when it comes to MapKit and real-time location tracking. In our fleet management app we track our entire fleet simultaneously without a hitch. His background processing optimizations noticeably extended battery life.
Can Aksoy · VP of Engineering · FleetTrack

Metrics I deliberately do not publish

The measurement stack collects these; I do not print them as numbers here for sample-size or privacy reasons.

Visitor and session counts
The sample is not large enough for a meaningful trend on a portfolio site; a single shared link rewrites the whole chart.
Conversion rate
A rate published on a small denominator reads like a real performance claim. I publish the raw counts instead.
Revenue and project budgets
This belongs to client contracts; even anonymised, combining it with project counts makes it recoverable.
Total code volume (lines/bytes)
The GitHub snapshot does not carry repository size, and size would count generated files and assets anyway — so it is not a measure of “code written”. I publish the language distribution instead.