-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reorganize repository #7
Comments
Moved all content to the "out-of-date" folder. Ignoring .class files
Added first problems: The Sorting and Searching problems.
Added description of the Sorting problem.
Added description of the Searching problem.
Good enough |
The proposed structured makes it harder to support correctness and performance tests. Therefore, I should be reorganizing the repository to focus on the code instead of documentation. I should be moving the documentation (problem descriptions) to a wiki page. Then I can propose a generic architecture to be implemented on different programming languages. So each language can have a dedicated directory avoiding mixing different source files. Again, I should be migrating to this new structure just to make it more flexible to work on tests and automation in the future. Now, the purpose is to understand the concepts and be capable of implementing them. Proposed structure:
|
This repository should be organized by problems:
The text was updated successfully, but these errors were encountered: