Rustam Ashurmatov

Today I caught a bug in a bank app and suddenly realized how weak the Russian fintech sector has become. I was transferring money between my own accounts in one of the banks.I catch a bug the balance suddenly doubles. A couple minutes later, the account gets automatically blocked for 3 hours. No warnings. No explanations. Just no access to my own money. This is the same fintech that has been praised for years as "the world’s #1, with no analogues anywhere", where to get a job you need to pass 10 algorithm interviews and prove you can implement bubble sort in six different ways? Somewhere along the way to this supposed world-class level, fintech turned into complexity for the sake of complexity, while reliability and UX were pushed aside. I’ve been noticing a strange trend for a while now: Russian banking apps keep turning into SuperApps - with marketplaces, animations, mini-games, personal dashboards for everything. Just checking your balance becomes a precision-navigation quest. When I moved abroad, I was shocked by foreign banking apps: simple, minimalistic, almost ascetic. At the time, they seemed primitive But over time you start to understand: Simplicity is not backwardness. Simplicity is maturity. Nobody tries to prove the app should do everything. It simply does what it must: shows your money -> lets you transfer it -> works reliably And that predictability, over time, becomes much more appealing than a cosmic UX that breaks from one unexpected request

2

1 Comment

Why Vite is crushing Webpack ? (and why we adopted it in my team) Vite up 50x faster! Webpack ❌ 30-60 seconds startup time ❌ Full bundling on every launch Vite ✅ Instant startup (< 1 second) ✅ Native ES modules ✅ No bundling in dev Better Hot Module Replacement Webpack ❌ HMR in 2-10 seconds ❌ Frequent state loss ❌ Full reload sometimes needed Vite ✅ HMR in 50ms ✅ State preservation ✅ Precise module updates Quicker configuration Webpack ❌ Complex webpack.config.js ❌ Loaders and plugins to configure ❌ Steep learning curve Vite ✅ Zero config by default ✅ Native TypeScript support ✅ Ready in 2 minutes Quicker build time Webpack ❌ 3-10+ minutes on large projects ❌ Manual optimizations ❌ Complex configuration Vite ✅ 30 seconds-2 minutes (same projects) ✅ Rollup optimized by default ✅ Automatic tree-shaking Better developer experience Webpack ❌ Cryptic error messages ❌ Difficult debugging Vite ✅ Clear error messages ✅ Precise stack traces ------------------------------------------------------------------------------- Let's connect! I'm a Lead Developer sharing technical insights and team management best practices 2-3 times a week. Follow me for more content on building better dev teams!

4

Practice > Theory: Mock System Design and Behavioral Interviews Some time ago, I was invited to an informal call with a group of Ukrainians in Tech seeking jobs. The idea was to share my experience with job search, interviews, and work culture. That conversation quickly made one thing clear: many people would benefit from hands-on interview practice, especially when it comes to System Design and Behavioral interviews. Soon after that, Anna Rosenthal and I decided to just go for it and plan first round of Mock System Design Interviews. Here are a few highlights: 📌 2 sessions 📌 90+ tech professionals joined 📌 Almost 2 hours of live Q&A 📌 Practical step-by-step guide 📌 Together, we raised funds for a volunteer supporting the Ukrainian Armed Forces 🇺🇦 But the most important part wasn’t the numbers. It was the energy. The questions, the discussions, the engagement. That’s when we knew this couldn’t be a one-time thing. So we’re keeping the momentum and planning more events. This time, we’re expanding to English-speaking sessions and adding Behavioral Interview Mocks. What’s next: 📍Behavioral Mock Interview (UA) — Feb 7, 5 pm CET 📍System Design Mock Interview (EN) — Feb 12, 6 pm CET 📍Behavioral Mock Interview (EN) — Feb 19, 6 pm CET Format: - Live mock interview (Anna & me) - Feedback based on the mock interview - Q&A We’ll also share a practical guide after each session with all key takeaways. 📩 If you are interested, drop Anna Rosenthal or me a message, and we will send you the invite.

38

3 Comments

Ildar is a full-stack .NET developer with 13 years of experience. His goal? To land a remote job at an international company. But there was a challenge… While Ildar is technically strong, technical interviews in English—especially system design discussions—were holding him back. The biggest struggle? ✅ Using the right technical vocabulary ✅ Explaining LeetCode & system design solutions clearly ✅ Thinking out loud in English To tackle this, we focused on: 💡 Breaking down a Booking.com system design problem step by step 💡 Practicing real-world interview discussions (not just coding) 💡 Expanding his technical vocabulary with homework and feedback 🔥 After one session, Ildar improved his ability to describe system design trade-offs confidently in English. We’re continuing this journey with more LeetCode deep dives & structured system design discussions. Want to improve your technical interview skills in English? Let’s talk! 🚀 https://lnkd.in/e5uBv3UQ

