Should I introduce a controller layer to separate networking from game/player logic in a C server project?

I’m writing a multiplayer server in C using sockets and pthreads. The project is separated by responsibility: server.c/.h → networking (socket, bind, listen, accept, thread creation) player.c/.h...