Author name: admin

Reading Time: 3 minutesVezha Issue #039: “Risk Control in the Long Development Cycle”.What did the team change this week, what effect did it have in production and what are we doing next.

Reading Time: 3 minutesVezha Weekly Entry #038: “What does ‘enterprise-ready’ mean in our case.”We explain what worked in practice and how it affected the stability of the service.

Reading Time: 3 minutesIssue #037 on Vezha: “Quality standards before a major release”.Briefly about the changes of the week, their impact on the daily work of the teams and the next practical steps.

Reading Time: 3 minutesIssue #036 dated 02/03/2025: “Aligning UX, API and operational scenarios” in Vezha.About the decision of the week without unnecessary theory – only the practical result and the next focus.

Reading Time: 3 minutes#035 (2025-01-27) on the Vezha blog: Preparing the product for scale, the operational impact of the updates and the priorities of the next iteration.

Reading Time: 3 minutesVezha Issue #034: “Risk Control in the Long Development Cycle”.What did the team change this week, what effect did it have in production and what are we doing next.

Reading Time: 3 minutesVezha Weekly Entry #033: “What does ‘enterprise-ready’ mean in our case.”We explain what worked in practice and how it affected the stability of the service.

Reading Time: 3 minutesIssue #032 on Vezha: “Quality standards before a major release”.Briefly about the changes of the week, their impact on the daily work of the teams and the next practical steps.

Reading Time: 3 minutesIssue #031 dated 12/30/2024: “How we cleaned up technical debt without stalling development” at Vezha. About the decision of the week without unnecessary theory – only the practical result and the next focus.

Reading Time: 2 minutes#030 (2024-12-23) on the Vezha blog: “Less noise, more signal” topic, operational impact of updates and priorities for the next iteration.

Reading Time: 2 minutesVezha Weekly Entry #028: “Operational Reliability Above All.” We explain what worked in practice and how it affected the stability of the service.