8

From 𝗨𝘇𝗯𝗲𝗸𝗶𝘀𝘁𝗮𝗻 to 𝗘𝘂𝗿𝗼𝗽𝗲: The biggest lesson moving to Europe taught me about software engineering When I first moved from Uzbekistan to Europe, I thought the biggest challenge would be adapting to new 𝘵𝘦𝘤𝘩𝘯𝘰𝘭𝘰𝘨𝘪𝘦𝘴, 𝘧𝘳𝘢𝘮𝘦𝘸𝘰𝘳𝘬𝘴, or 𝘦𝘯𝘨𝘪𝘯𝘦𝘦𝘳𝘪𝘯𝘨 𝘱𝘳𝘢𝘤𝘵𝘪𝘤𝘦𝘴. But surprisingly, the lesson that shaped me most wasn’t technical at all. I realized that software engineering is as much about 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻, 𝗰𝗼𝗹𝗹𝗮𝗯𝗼𝗿𝗮𝘁𝗶𝗼𝗻, and 𝗮𝗱𝗮𝗽𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆 as it is about writing clean code. Working across cultures, time zones, and diverse teams taught me:  • Clear communication is more valuable than clever code.      • Adaptability matters more than memorizing a framework.      • The ability to listen, align, and deliver together is what makes you a strong engineer—not just your technical skills.    Yes, hard skills open the door. But soft skills and mindset determine how far you go. What’s the biggest lesson 𝘆𝗼𝘂’𝘃𝗲 learned from a major life change? #SoftwareEngineering #CareerGrowth #LifeLessons #Adaptability #Communication #SoftSkills

6

🚀 Excited to announce the launch of vue-persian - a new GitHub organization dedicated to building high-quality Vue.js tools for Persian language support! After years of working with Persian/Farsi applications and constantly writing the same RTL, digit conversion, and date formatting code, I decided to create reusable solutions that the entire Vue.js community can benefit from. 📦 Current Project: @vue-persian/composables A comprehensive TypeScript library featuring: - Direction management (RTL/LTR) - Persian & Western digit conversion - Persian number formatting with proper separators - Jalali (Persian) calendar support - Currency formatting (Rial/Toman) - Persian text normalization - Smart input handling The library is production-ready, fully typed, and tested with Vitest. 💡 What's Next? We have so many ideas in the pipeline: - Persian UI component library - Form validation with Persian error messages - Persian typography utilities - Calendar components - Data grids with RTL support - Nuxt 3 modules - And much more! If you're a Vue.js developer working with Persian/Farsi interfaces, or just interested in building accessible, localized web applications - I'd love for you to check it out, contribute, or share your ideas! 🔗 GitHub: https://lnkd.in/esZpAHp7 #VueJS #Persian #Farsi #WebDevelopment #OpenSource #TypeScript #Frontend #RTL #Localization

11

2 Comments

LinkedIn decided to block my post exposing fraudsters in their platform. There are easy signs to spot: 1. Fake photo (AI slop) 2. Names from different regions of the world 3. Countries from different regions if the world 4. No real connections. Real recruiters have more than “500+” connections and they show 2 numbers instead of one. 5. Real recruiters are usually “verified.” 6. Random small companies that nobody knows. 7. Basic spelling and syntax errors.

11

2 Comments

