How Senior Devs Organize Their C Projects
From Amateur to Pro: 3 Layers of Separation for Your Codebase Does your project directory look like a flat pile of files? You know the look: logic, headers, tests, and binaries all fighting for space in one folder. In a university project, this is fine. But in a professional environment, this is called Source Pollution.
Why Your Code Looks Amateur (Even When It Works)
Have you ever finished a coding project where the features worked exactly as intended, but you still weren’t proud of the result? You look at the code and feel that something about it looks “amateurish,” even if you can’t quite put your finger on what would make it professional. When I graduated from university, I
Grep 101: Search Your Code Like a Senior Dev
How to Search Your Entire Codebase with Grep Say you’re having an issue with your program and it’s having a connection issue. Usually, like we would in a browser or in any other file, we can just do Ctrl+F in our file of choice and type in something like connection. That lets us see where
