Wrong Mansur
Ir al canal en Telegram
software engineer @ payme https://github.com/MansurIsakov https://www.linkedin.com/in/mansur-isakov/
Mostrar más177
Suscriptores
+224 horas
+47 días
+430 días
Carga de datos en curso...
Canales Similares
Nube de Etiquetas
Sin datos
¿Algún problema? Por favor, actualice la página o contacte a nuestro gerente de soporte.
Menciones Entrantes y Salientes
---
---
---
---
---
---
Atraer Suscriptores
julio '26
julio '26
+6
en 0 canales
junio '26
+2
en 0 canales
Get PRO
mayo '26
+3
en 0 canales
Get PRO
abril '26
+1
en 0 canales
Get PRO
marzo '26
+1
en 0 canales
Get PRO
febrero '26
+2
en 0 canales
Get PRO
enero '260
en 0 canales
Get PRO
diciembre '25
+2
en 0 canales
Get PRO
noviembre '250
en 0 canales
Get PRO
octubre '25
+2
en 0 canales
Get PRO
septiembre '25
+4
en 0 canales
Get PRO
agosto '25
+8
en 0 canales
Get PRO
julio '25
+4
en 0 canales
Get PRO
junio '25
+8
en 0 canales
Get PRO
mayo '25
+2
en 0 canales
Get PRO
abril '25
+6
en 0 canales
Get PRO
marzo '25
+3
en 0 canales
Get PRO
febrero '25
+3
en 0 canales
Get PRO
enero '25
+9
en 0 canales
Get PRO
diciembre '24
+4
en 0 canales
Get PRO
noviembre '24
+5
en 0 canales
Get PRO
octubre '24
+4
en 0 canales
Get PRO
septiembre '24
+2
en 0 canales
Get PRO
agosto '24
+5
en 0 canales
Get PRO
julio '24
+13
en 0 canales
Get PRO
junio '24
+4
en 0 canales
Get PRO
mayo '24
+8
en 0 canales
Get PRO
abril '24
+6
en 1 canales
Get PRO
marzo '24
+30
en 0 canales
Get PRO
febrero '24
+40
en 0 canales
Get PRO
enero '24
+248
en 0 canales
| Fecha | Crecimiento de Suscriptores | Menciones | Canales | |
| 23 julio | +1 | |||
| 22 julio | +2 | |||
| 21 julio | +1 | |||
| 20 julio | +1 | |||
| 19 julio | 0 | |||
| 18 julio | 0 | |||
| 17 julio | 0 | |||
| 16 julio | 0 | |||
| 15 julio | +1 | |||
| 14 julio | 0 | |||
| 13 julio | 0 | |||
| 12 julio | 0 | |||
| 11 julio | 0 | |||
| 10 julio | 0 | |||
| 09 julio | 0 | |||
| 08 julio | 0 | |||
| 07 julio | 0 | |||
| 06 julio | 0 | |||
| 05 julio | 0 | |||
| 04 julio | 0 | |||
| 03 julio | 0 | |||
| 02 julio | 0 | |||
| 01 julio | 0 |
Publicaciones del Canal
| 2 | I want to share a bit about what I’ve been working on outside of my main job.
Over the past few months, I’ve been building an project called Concierge - a platform for residents and property management teams in residential complexes.
The idea didn’t come from “let’s build another startup.” It came from my own experience of buying an apartment, going through renovation, and then living in a residential complex.
I started noticing how many everyday processes around the building still live in Telegram chats, personal messages, and manual agreements like “just text the manager.”
Want to book a shared space like a chaykhana or BBQ zone? You message someone.
Need the security or technician’s contact? You search through old chats.
Trying to find an important announcement? You scroll Telegram.
Need to connect your apartment or solve a building-related issue? Again, personal messages.
It works somehow, but as the number of residents, apartments, and shared spaces grows, it quickly turns into manual chaos. And it’s not only inconvenient for residents, it also puts a lot of pressure on the property manager, who has to deal with dozens of repetitive questions, requests, and small operational tasks every day.
With Concierge, I want to bring these processes into one clear and convenient product.
The first working version is already built:
— a web app for residents inside Telegram Mini App;
— an admin panel for residential complex managers;
— a product landing page;
— a backend service that powers both the app and the admin panel.
In the first version, I focused on the core scenarios: authorization, apartment ownership verification, resident management, booking shared spaces, announcements from the management company, and important contacts in one place.
For me, it was important not to build just a nice-looking app for residents, but to look at the process from both sides.
On one side, residents want to solve everyday issues quickly, without endless messages and searching through chats. On the other side, managers need a proper tool where they can clearly see who lives in which apartment, who submitted an access request, which shared spaces are booked, what announcements are published, and what currently needs attention.
The first pilot I want to launch is in my own residential complex. This is where I personally noticed the problem and decided to try turning it into a product.
Right now, I’m polishing the product, talking to potential users, and preparing for the first pilot.
I’d be happy to hear any feedback, especially from people who live in residential complexes, work with real estate, property management, or just enjoy discussing product and startup ideas.
https://landing.concierge-service.uz/ | 269 |
| 3 | Ребята, привет!
Хочу показать вам проект, над которым я сейчас работаю в свободное время.
Я делаю сервис «Консьерж» - это приложение для жителей ЖК и админка для менеджеров дома. Идея появилась после того, как я сам столкнулся с жизнью в ЖК: заявки, объявления, бронирование общих зон, контакты, вопросы к менеджеру - всё обычно разбросано по Telegram-чатам и ручным сообщениям.
Я хочу собрать это в одном удобном месте.
Сейчас уже есть рабочая версия: Telegram Mini App для жителей, админ-панель, backend и лендинг. Первый пилот хочу попробовать запустить в своем ЖК.
Буду рад, если вы посмотрите концепт / скрины / демо и честно скажете, что думаете: понятно ли, полезно ли, что выглядит сильным, а что стоит улучшить.
Мне сейчас очень важен живой фидбек, особенно от людей, которые сами живут в ЖК или сталкивались с такими бытовыми вопросами.
https://landing.concierge-service.uz/ | 1 |
| 4 | DevOpsDays Tashkent 2026
https://youtube.com/playlist?list=PLfxac9SJZ5QZfUnEkLscL6PbL3vs7HsgT&si=ZXajIe7lzKdXC63I | 262 |
| 5 |  Sin texto... | 279 |
| 6 | the second concept i liked is Tracer Bullets.
most LLMs tend to code horizontally. they build layer by layer: first models, then services, then UI, and only at the end you see if everything actually works. it can feel productive, but the problem is that feedback comes too late.
tracer bullets push you to do the opposite: build a small vertical slice that goes through the whole flow. not the final version. not the perfect architecture. just one thin path that works end to end.
for example: one screen, one API call, one database operation, one result back on the screen.
what i like about this idea is that planning becomes more grounded. you are not trying to guess everything in advance. you quickly see the real problems: missing requirements, unclear data, wrong assumptions, integration issues.
after that, it is much easier to plan the next steps.
i think this is especially useful when working with AI coding agents. instead of asking an agent to build a big feature at once, i prefer to start with a tracer bullet first.
small working flow → feedback → improve.
it keeps the agent on track, and keeps me in control of the direction.
here is promt example by Matt:
## Tracer Bullets
When building features, build a tiny, end-to-end slice of the feature first, seek feedback, then expand out from there.
Tracer bullets comes from the Pragmatic Programmer. When building systems, you want to write code that gets you feedback as quickly as possible. Tracer bullets are small slices of functionality that go through all layers of the system, allowing you to test and validate your approach early. This helps in identifying potential issues and ensures that the overall architecture is sound before investing significant time in development. | 277 |
