About me
Pavel Konoplev
Developer of websites and cross-platform apps
I build websites, web apps and cross-platform products for Web, Android, iOS, Windows, Linux and macOS. One person, one point of responsibility, from idea to release.
4+ years in development, from IoT telemetry to a platform for technical computing. I led the frontend of a 13-person team for 2 years and learned first-hand where the meaning of a task gets lost along a long chain.
“Broken telephone” kills projects: by the time a task passes through a manager, an analyst and a developer, half of the idea is gone. I keep the specification, architecture, code, tests and release in one pair of hands, so a single person is accountable for the whole result.
AI writes code to pass the tests and prepares drafts, while the specification, architecture and decisions stay with me, and I review every line. You get the speed of several developers and, in the end, the code and a specification repository that any developer can pick up without me.
Transparent timelines: I estimate honestly and commit to a deadline that I keep. A clear project handover with documentation and setup instructions, so onboarding takes hours, not weeks. And support after release, because for me launch is only the beginning of a product’s life.
01 / Timeline
Projects by year
- 2026
Website for the Greek community of Saint Petersburg
Paid subscribers get access to members-only content
- 2026
Workout tracking app
The user instantly sees a clear summary and progress for each workout
- 2025
Web application for building heating control
Full monitoring and remote control of a building’s heating supply
- 2024
No-code platform for calculations and modeling
Covers the full engineering cycle of calculation, modeling, demonstration and reporting, automating the work and speeding up computation
- 2023
Web app for monitoring power line breaks
Quick location of a line break and notification of the people responsible
02 / Approach
How I work with AI
AI speeds up writing code but does not replace engineering decisions. That is why the source of truth is the specification, not the chat history.
| Criterion | Vibe coding | My approach: AI engineering |
|---|---|---|
| Source of truth | The chat history with the AI and whatever came out of it | A specification in the repository — the code follows from it |
| Changeability a year later | Scary to touch: nobody remembers why it was done this way | Change the spec → design → tests → code. Decisions are recorded in documents |
| Tests | None, or added after the fact | Written before the code and verify the requirements in the spec |
| Handover to another developer | Only together with the author, and not always | Specification and documentation — a new developer gets up to speed in a day |
| Predictable timelines | “Almost done” for weeks | Estimates come from the spec, progress is visible in closed requirements |
- 01Specification
- 02Tests
- 03Code with AI
- 04Review and documentation