About Ayush Basak

Ayush Basak is a CTO, systems architect, and software engineer based in Kolkata, India. He works on backend platforms, database engineering, distributed systems, and production AI. He currently builds AI-enabled sales infrastructure at Saleslyt and companion software for the connected fitness product Myotrek.

I publish as ayushworks. You can follow my code on GitHub, my engineering discussions on LinkedIn, and my videos and talks.

Start with the work

My writing focuses on the point where a design meets production: retries that multiply load, schema changes that outlive a deployment, and AI systems that need explicit limits.

For product context, see Saleslyt and Myotrek in my work, the project archive, and field notes.

My story

I did not begin as a prodigy

For years, I disliked Computer Science. It felt abstract, cold, and disconnected from anything I wanted to become. I was not the person who had been coding since childhood, and I do not want to rewrite the beginning to make the present look inevitable.

The direction changed because of a person. I admired her discipline and wanted to become capable enough to keep up. The immediate reason was personal; the consequence became permanent.

An exam on sequential circuits was the first real turn. I studied something I thought I could not understand, did well, and discovered a more important fact than the score: difficulty was not a verdict. It was something I could stay with.

Then came networking, C++, programming, software architecture, and systems. Somewhere in that progression, borrowed motivation became my own curiosity.

The complete account is in Life Is Beyond Binary. I keep it public because an honest trajectory is more useful than a polished origin myth.

From code to responsibility

Writing code taught me how to make a machine do something. Owning systems taught me to ask harder questions: Who absorbs the failure? Which data is authoritative? What happens during a partial deployment? Can the team explain the system at 3 a.m.? Does the technology create value, or merely activity?

Today I work as a CTO and systems architect. At Saleslyt, I work on AI-enabled sales infrastructure. For Myotrek, I build software around a connected physical product. My independent work spans healthcare microservices, offline payments, smart-agriculture infrastructure, network analysis, and accessibility.

The technologies vary. The questions repeat: what must remain true, where does complexity belong, how will the system fail, and what evidence will tell us the design is working?

Why I publish

Private understanding helps once. Clear public writing can help repeatedly.

This site is where I turn implementation experience, research, mistakes, and unresolved questions into reusable material. The engineering notes are compact decision tools. The papershelf records research worth carrying into production. The blog is for ideas that need room to be argued properly.

The standard I am trying to keep

  • Useful work should leave people with more capability than they had before.
  • Technical depth matters when it improves a consequential decision.
  • Ownership includes the failure path, not only the launch.
  • Architecture should reduce ambiguity, not decorate it.
  • A career should compound judgement, not merely accumulate activity.
  • Teaching is one way to test whether understanding is real.

Still becoming

I am still building, revising assumptions, and learning which problems deserve years of attention. I expect this page to change as the evidence changes.

For the technical record, visit Work and Projects. For the ideas shaping it, browse my Bookshelf, Papershelf, and Movies.

You can find me on X, LinkedIn, YouTube, and GitHub, or email basakayush942@gmail.com.

>