1gr14/igrich/
  • Menu
    • Home
    • Start0
    • Support
    • Education
    • Blog
    • Author
  • Community
    • Discord
    • Telegram
  • Open Source
    • Point0
    • Route0
    • Error0
    • Flat
  • Account
    • Sign In
    • Sign Up
1gr14/igrich/
Building open-source software for the glory of the Lord Jesus Christ ☦️
With love for developers of all backgrounds around the world ❤️
Terms of ServicePrivacy PolicySergei Dmitriev 2026 😎

Sergei Dmitriev

I'm a fullstack TypeScript developer. I'm 32 years old. 18 years of commercial experience, the last 9 focused on startups — that is, on building products from scratch. More often I worked alone, or as a team lead over a team of a couple of people. There was a period when I worked as a backend developer, including on high-load projects, but that is more the exception.

Mostly I built SaaS products. More often web, but I also made mobile and desktop apps. From clients I usually got a high-level description of the task — something like "We're making a service for finding freelancers and working with them"; the details important to the client I clarified with him, the unimportant ones I figured out myself. After that I set my own tasks, did them myself, demoed them to the client myself, closed them myself, and brought in the specialists I needed when necessary (more often designers, less often developers).

From the very start of building turnkey multi-user projects, I wanted to hone this skill in itself, to be able to create quickly, with quality, and at scale. I paid special attention to my own DX, to enjoy the work, improving my groundwork with every project I built.

Three years ago I decided I had reached a sufficient level in the skill of building projects from scratch to solve the tasks I set. I decided to capture this professional milestone by releasing a fullstack project-development course: 140 lessons and 28 hours of video. I tried to sell it, got tired of it, gave it away for free, and got more than 10,000 happy participants.

Right after that I realized my approach to building projects from scratch could and should get even better. Instead of creating reusable groundwork, I decided to start building open-source libraries, to eventually assemble the perfect boilerplate for starting new projects. And I could not build the perfect boilerplate on existing frameworks (Next.js, React Router, tRPC). In the end I understood that all my groundwork was turning into crutches to work around the limitations of existing frameworks and libraries. That was the dead end of the chosen path. I decided to build my own framework, because now I had real grounds for it, and I had honestly tried all the other options.

Ten months later I finished building the Point0 framework and several other libraries. Around this framework I was finally able to assemble a boilerplate that suited me — that boilerplate was named Start0. There is still plenty to work on in both the framework and the boilerplate, but the foundation is already in order and ready to scale.

I'll keep building open-source libraries and developing my framework and boilerplate. There are still many ideas that inspire me and could be useful to the developer community.

Plans

I'm going to build my own SaaS products, because that will help develop both the framework and the boilerplate with every new SaaS I launch. At the same time, I can't say I'm good at business or marketing, so I definitely can't count on these projects' financial success. But they will certainly let me grow as a developer and develop the open-source solutions I use in them.

I plan to make SaaS products first of all for developers, since that is the only audience I truly understand and belong to myself. At the same time, I'm thinking of building SaaS in other areas too — but rather not to launch them myself, more as ready-made code that anyone wanting to launch a similar SaaS could buy. That is, to create something like a showcase of projects.

I'd be glad to collaborate with businesses that want to build their own SaaS products. I'm not too fond of the idea of working for a fixed hourly rate — I prefer to price the result and work in iterations. If you'd like to collaborate, I'd be happy to discuss possible terms.

The story

To describe my background, I think a timeline of my career history fits best.
2008–2013

Websites from age 14

From age 14 I built turnkey websites: design, markup, CMS setup. It is from 2008 that I count my commercial experience — that is how it comes to 18 years. Because at 14 I had roughly 3 commercial orders a year, and it grew from there.
jshtmlcssphpmysqlmodx
2013–2017

Into a web studio

By this point I had built about 50 turnkey websites — I do not remember exactly, but that is the order of magnitude. As a freelancer I could no longer grow as a developer, so I decided to take a job at a web-development studio to see how the world of professional development is actually arranged, and my age already allowed me to be officially employed. I worked at the firm for 2 years and learned a great deal from both colleagues and bosses. Then I freelanced for another year and realized that now I did not want to build ordinary websites — I wanted to build multi-user projects, essentially SaaS.
jshtmlcssphpmysqlmodxrubyruby-on-rails
2017–2018

A platform for online courses

One of my former clients wanted to build a service for running online courses: adding courses, checking homework, communicating with curators, analytics, and so on. A real SaaS project. I did not yet know how to build multi-user projects, but thanks to the trust built earlier the client decided I would manage, and I was very grateful for his trust. I lacked the experience to deliver this project alone. I hired two programmers (one backend, one frontend). I set their tasks, learned from them, and mostly wrote the frontend code myself. In the end everything worked, but the client decided not to launch the project for his own business reasons. Still, the client was very happy with our work and recommended our team to his friend, to build his project.
reactgraphqlnode.jsmongodbdocker
2018

