Skip to content
View ertgl's full-sized avatar

Block or report ertgl

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
ertgl/README.md
About

Hello, I'm Noyan.

/ɛrˈtuːɾul noˈjan keɾeˈmoːɫu/

This is my jungle boogie. [🎵] [🎶]

I design elegant algorithms and resilient software architectures, to solve hard problems with authentic solutions. I believe the best developer experience is when a system lets everybody sleep well.

For more, below are some of my technical interests, guiding principles, and a few off-topic notes that reflect my professional and personal style.

Technical interests:

  • Programming languages:
    • Syntax, semantics, and paradigms. How they are implemented and how they influence our thinking.
    • Imperative-first, declarative-later. FP/OOP. Domain specific.
  • Algorithms and data structures:
    • Time/space complexity. Zero-copy/zero-cost abstractions.
    • Data architecturing. Trade-offs.
  • Systems design and software architecture:
    • Extensibility, interoperability, performance, and reliability.
    • Domain analysis/design. Patterns with/without OOP.
    • Metaprogramming. Tooling. Developer experience.
  • Distributed systems:
    • Consistency, high availability, fault tolerance.
    • Event-driven, data ingestion, back-pressure.
    • Deploy it once and watch how everyone is happy about it for years.
  • Human–centered computing:
    • Interaction design. User interface/experience.
    • Visualizations are cool. Accessibility is a must.
  • Automation and self-healing:
    • Minimal human intervention.
    • Adaptive systems. Agentic processes.
    • Zero-alloc logging. Monitoring and alerting stuff.
  • CI/CD pipelines:
    • Automated, transparent workflows for builds, tests and deployments.

Guiding principles:

  • Accessibility: Sometimes even seconds matter. A good system shouldn't behave like a barrier.
  • Deterministic environment: Automating what you don't control will eventually fail.
  • Resource consumption: Aim for efficiency. Performance without it can burn what you'll need next.

Off-topic:


Status

Currently

  • Working on holypack.
    • Adding source analysis features to export-map-generator.
    • Building an enhanced Babel CLI focused on dual-package TypeScript projects.

Latest


Scaling with no supervision breaks sustainability. Software is not soft. Safety first. 💚

Feel free to say hi. Contact links are on my profile.

Pinned Loading

  1. holypack holypack Public

    [WIP] Backend-agnostic build system for scalable web projects.

    TypeScript 1

  2. dotfiles dotfiles Public

    My setup: A minimal design with a botanical-inspired theme.

    Shell 3 1

  3. tapable-tracer tapable-tracer Public

    Trace the connections and flows between tapable hooks.

    TypeScript 2

  4. stackholm stackholm Public

    Zero-copy stack-based context data management library.

    Python 4

  5. cx-tagged-template cx-tagged-template Public

    Class-name expressions in the style of concatenative programming.

    JavaScript 2

  6. revy revy Public

    Revision control system toolkit for Django models, built with stackholm.

    Python 8