Skip to content

Blog 3

It was satisfying to witness the code functioning once it was deployed on Vercel. However, the most challenging and frustrating aspect of backend development for me was attempting to bring my conceptual ideas to life and realizing that many of them would be better integrated into other concepts rather than existing as independent entities. In the realm of backend development, I found myself discarding numerous concepts or amalgamating them with others.

One specific concept I regret not fully implementing was the notion of expiring resources for my skill score. Instead of incorporating this concept directly, I resorted to integrating the expiring aspect within the routes, which left me perplexed as to how I could incorporate it solely within the concept's code. I also found myself incorporating visibility within the post concept, although, in hindsight, I would have preferred to have it as a standalone concept. Unfortunately, I couldn't identify a way to implement visibility without creating an inherent dependency between posts and visibility, ultimately leading me to make visibility a state of a post.

In the end, the most exhilarating part of coding the backend was witnessing the tangible results and gaining a deeper understanding of how our conceptual ideas could materialize into a fully functional application. The process also enhanced my comprehension of the essential information that needed to be tracked for the application.