I am wondering what the best practices are for organizing a large C project are. It is a professional project, not an open source one, likely to be stored in a Git repository. How should things be sorted? Where should structures go? When should one use functions attached to structures versus functions that take a structure as a parameter?
In terms of laying out the files in the project, how should things come together? What naming conventions are most appropriate?
A mining company that builds a new mine in South Africa, an automobile manufacturer that creates a new truck design, and a pharmaceutical company that moves a new drug from testing to production are examples of projects that may consume more resources in a given year than any of the organization's operating divisions.
A project organization is a structure that facilitates the coordination and implementation of project activities. Its main reason is to create an environment that fosters interactions among the team members with a minimum amount of disruptions, overlaps and conflict.
You may be interested in answers to this question.
I think the best thing to do in your situation is just make sure your whole team is on the same page. This point can't be stressed enough. Have a standardized method of doing things and make sure your doing it.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With