Building software while learning computer science fundamentals is a brutal balancing act, as developer Tanay Dwivedi discovered during his third week of focused upskilling. His recent log on DEV.to details a hectic period spent juggling freelance commitments with the Sanity AI Challenge, resulting in a mixed bag of completed projects and valuable lessons on time management and technical architecture.

The Sanity AI Challenge Hurdle

Dwivedi participated in the Sanity AI Challenge by building MoneyVerse, a financial literacy game for children. While the project went live, the development process exposed a critical architectural misunderstanding. He initially embedded Sanity Studio directly into the application framework, a pattern that documentation suggests should be avoided. He realized this structural error only minutes before the submission deadline, forcing a rushed pivot that highlights the importance of reading implementation guides before writing code.

Incomplete Ambitions and GitHub Repositories

The challenge's scope proved too ambitious for the available time. Dwivedi had planned a second submission called Budget-Bites, an app designed to help students meet health goals on a budget. Unlike MoneyVerse, Budget-Bites did not make the cutoff. The incomplete version remains available on his GitHub repository, serving as a public testament to the reality of unfinished side projects. This transparency is useful for other developers assessing the realistic time investment required for hackathon-style challenges.

Back to Basics With Algorithms and AI Concepts

Amidst the project crunch, Dwivedi also carved out time for foundational computer science study. He revised Design and Analysis of Algorithms, specifically tackling sorting mechanisms like Heapsort and Quicksort. He also addressed a common developer pitfall: superficial understanding of AI terminology. By diving into the Model Context Protocol (MCP), he sought to clarify its distinction from Retrieval-Augmented Generation (RAG) and other buzzwords like temperature and context windows, moving beyond performative knowledge to actual comprehension.

Key Takeaways

  • Architecture matters: Embedding Sanity Studio incorrectly can lead to last-minute panic during competitive submissions.
  • Scope discipline: Planning two projects (MoneyVerse and Budget-Bites) for a single challenge window resulted in one unfinished deliverable.
  • Foundational review: Revisiting core algorithms (Heapsort, Quicksort) alongside new AI protocols (MCP) provides a more robust skill set than chasing trends alone.

The Bottom Line

Dwivedi's week is a case study in the 'tutorial hell' trap versus real-world application. The fact that he shipped MoneyVerse despite the architectural scare shows resilience, but the abandoned Budget-Bites repo is a reminder that scope creep kills momentum. For devs, the lesson is clear: finish one thing perfectly rather than starting two things halfway.