technical_shivam

@technical_shivam

"Tech enthusiast & Engineer from Lucknow. Solving complex problems with code. I joined VTogether to build in a creator-first ecosystem. 🚀"

LINKS ARE AT THE BOTTOM

Latest Updates

meet my friend...

Feb 16

enjoying with friends !!

Feb 16

My Journey

Milestones and updates

February 25, 2026

Here is another aspect of Shivam’s journey. To give you a completely different writing style, I’ve shifted the tone from a nostalgic, sentimental reflection to a gritty, architecture-focused "devlog" or startup manifesto. This version focuses on the brutal reality of system design, the technical hurdles of building a startup, and the exact mechanics of creating a fair platform. The Architecture of Equity: Hardcoding a New Ecosystem Let’s drop the romanticized idea that software engineering is just sitting in a dark room having "eureka" moments while typing furiously on a mechanical keyboard. The truth is, once you move past building cute local utilities and step into the arena of scalable systems, the game fundamentally changes. It stops being about whether the code compiles and starts being about who the code serves. When you look at the legacy tech giants, their infrastructure is a marvel of modern engineering, but it’s inherently designed as a black box. The algorithms that dictate reach, and the backend processes that calculate creator payouts, are intentionally obfuscated. As an engineer, looking under the hood of the modern internet made me profoundly cynical. I realized that big tech doesn’t have a "glitch" in how it treats creators; the exploitation is a feature, perfectly optimized at the database level. That realization was the catalyst for the real work. When my co-founder and I sat down to map out the backend architecture for vTogether, we weren't just arguing about server costs, latency, or whether to use a relational database. We were arguing about philosophy. We knew that if we wanted to build a genuinely transparent social media platform, we couldn't just promise fairness in our Terms of Service; we had to hardcode it directly into the system's DNA. The hardest engineering challenge wasn't building a sleek user interface or optimizing the media delivery network. It was designing the revenue-splitting engine. We spent weeks architecting an automated ledger system that could accurately, transparently, and instantly route ad revenue to the creators who actually generated the traffic. When you are building a system where a creator's livelihood depends on your mathematical precision, a dropped query or a miscalculated floating-point number isn't just a bug—it’s a breach of trust. Building this wasn't glamorous. It was a grueling cycle of drafting schema migrations, load-testing API endpoints until the servers choked, and drinking terrible instant coffee at 3:00 AM while trying to patch security vulnerabilities. There is no applause when you successfully optimize a background job to run 200 milliseconds faster. But that unseen labor is exactly what structural change requires. Today, my role isn't just to write features; it's to maintain a digital infrastructure that proves a different model is possible. I document my builds and share my deployment strategies openly because I want other developers to see that we don't have to blindly inherit the architectures of the past. We can build ecosystems where the value flows back to the community, bypassing the corporate gatekeepers entirely. Code is law, and for the first time, we get to write the legislation.

Privacy Terms

February 16, 2026

My Journey from a Curious Kid to a Systems Engineer I grew up in a household where "breaking things" was just the first step of learning how to fix them. While other kids in my Lucknow neighborhood were out playing cricket, I was usually huddled in the corner of our living room with a screwdriver, taking apart a broken radio or an old alarm clock. I wanted to see the hidden gears, the soldered circuits, and the silent logic that made the world work. My parents were patient, but I think they were mostly just relieved when I eventually learned how to put the devices back together without having "spare parts" left over. This innate curiosity was the spark that eventually led me into the world of Software Engineering. The transition from physical hardware to abstract code felt like moving from a small room into an infinite universe. When I wrote my first "Hello World" program in high school, I didn't just see text on a screen; I saw the potential to build tools that could solve real-world problems. However, the path to becoming a professional engineer was far from a straight line. During my university years, I struggled deeply with the theoretical side of computer science. I found the dry textbooks and ancient assembly languages incredibly disconnected from the exciting, fast-paced tech world I saw online. There was a moment in my second year where I seriously considered quitting, feeling like I just wasn't "smart enough" for the high-level mathematics required. Everything changed when I stopped trying to learn for the grade and started learning for the "build." I decided to create a small app that helped local street vendors in Lucknow track their daily sales—something simple but functional. For the first time, the code mattered. I wasn't just solving a textbook problem; I was building a solution for a neighbor. This project taught me more than any lecture ever could. It taught me that engineering is 10% syntax and 90% empathy and persistence. I spent long nights debugging database connections and learning how to optimize queries, fueled by the thrill of seeing my work actually being used. After graduating, I entered the corporate tech world, but I quickly realized that many platforms are built for profit first and users second. I saw how algorithms could hide great content and how creators were often left in the dark about their own data. This is what eventually drew me to vTogether. As an engineer, I value transparency, clean architecture, and systems that empower the individual. I wanted to be part of a community that wasn't just another walled garden, but an open ecosystem where everyone keeps what they earn. Today, my journey as technical_shivam is about more than just writing code; it’s about sharing the process. I use this platform to document my experiments, from building automation scripts to exploring the latest in decentralized tech. I’ve learned that being a "technical" person doesn't mean you have to be robotic. It means you have the tools to build a better, more transparent world for everyone. Whether I'm refactoring a messy block of code or designing a new feature, I’m driven by that same kid who just wanted to see how the radio worked. The only difference is, now I'm building the radio.