This project is intended to be useful in my development of other software.
The concept involves understanding the difference between the mindset of a programmer and a developer.
🚫 The use of artificial intelligence is prohibited in the development of this repository.
- pep errors
- uml management
- boilerplates
- datatracking
- software integrity
- file management
- tests
- copyright
- plagiarism
- devops
- metadata
- cybersecurity
there is a dedicated folder for each module containing readme file, design features and goals.
Inside each module's folder there is a minimal script. This script has the sole responsibility of performing some operation.
- The first task is to make this script work and minimally resolve some problem. THIS IS BASIC FEATURE CREATION
sample: The copyright module has a script that sends an image to the wikimedia database. This script should only be able to send one image.
- The second task is to make this same script work for another set of files, such as all the files in the images folder. THIS IS SCALING FEATURE.
At this stage, the creation of files, folder structure, the time in which the functions will have to operate, and synchronizations are being resolved.
- The third task involves presenting a feature visually. THIS IS HOW THE ARCHITECTURE OF THE PROJECT WORKS
At this time, the sending of data and urls routes - model- view - template - database relationships must be resolved
- The fourth task is to improve this feature. THATS'S DELIVERING VALUE.
At this point, something must be done to differentiate the process, such as automating, managing, viewing quantitative data in graphs, and concluding that there is a module that provides benefits.