Skip to content
View whoElseButUmar's full-sized avatar
🚀
Deploying
🚀
Deploying

Highlights

  • Pro

Block or report whoElseButUmar

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.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

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

Report abuse
whoElseButUmar/README.md

Umar — Omar Aderkaoui

AIByte Labs AIByte Labs on GitHub LinkedIn Email Omar

Good software should explain itself.

I’m Omar Aderkaoui, a software engineer, technical consultant, and founder of AIByte Labs.

I spend most of my time building products where the UI/UX and the underlying systems have to work well together. That usually means complex workflows, integrations, internal tools, and AI features that actually earn their place.

I care a lot about the small things that make software feel good to use: clear feedback, sensible defaults, useful error messages, good naming, and making sure people always know what is happening.

NOW / 2026

BASE         Morocco

ROLE         Founder & engineer

FOCUS       Product systems

DEFAULT   TypeScript

MODE          Design → Build → Refine

STANDARD Engineered for use

The workbench

INTERFACE

Things people see and use

React, Next.js, TypeScript, Tailwind CSS, design systems, and the small interaction details that make an interface feel finished.

SYSTEM

Things behind the UI

Node.js, Hono, Zod, APIs, integrations, and backend systems that stay understandable as the product gets bigger.

WORKFLOW

Things I use every day

pnpm, Git, GitHub, Figma, Cloudflare, testing, debugging, and enough documentation that I do not hate myself six months later.

Core technologies

Hono Zod Cloudflare


Operating principles

01

Make the next step clear.

People should not have to stop and figure out what the interface wants from them. The important action should be easy to spot.

02

Do not add complexity for fun.

Every dependency, abstraction, setting, and extra screen becomes something you have to understand and maintain later.

03

Think about what happens when it breaks.

The happy path is the easy part. Good software tells you what went wrong, keeps your work safe, and gives you somewhere to go next.

04

Leave things easier to understand.

Better names, fewer weird exceptions, clearer boundaries, and less hidden behavior. Small improvements like that add up fast.


GitHub activity

I don't read too much into GitHub stats, but they're still a nice way to see what I've been building and experimenting with over time.

Umar's GitHub activity


Behind the interface

What I care about

I want people to understand what they are looking at quickly, know what to do next, and trust that the software will behave the way they expect. On the code side, I try to leave things clear enough that someone else can jump in without needing me to explain every decision.

How I think about AI features

I usually start with the problem, not the model. If AI is not making the workflow meaningfully easier, it probably does not need to be there. I also like keeping the user in control and being clear about what the system is doing instead of pretending it is always right.

Things I tend to remove

Extra settings, unnecessary dashboards, vague labels, abstractions that exist too early, animation for the sake of animation, and features that only exist because somebody else has them.


Have something interesting to build?

I work on product engineering, platform integrations, applied AI, and the occasional weird idea that is worth trying.

contact@aibytelabs.com

aibytelabs.com ↗

Engineered for use

Popular repositories Loading

  1. whoElseButUmar whoElseButUmar Public

  2. waker waker Public

    Forked from workspaces-team/waker

    Rust

  3. killpnpm killpnpm Public

    JavaScript

  4. invader-tui invader-tui Public

    Reusable TypeScript TUI components for ANSI terminal interfaces, with a playable retro arcade demo.

    TypeScript 1

  5. killpnpm-site killpnpm-site Public

    Astro

  6. build-your-own-x build-your-own-x Public

    Forked from codecrafters-io/build-your-own-x

    Master programming by recreating your favorite technologies from scratch.

    Markdown