𝐏𝐞𝐫𝐟𝐨𝐫𝐦𝐚𝐧𝐜𝐞 𝐈𝐬𝐧’𝐭 𝐀 𝐅𝐞𝐚𝐭𝐮𝐫𝐞 𝐈𝐭’𝐬 𝐀 𝐃𝐞𝐜𝐢𝐬𝐢𝐨𝐧 Your app loads in 8 seconds. Your users leave in 3. That’s not a tech issue. That’s a revenue issue. ◉ 𝐁𝐞𝐜𝐚𝐮𝐬𝐞 𝐡𝐞𝐫𝐞’𝐬 𝐭𝐡𝐞 𝐬𝐡𝐢𝐟𝐭 𝐟𝐨𝐮𝐧𝐝𝐞𝐫𝐬 𝐜𝐚𝐧’𝐭 𝐢𝐠𝐧𝐨𝐫𝐞: Performance is no longer “engineering polish.” It’s product strategy. React 19.2 is shipping compiler-level memoization. Signals are reshaping reactivity across frameworks. Partial prerendering is redefining perceived speed. The ecosystem is evolving fast. But tools don’t fix bad decisions. ◉ 𝐖𝐡𝐚𝐭’𝐬 𝐚𝐜𝐭𝐮𝐚𝐥𝐥𝐲 𝐡𝐮𝐫𝐭𝐢𝐧𝐠 𝐲𝐨𝐮: – Hydration bottlenecks nobody audited – Bloated bundles shipped “just in case” – Streaming done without intent – Architecture that worked in dev not in production Your dev build feels fast. Your production build tells the truth. ◉ 𝐖𝐡𝐲 𝐭𝐡𝐢𝐬 𝐦𝐚𝐭𝐭𝐞𝐫𝐬 𝐭𝐨 𝐛𝐫𝐚𝐧𝐝𝐬: Speed builds trust. Trust drives conversions. Conversions fund growth. Performance isn’t about milliseconds. It’s about momentum. Don’t treat performance as a feature you “add later.” Design for it, Architect for it, Ship with it. ================================================ Founders & SaaS teams: if your front-end feels fast locally but slow for real users, it’s time to rethink your performance mindset. At Nordex Hub, we help brands turn performance into a competitive advantage not a post-launch fix. Let’s build something that feels fast and converts fast.

17

18 Comments

All I learned from this "AI will replace you" is that if you are working in the IT industry you need a second career, and not because the AI actually can do what I do, but because there's no longer any respect for this craft.

29

📝 Big update on Typer.uz — we now have a Blog! A few weeks ago I launched Typer.uz, a free typing speed test for Uzbek, Russian and English users. Today I'm excited to share that we've added a full blog section with 10 articles in both English and Russian! 🎉 Some of the topics covered: 📌 What is a good typing speed? 📌 How to type faster — 10 practical tips 📌 Touch typing vs hunt-and-peck 📌 Typing speed for programmers 📌 Uzbek & Russian keyboard layouts explained The blog is designed to help people improve their typing skills and understand keyboard efficiency — whether you're a student, developer, or office professional. 🔗 Read the blog: https://typer.uz/blog 🔗 Russian version: https://typer.uz/ru/blog Would love to hear your feedback — which topic interests you most? 👇 #typing #productivity #uzbekistan #webdevelopment #buildinpublic #solodev #blog

9

I gave Google Gemini my CV, and it wrote the code for my portfolio. Here is what happened. Backend engineers, we have it the hardest. It is almost impossible to send APIs and Documentation as a portfolio to a client and expect them to be "wowed." But I needed a portfolio that non-technical clients could actually appreciate (because let's face it, they don't read API docs). So, I tried an experiment. I decided to test out "bi-coding" (collaborating with AI). I went to Google AI Studio and used Google Build with Gemini. I didn't spend weeks fighting with CSS. Instead, I simply uploaded my CV/Resume and asked it to visualize my experience. The result? It parsed my backend experience and built this fully functional, visual portfolio website for me. 🤯 The Process: Uploaded my raw Resume/CV. Prompted the AI to build a portfolio based on my actual history. Let the AI handle the frontend logic while I focused on the content. This is "bi-coding" in action using AI to handle my blind spots so I can showcase my strengths. Result: https://lnkd.in/dvRpHMyA Critique the AI's work! How is the UX/UI? Does the presentation do justice to the backend projects I’ve listed? Drop a comment below with your review. If you want to know how to do this for your own resume, ask away I'm happy to guide you through it! 🚀 #ArtificialIntelligence #GoogleAI #WebDev #Backend #CareerGrowth #TechPortfolio

148

40 Comments

A programming language is just a tool! In international developer job postings, you often see requirements like "knowledge of one of the following languages: Python/Java/C#/Go." At first glance, it might seem like the employer hasn't decided on their tech stack. In reality, this reflects an important truth: fundamental programming concepts are universal. I recently experienced this firsthand. With years of Java development experience and occasional JavaScript work, I needed to modify a FreeCAD plugin written in Python — a language I had barely used. The result? The task was completed in one evening. Why did this work: - Algorithmic thinking remains constant. - Unit testing principles are universal. - Modern AI tools very helpful. Of course, deep language expertise requires years of practice. But for solving specific problems, a solid foundation and willingness to learn are often sufficient. What's your take on this approach? Do you find it easy to switch between programming languages? #programming #softwaredevelopment #python #java #javascript #AI

