So I have this idea for an amazing C program, but I've never seriously been through the traditional, professional development process (liaising with developers/users; sharing source on git, mercurial, svn, sourceforge; standards & portability; licensing; documentation; bug tracking; packaging & distribution etc.)
How do I get started? I haven't coded the program yet, but I expect it to be usable within a week.
Stacey Warren - Expert brainly.com
Hey! We 've verified this expert answer for you, click below to unlock the details :)
At vero eos et accusamus et iusto odio dignissimos ducimus qui blanditiis praesentium voluptatum deleniti atque corrupti quos dolores et quas molestias excepturi sint occaecati cupiditate non provident, similique sunt in culpa qui officia deserunt mollitia animi, id est laborum et dolorum fuga.
Et harum quidem rerum facilis est et expedita distinctio. Nam libero tempore, cum soluta nobis est eligendi optio cumque nihil impedit quo minus id quod maxime placeat facere possimus, omnis voluptas assumenda est, omnis dolor repellendus.
Itaque earum rerum hic tenetur a sapiente delectus, ut aut reiciendis voluptatibus maiores alias consequatur aut perferendis doloribus asperiores repellat.
I got my questions answered at brainly.com in under 10 minutes. Go to brainly.com now for free help!
I hope that it will be super portable as well, able to function on every windows, unix, os ten, playstation: anything that implements a C standard library :-D
also, what's the best way to go about designing a program, laying out it's specifications and then coding it up from those specifications?
You can start a development process in many different ways, but if you would like to start in a profissional way, you can read more about ALM (Application Lifecycle Management).
Not the answer you are looking for? Search for more explanations.
So, the best word of advice that I can give you is not to over-think things. Start simple, work up into complexity. There's can be a lot involved with Application Lifecycle Management or very little at all. :)
Out of the list of topics you'd listed, I'd recommend making version control a priority.
Version control is a valuable skill that was seeded in application management and has grown into many aspects of my digital life. It has revolutionized the way I think about information and how information should be shared and delegated with others. I would suggest learning about it for the sake of knowing it.
I just build programs with no formal plan. I call it creativity by simplicity.....I might not crank out programs in 3-4 days usually I build a program with 1 6000+ line class in 30 days and occasionally 2 months the longest I ever spent on a program was 3 months. This takes into account that you have allot of classes already built to work with. I spent around 5 years building and compiling code snippets and classes so I can rapidly develop applications in multiple languages. So if you think you are going to build a complex program in a week you are so wrong :) good luck to you.
speaking of version control SVN servers are good thing to use.....saved me more than once.
I hope I will be a O(log(N)) guy someday :(
This C project will be my first step up that route! :) time to learn what version control is...