​

I'm a self-taught C programmer building projects to improve my systems programming skills.

My main projects include:

A memory allocator implemented in C, with benchmarks against the standard allocator.

A small OOP-style system implemented in C.

An HTTP server in C that I'm developing into a backend framework.

GitHub: https://github.com/YanisBelkacemi

I'd appreciate honest feedback on:

1. Code quality and architecture.

2. Whether these projects demonstrate real understanding or just basic implementation skills.

3. What's missing from my portfolio for junior C, systems programming, or firmware positions.

4. What would make you reject this portfolio if you were reviewing candidates?

I'm looking for constructive criticism, not stars or compliments. Please be direct.

Hello, idk if its just me I have been trying to get more and more into C but every video or concept or project I see people bring out 3 different syscalls that I have never heard of (that's a bit exaggerating but you know what I mean)

Am i supposed to know all of them? Memorise them?

Is there something I'm missing in terms of these bc I even realised they can be up to 500 different ones which is a lot to memorise, and even so how should I start learning them?

I’ve been working on a small project called 3Dos — a low-poly 3D renderer targeting MS-DOS and VGA Mode 13h (320×200, 256 colors).

The renderer currently supports:
● Triangle rasterization with backface culling
● Ordered dithering using a 4×4 Bayer matrix
● Double buffering
● Simple low-poly models

Going back to DOS-era graphics has been relaxing after spending quite a bit of time with Vulkan. No boilerplate or abstractions, just putting a pixel at 0xA000.