Skip to main content

Challenges & Lessons

Building and shipping the platform as a two-person team surfaced a consistent set of pressures worth recording for anyone continuing the work.

Challenges faced​

  • Managing a large workload spanning design, development, testing, and deployment with only two contributors.
  • Integrating multiple user roles, each with different permissions and workflows, without letting complexity leak into every layer.
  • Handling backend logic, frontend interfaces, and database operations together within a fixed academic timeframe.
  • Balancing academic requirements against the realistic complexity of a production-style system.
  • Ensuring stability and usability while still meeting every functional requirement on schedule.
  • Debugging integration issues where the frontend and backend disagreed about data shape or timing.
  • Operating with limited human resources, so most tasks routed through a small team rather than being distributed.
  • Working within real financial constraints, which limited access to premium tools, hosting, and infrastructure.
  • Optimizing performance while relying on cost-effective or free-tier resources rather than dedicated infrastructure.
  • Maintaining steady progress through continuous testing and incremental delivery despite all of the above.

Why this matters going forward​

These aren't just historical notes — they directly motivate several items in Future Work: bringing on more contributors, distributing responsibilities, and moving off free-tier infrastructure all trace back to constraints the original team worked within rather than around.

  • Timeline & Budget for how these challenges showed up concretely in the schedule and spend.
  • Future Work for the roadmap these lessons inform.