A marketplace for crypto miners

The next client ordered from us a marketplace for wholesale sales of products related to the cryptocurrency industry (selling immersion baths, computing power, and so on). We worked as the same team for 7 months, and then the client ran into problems in his main business and abruptly stopped the collaboration. I had ended up with debts to the team (I paid them monthly), so I had to take a loan to settle them, and I got a little down. The team broke up and I was left alone, but by then I confidently commanded our tech stack and felt I could handle any project on my own — and, if needed, assemble a team again.
reactgraphqlnode.jsmongodbdocker
2018–2024

BinKing

In parallel with these events, the idea for my own small startup, "BinKing", came to me. I decided to build a service that determines a bank's logo, colors, phone, and more by card number. This is needed to lay out a payment-card form as responsive as the ones in mobile banking apps, so that as you type the number you see the bank's brand right in the form. The project was open-source at first, then became a closed project with a paid API, and then closed entirely, since it brought almost no profit. It was my first startup, and it taught me a great deal.
reactgraphqlnode.jsmongodbdocker
2019

A freelance exchange

When I was announcing one of the versions of my startup, I wrote at the bottom of the announcement that I was looking for clients for SaaS development. A client from England turned up who wanted to build his own freelance exchange. I had no team, so I decided to build this project myself. I drew the prototype myself to agree on the vision of the future product with the client. My tech stack was well honed and development went smoothly. Somewhere in the middle I hired a second programmer to help me build faster. This project launched successfully — I built a web service and an iOS app. By the way, this same client later took a share as product manager in my BinKing project. The client was very happy with me and recommended me to his friend from Estonia, who became my next client.
reactgraphqlnode.jsmongodbdocker
2020

A worker exchange for builders

Next I built a service for exchanging workers among construction companies. Again I drew the prototype myself, took it into development, and in parallel handed it to a designer for the visuals. I built this project alone too, bringing in a markup developer at the final stage so I would not have to do it myself. I delivered the project, but unfortunately the client ran into problems in his main business and never got around to launching it.
reactgraphqlnode.jsmongodbdocker
2021

A niche CRM

Then no one came through word of mouth, and I do not know how to look for clients myself, simply because I had never done it. I had free time, so together with a marketer friend I decided to make a niche CRM for stretch-ceiling installers. Everything got built, but the choice of niche turned out to be extremely questionable. In short, we essentially never launched it.
reactgraphqlnode.jsmongodbdocker
2022–2023

Health Samurai

I was tired of building projects "for the drawer", and I decided I wanted to see how work is organized in relatively big companies, so I joined Health Samurai as a fullstack developer. The company built software in the medical field for the US market. I worked on a project for sending notifications to clinic patients. I spent a year and a half here and grew a lot, both in certain technologies and in approaches to building high-load applications in general. I was glad to work there and they were glad to have me, but then our firm's client replaced our team with a team from India, and I left the firm.
typescriptreactnode.jspostgresqldocker
2023–2024

My fullstack course

Analyzing my experience in startups and at my last job, I realized I had my own vision of how to build products from scratch, so I created a fullstack development course: 28 hours of video and more than 140 lessons. I tried to sell it, but that was hard and not interesting, so I released it for free and got more than 10,000 happy participants.
typescriptreactnode.jstrpcpostgresqldocker
2023

5 billion pushes a day

Then I worked as a fullstack developer on a project for delivering web-push notifications. Probably the biggest high-load of my career — about 5,000,000,000 pushes a day. I did not build this project from scratch; I only helped it grow.
typescriptreactnode.jspostgresqlgraphqldocker
2022–2025

Side projects

In parallel with my main job, as a solo developer I managed to build several more small projects from scratch. A habit-tracking mobile app, a Shopify plugin for SEO optimization, a CRM for managing sunbeds in Montenegro, a video-dubbing service.
typescriptreactnode.jstrpcpostgresqldocker
2024–2025

Backend for mobile apps

Next, at the same firm that ran the web-push delivery, I moved to another direction where we built mobile apps, but as a backend developer. I built a chat with an AI assistant, a tracker for medications taken, a calorie tracker, and other projects.
typescriptnode.jspostgresqldocker
2025–2026

Point0 and Start0

I felt that I had stopped growing as a developer, and that I could no longer develop my own groundwork for building projects from scratch within existing frameworks and libraries. I decided to build my own framework. I was tired of combining it with my main job. I quit. I built the Point0 framework and the Start0 boilerplate. No money, no job — but I am happy, and I believe the best is yet to come. Thank God for everything!
typescriptbunreactpoint0