4+ years shipping enterprise web applications across Ford Otosan, B2B SaaS, and freelance. I treat architectural decisions as tradeoffs — not religion — and document the why so the next engineer doesn't have to guess. Lately I've been bottling up everything I wish I'd had on day one into reusable production templates.

Two end-to-end templates that pair into a complete starter for any new product:

Why these matter: every architectural decision in the docs follows a Decision → Why → Alternatives → Tradeoff block. They aren't tutorial dumps — they're the templates I personally use to ship.

Freelance · Full Stack Developer — 07/2025 – 03/2026 Client demo environments, technical prototypes, and Python automation pipelines (~800 SKU normalization + bulk import workflows with metadata enrichment).

Ford Otosan · Full Stack Developer (.NET 8) — 11/2023 – 06/2025 Enterprise applications in Clean Architecture + Repository Pattern.

• Cut average API response time ~25% (1.2s → 0.9s) via stored procedures + execution plan analysis
• Reduced technical debt ~20% by integrating SonarQube into Azure DevOps YAML CI/CD pipelines
• JWT authentication, RESTful APIs documented with Swagger / OpenAPI, async/await throughout
• Structured Pull Request workflows with code review and Git-based version control

Onerov IT · Full Stack Developer — 07/2021 – 10/2023 Multi-tenant SaaS modules — .NET Core MVC / WebAPI + Angular.

• Improved database performance ~15% through indexing and query optimization
• Entity Framework Core + LINQ + Repository Pattern for clean data abstraction
• RESTful APIs documented with Swagger

Gendarmerie General Command · Reserve Officer (First Lieutenant) — 02/2019 – 02/2020 Mandatory military service. Delivered structured technical training sessions on networking fundamentals.

B.Sc. Computer Engineering · Sakarya University — 2013 – 2018

Clean Architecture · N-Layer Architecture · Repository Pattern · SOLID · Dependency Injection · CQRS · Result Pattern · JWT + Refresh Rotation · RESTful API design · Async / Await · Structured Code Review · Agile / Scrum

public sealed record Erdem
{
    public string Title           => ".NET Full Stack Developer";
    public int    YearsOfPractice => 4;

    public List<string> Beliefs { get; } =
    [
        "Architectural decisions are tradeoffs, not religions — document the why.",
        "Senior isn't about exotic problems. It's about CRUD that survives 6 months later.",
        "Comments don't explain WHAT — names do that. Comments explain WHY.",
        "Production-ready means: works on Friday, still works on Monday."
    ];

    public string CurrentlyAvailableFor =>
        "Freelance · Contract · Remote full-time · Worldwide";
}

If you're hiring, contracting, or just want to compare notes on .NET architecture choices — pick any: