A naukri.com initiative
Medium
2w
8
Image Credit: Medium
The SkillForge Journal #3: From Blueprint to Living Code
- The article discusses the implementation of a Test-Driven Development (TDD) workflow in creating a SkillForge engine.
- TDD involves writing tests prior to writing code, enforcing clarity and correctness.
- The TDD process revealed a critical bug where a Skill object was passed instead of a skill_id string to a function, showcasing the importance of tests in catching errors.
- A fundamental decision was made regarding treating a 'category' of skills as the same type of object as a 'skill' itself.
- To maintain simplicity and power, categories were treated as skills by adding a boolean attribute to the Skill class.
- An abstract skill functions as a parent node, while a concrete skill acts as a completable task, enabling future complexity.
- The V1 implementation of the core Skill and SkillGraph classes has been completed through TDD-driven work.
- The foundation is verified, and the next step involves implementing graph traversal algorithms for the SkillForge engine.
- These algorithms will help answer critical user questions related to learning specific skills and potential progression paths.
- The blueprint has transitioned into code, laying the foundation for the next phase of development.
Read Full Article
Like
For uninterrupted reading, download the app