開始是一種技能，讓軟件持續有用是另一種：認識 sudovijay

A launch tells you that someone built something.

What happens afterwards tells you whether they are willing to keep taking responsibility for it.

That is the part of software development I have come to appreciate most while working with Vijay Singh, known online and on GitHub as sudovijay.

He is the founder of 123sudo, a self-taught full-stack developer, and someone I call VJ.

I’m his co-founder, and I work closely with him. This is my perspective on his journey: how a student building websites became a developer maintaining products for people around the world, and what I have learned from working beside him.

He started before there was a career plan

VJ was born in Chaturani, a small village in Bageshwar district, in Uttarakhand’s Kumaon region. His school years took him to Meerut.

By Class 10, he was already building websites.

He later left college during his first semester and continued learning independently.

It would be easy to turn that into a familiar dropout story. I don’t think that would do his journey justice.

Leaving college did not automatically make him a developer. The years of learning and building afterwards did.

His route was unconventional, but the work still required the same things: understanding problems, learning technologies, making mistakes, and figuring out how to improve.

The meaningful part is not that he stopped attending college. It is that he did not stop learning.

A stack is a toolkit, not a product

Today, VJ works across web, desktop, and mobile.

His publicly listed toolkit includes JavaScript, TypeScript, PHP, Python, React, React Native, Next.js, Node.js, and Laravel, among other technologies.

That gives some context, but it does not explain the whole job.

A user does not experience a framework. They experience whether an installation works, whether a task makes sense, and whether the application helps them do what they came to do.

Working beside VJ has made that distinction clearer to me.

Knowing how to implement a feature is important. So is noticing where the experience becomes confusing, where an assumption fails, or where a seemingly finished feature still needs attention.

Those details are part of development, not something separate from it.

Different tools, different problems

At 123sudo, VJ’s work includes:

• 9xchat, an AI workspace bringing multiple models and persistent context together.
• 9xconvert, a practical file-conversion tool.
• 9xlyrics, another part of the growing portfolio.

More products are coming.

These are not interchangeable projects. Each has its own audience, constraints, and reasons to exist.

What connects them is a practical question:

Can we make this everyday task less frustrating?

That is one of the things I value about his approach. A product does not have to make a grand promise to be worth building. Helping someone complete a task with less friction is a meaningful outcome.

Privacy starts with what you ask for

Another principle VJ cares about is avoiding unnecessary demands for personal information.

That thinking informs the UID-based approach used in supported 123sudo products, reducing reliance on a conventional email-and-password account.

There is an important distinction here: a UID does not automatically make a service anonymous, and it does not mean that no data is collected. Those details depend on the implementation and the individual product’s privacy policy.

The design question still matters:

What information does this product genuinely need to function?

I think that is a useful question for any developer to ask before an onboarding flow becomes a collection of fields nobody has challenged.

It reflects the philosophy behind our work:

Software should solve the problem, respect the user, and get out of the way.

Building internationally means questioning your assumptions

According to our company’s account of its reach, VJ’s software has reached millions of people across more than 200 countries.

These are company-reported figures, not independently audited measurements.

For me, the significance is not only the number. It is the distance between where the work began and where it has travelled.

Someone using a product may have a different device, connection, or workflow from the person building it.

That creates a useful discipline: your own environment cannot be the only definition of “working.”

For a small team, every difference cannot be anticipated. But continuing to learn from those differences is part of the responsibility.

Leadership is also part of the work

I have seen VJ’s dedication extend beyond his own development tasks.

As his co-founder, I believe he has helped raise the quality of our work and helped the people around him grow in confidence and contribution.

That is my experience of working with him, not a quantified performance claim.

In a small team, development does not happen behind a sealed door. Technical decisions meet design questions, communication challenges, and user feedback.

The ability to bring those perspectives together matters.

VJ’s passion for building is visible in the products. His leadership is something I experience in the work we do together.

“I’m more of a private repo”

That line appears on his personal website, and it makes me smile:

“I’m more of a private repo.”

It captures his understated online presence. But it is not the whole person.

Away from software, VJ loves travelling and photography. He has visited multiple countries and enjoys meeting people and connecting with them along the way.

For someone with such a brief online introduction, he has a genuine interest in the people beyond his own world.

He also loves animals. From what I have seen, the affection is mutual.

His mother and family are deeply important to him, too. Those relationships belong in this story because they are part of the person I know, even if they never appear in a developer biography.

And yes, I find him charming and handsome. Consider that an openly biased co-founder observation, not an engineering benchmark.

You may already know his work

There is one product I have deliberately left until this point.

VJ is the builder behind 9xbuddy, including the 9xbuddy website.

If that name is familiar, you may have encountered his work long before you encountered his name.

It also explains why maintenance is such an important part of this story.

A media-download tool interacts with external websites and systems that change. Available formats differ. Previously working behaviour needs investigating again.

For a user, the interaction can be brief.

For the developer, the responsibility continues well beyond it.

That is the background to the newer work at 123sudo: not just experience launching products, but experience returning to them.

Small teams are not limited to small reach

I don’t believe a product used around the world must begin inside a large company.

One person can start something useful. A small team can develop it further. Neither guarantees success, but a modest starting point does not have to set the limit.

For me, VJ is an example of that possibility from India: a self-taught developer whose work has travelled far beyond where he began.

That does not mean he has done everything alone. It means that sustained work from a small team can have an international reach.

The lesson I take from his journey

When I think about VJ’s story, I come back to the difference between starting and continuing.

Starting a website in Class 10 mattered.

Continuing to learn mattered more.

Launching products mattered.

Continuing to maintain them mattered just as much.

There are more products ahead, more things to understand, and more work to improve. His journey is still unfolding.

If you know him only as sudovijay, I hope this gives you a fuller introduction to the person behind the handle.

Explore his work through sudovijay on GitHub and 123sudo.com.

Disclosure: I’m a co-founder of 123sudo and work closely with VJ. This article reflects my personal perspective. Biographical details and reach figures are provided by us; reach figures have not been independently audited.