// the take
A toy student-records CRUD app in C that uses flat text files instead of a database, with four hardcoded role tiers (Admin/Staff/User/Guest) gating which menu functions a logged-in user can call. It's a learning project for someone picking up C file I/O and basic access control concepts, not something meant to run anywhere real.
Role separation is enforced cleanly at the menu level — each role gets its own function (adminMenu, staffMenu, etc.) rather than one giant switch with permission checks sprinkled in, which is actually a reasonable way to teach the concept. The CRUD operations map 1:1 to simple file operations (append for add, full scan for display/search, rewrite-on-delete), which is honest about what's happening under the hood rather than hiding it behind abstractions a beginner wouldn't understand yet.
Credentials are stored and compared in plaintext in credentials.txt — no hashing, no salting, so anyone who opens the file has every password. Delete/update work by rewriting the entire file on each operation, meaning no partial-write protection: a crash or power loss mid-rewrite loses the whole dataset, and there's no locking so two concurrent users will corrupt each other's writes. Search and lookups are linear scans over the text file with no indexing, so this doesn't survive past a toy dataset size. The space-delimited format (`roll name mark`, `username password role`) has no escaping, so a name or password containing a space silently breaks the parser — there's no schema validation on read.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →