Why We Built ErithX for Students to Track Real Coding Progress

Debjyoti Roy — Wed, 02 Sep 2026 09:34:49 +0000

ErithX started with a simple frustration.

As students, we had separate dashboards for LeetCode, GitHub, and Codeforces.

Each platform showed what we had done. But none of them helped us understand our complete progress.

We wanted a system that could observe our activity across platforms, compare it with our goals, and honestly tell us whether we were improving or simply staying busy.

That idea became ErithX.

The problem with separate dashboards

LeetCode shows the problems you solved.

GitHub shows your repositories and contributions.

Codeforces shows your contests and ratings.

All of these platforms are useful. But each one shows only a small part of your journey.

They do not look at everything together and ask:

Are you actually improving, or are you just collecting activity?

Students can solve problems every day and still avoid difficult topics.

They can make GitHub contributions and still build projects that teach them very little.

They can participate in contests and still repeat the same mistakes.

Numbers can show activity. They cannot always explain progress.

What ErithX does

ErithX is built for students and undergraduates who want to take their coding and development seriously.

You set a temporary goal, such as improving your problem-solving skills, preparing for product-based companies, building better projects, or following a balanced development plan.

The internal system then observes the activity connected to your profiles.

It analyses what it can and compares your current performance with your previous progress.

It looks for patterns in your:

Consistency.
Growth or decline.
Problem difficulty.
Contest participation.
Project activity.
Repeated habits.
Comfort-zone topics.

The purpose is not to show more charts.

The purpose is to help you understand what those activities actually mean.

A review at the end of the week

At the end of each week, ErithX gives you an honest review of your performance.

It can show when you are moving forward.

It can also point out when you are avoiding difficult topics, repeating familiar work, or moving away from your goal.

The system changes its behaviour based on your weekly performance.

When you are consistent, it helps you continue.

When you repeatedly ignore your goals, the feedback becomes more direct.

This is important because students do not always need more motivation.

Sometimes they need a clear view of what they are actually doing.

Why we built it

We wanted ErithX because we wished there were someone who could notice our progress throughout the week.

Someone who could look at our profiles, understand our goals, and suggest what we should focus on next.

A professional mentor can provide that kind of guidance, but even a short conversation requires time, availability, and money.

Existing platforms already provide valuable data.

ErithX tries to bring that data together and add context around it.

A problem count cannot tell you whether you are learning new concepts.

A contribution graph cannot tell you whether your project involves real engineering.

A rating cannot always explain why your performance improved or declined.

Progress needs more than isolated numbers.

You still have to do the work

ErithX is not meant to become the single source of truth for your learning journey.

It cannot replace your judgement.

It cannot build your projects, solve your problems, or make your decisions.

You still need to practise, think deeply, build real things, and push beyond your comfort zone.

ErithX is designed to help you stay aware of your direction.

It gives you a clearer weekly view so that you can decide what to do next.

This is only the beginning

We are building ErithX for students and undergraduates who want to stop guessing about their progress.

If you want to understand your coding and development activity more honestly, you can explore ErithX at erithx.dev.

The idea is simple:

Review your progress honestly, understand your patterns, and decide what to improve next.

What challenges do you face as a student while trying to stay consistent with coding, competitive programming, or project building?

We would love to hear your thoughts and learn what kind of feedback or support would actually help you make progress.