11

💡 Dear recruiters, if you are hiring PHP talent, please stop mentioning Zend Framework in job descriptions or interviews. ➡️ The latest major version was Zend Framework 3, released in 2016. ➡️ Zend Framework was rebranded as Laminas Project in April 2019. So unless you’re deliberately asking a trick question, referencing Zend Framework today just shows you haven’t done your homework. ✅ On the other hand, the "Zend Certified PHP Engineer" is still alive and kicking! It was updated in 2025 and remains a respected credential. #PHP #Recruiting #DevLife #Zend #Certification

6

1 Comment

Senior Frontend Truth: You Don’t Rise to Senior by Writing More Code There’s a quiet misconception in our industry, If I write more code, I’ll become senior. It feels logical, more output - more value - promotion. However seniority isn’t about volume, it’s about leverage. The Output Trap: At junior and mid-level roles, performance is often measured by visible activity: - Tickets closed - Features shipped - Lines of code written - PRs merged So engineers optimize for productivity and the problem is productivity alone doesn’t scale your impact. What Actually Changes at Senior Level: The transition to senior isn’t about doing more work, it’s about changing the type of work you do. Senior frontend engineers: - Think in systems, not tickets - Anticipate future change - Reduce technical debt before it compounds - Improve team decision-making - Mentor and unblock others - Challenge unclear requirements - Design for maintainability Their influence extends beyond the code they personally write, in-fact, some of the most senior decisions result in less code being written. The Shift from Output to Impact: Mid-level engineers increase output, senior engineers increase organizational clarity. They ask: - Should we build this? - Is this the right abstraction? - What happens six months from now? - Where will this design break? They optimize for sustainability, not speed alone. The Real Promotion Skill: The real signal of seniority isn’t how much code you write, it’s how much complexity you remove. It’s the ability to: - See second-order consequences - Make trade-offs explicit - Protect the system from fragile design - Multiply the effectiveness of the team Code is still important, but judgment is what gets you promoted. Apart from judgement, what other components makes you rise as a senior?

29

6 Comments

🇺🇦 Why Ukrainian developers are the best partners for European and American projects Working with clients from different countries, I keep noticing the same thing — Ukrainian developers quickly become indispensable in any team. Here’s why 👇 💡 1. Strong technical expertise. Ukrainian developers have deep knowledge of modern technologies and are not afraid of complex challenges. 🧩 2. We think like partners, not just executors. We don’t just follow instructions — we suggest better solutions, improve processes, and think from a business perspective. ⚡️ 3. We adapt fast. New tools, different time zones, shifting priorities — that’s not a problem, that’s our normal. 🌍 4. We share similar values. Western teams appreciate honesty, responsibility, and transparency — the same principles Ukrainian professionals live by. ❤️ 5. We genuinely care about results. For us, every project is more than a contract — it’s an opportunity to build something valuable and represent Ukraine on the global stage. That’s why international companies keep coming back to Ukrainian specialists and freelancers. And I see it happening every day. #UkrainianDevelopers #WebDevelopment #Freelance #RemoteWork #Teamwork #IT #Upwork #FrontendDevelopment

6

4 Comments

Hi all, I keep seeing posts on Instagram and Facebook where people compare frontend developers with backend developers. Comments like “tu bas div ko middle me kr” 🤦‍♂️ clearly show a limited mindset. Having worked in both frontend and backend, I can confidently say this: yes, backend can be more complex and time-consuming in many cases—but reducing frontend to “just centering a div” is unfair and uninformed. In today’s AI era 🤖, many tasks across both domains can be accelerated with AI tools. But that’s exactly why developers still get hired—because AI isn’t perfect, and real-world projects need experience, problem-solving, and judgment. The conversation shouldn’t be about which side is harder. It should be about the quality we deliver: 🔹 Are we writing clean, maintainable code? 🔹 Are we following SOLID principles? 🔹 Are we designing scalable systems and user-friendly experiences? Also, compensation varies widely. Some frontend developers earn more than backend developers—not because frontend is harder, but because experience, depth of knowledge, and ownership matter. 💼 Would love to hear your thoughts 😊💬 #frontend #backend #frontend_developer #backend_developer #frontend_backend

12

3 Comments