Skip to content
Harry Curtis edited this page Feb 9, 2024 · 13 revisions

Introduction

Rebuilding Arithmetic Speedrun is a personal project. By the end, I intend to have a more intuitive understanding of how to develop software efficiently and effectively, alongside an awareness of a range of common software development methodologies and principles. The project is exploratory. That is, many factors are not known from the outset, and I intend to document how I approach each one as I progress. My decision-making process will be based on an analysis of the feasibility of each feature, and the likelihood that the understanding utilised to develop the feature could be reapplied to future projects. For example, utilising React, a framework that many companies work with, would be preferable to Svelte, a less common framework. Once I have decided on the requirements for the final application, I will add specific, measurable milestones to track my progress. As I go forward, I intend to keep a log on this wiki of the decisions that I have made, and my reasoning for each one. If you are reading this, and you have constructive feedback, a feature suggestion, or would like to contribute to the project, please start a new discussion in the Discussions tab.

Purpose of the Wiki

List of Contents

  1. Project Overview
  2. Requirements Analysis
  3. Design
  4. Development Methodology
  5. Technology Stack
  6. Version Control
  7. Coding Standards and Practices
  8. Testing
  9. Deployment
  10. Security Measures
    1. Security practices and tools used
    2. Compliance with security standards
  11. Performance Optimization
    1. Techniques and tools used for optimization
    2. Pre and post-optimization metrics
  12. Challenges and Solutions
    1. Major challenges faced during the project
    2. Solutions implemented to overcome these challenges
  13. Lessons Learned
    1. Technical and project management insights gained
    2. What would be done differently in hindsight
  14. Future Directions
    1. Planned features or improvements
    2. Technical debt to be addressed
  15. Appendices
    1. Glossary of Terms
    2. References and Resources
    3. Acknowledgments

Clone this wiki locally