Operations | Monitoring | ITSM | DevOps | Cloud

Gleb Lesnikov has been developing the system behind Dodo Pizza, an international fast-food chain, since joining the company in 2015. Over the years, the local business turned into a company running over 1,600 restaurants. When Dodo expanded rapidly, Gleb had to take key technical decisions that allowed the company to scale and succeed. Looking back, he reflects on the period when the company moved to a microservices architecture and explains how he managed to solve problems that could have caused the company to collapse.

Technical debt is one of those problems that's easy to understand in the abstract and genuinely painful to manage in practice. Every software team knows what it is - the accumulated cost of shortcuts, quick fixes, and decisions that made sense in the moment but created future work. What's harder to internalize is how quickly it compounds. McKinsey research found that technical debt accounts for approximately 40% of IT balance sheets, with companies diverting an additional 10-20% of their technology budgets just to manage it.

A trapeze artist does not perform the difficult part of the act without a net strung underneath. The net does not make the trick any easier. It makes attempting it survivable, which is the only reason anyone dares to let go of the bar. Jasiri Limited thinks about regression testing in much the same way. In a fast sprint, the temptation is to move quickly and assume nothing already working will break. The testing is the net that makes moving quickly survivable, and the company builds its approach by starting from the outcome and working backward.

TL;DR: The best AI app builder for small businesses in 2026 is Jotform AI App Builder for end-to-end workflow automation. Lovable is best for customer-facing web apps, Softr for portals, Glide for field operations, Adalo for native mobile apps, and Base44 for custom AI web apps. Small businesses rarely need an app in the abstract. They need a faster way to handle bookings, orders, client intake, approvals, inspections, payments, documents, and follow-up.

Software retention is usually described in the language of metrics: net revenue retention, logo churn, product adoption curves, health scores that turn green or red on a dashboard. All of it is useful. None of it is the reason a customer decides to stay. People renew contracts, but people also remember how a company made them feel at the three or four moments that actually mattered - the botched onboarding that someone personally rescued, the renewal that arrived with a real thank-you instead of an invoice, the support ticket answered by a name rather than a queue.