Evrone

We’ve got a New Year’s tradition with the team: once a year we get together and… nope, not to go to the banya (we save that for the corporate party 😉), but to sit down and unpack the year’s results. As you’ve probably guessed, it’s our New Year’s edition on air! Unit tests are written, projects are shipped, and developers are chopping salads while sincerely believing Santa will fly in on a plane and extend their Cursor subscription for free. And we’re wishing you—friends and colleagues—a Happy New Year. To finally let the old year go, let’s do a quick retrospective. 🎬 So, in 2025 we kicked off 19 new projects. Different stacks, tasks, and domains—we’re not afraid of tough decisions and big challenges. A special thank-you goes to our team and our clients for the trust and the exciting work we got to do together. 👨💻 45 new pros joined Evrone this year—team, just know you’re absolutely awesome. And we didn’t just grow in headcount: 9 babies were born to our colleagues in 2025. Scaling up! 🎁 It was also a year of поздравления (we moonlight as part-time Santas 😀): our little wizards shipped around 600 gifts worldwide—to the team, partners, and clients. 😺 And what about internal traditions? We hosted 50 “Cat Fridays” and collected 350+ cat photos. Keeping a healthy company culture matters. 🚀 25 people took part in our mentoring programs in Golang and Python (3 Go cohorts and 1 Python). Love seeing learning become part of the team’s DNA. 🪩 One more reason to be proud: our Go-clean-template repo hit 6,900 stars and nearly 600 forks, taking 2nd placeamong the most popular Russian open source projects on GitHub. A huge shared win—and it’s amazing to see the product live on and help people around the world. A new year is ahead—new projects, new challenges, new opportunities. We truly believe that together with you—our clients and partners—we’ll build even more great things. May the coming year bring lots of joy, inspiration, and reasons to be proud. Happy New Year! 🎉

Jumping into your feed at the end of the year with a topic that’s gotten way too much hype: AI in IT development. But today we’re not talking about copy-pasting code from ChatGPT or taking an express “prompt engineer” course when the only thing you know about Python is that it’s the snake from the first Harry Potter movie. We’re talking about neural nets in software testing. In QA, AI is especially useful when you need to quickly structure requirements, build a baseline test coverage from descriptions and specifications, draft API/UI automated tests, and tidy up the related documentation. It’s a practical way to get to the point faster and leave developers more room for real engineering work 😄 Denis Kirov and the Evrone team will break it down: how to approach AI adoption in QA processes, what requirements matter (security, environment boundaries, data, and output quality control), which tech stack to choose, how to write prompts for predictable results, and what it all looks like in practice. 📌 All the details are in the slides. And a quick note before you jump in: AI has grown fast this year. That’s exactly why a sober approach matters—use it as a tool, not as a universal replacement for people 😉 #ai #softwaretesting #qa #qualityassurance #automationtesting #apitesting #uitesting #devtools #it #evrone

Did everyone survive the imperative case back in school? You know, when the teacher stood by the chalkboard explaining verbs and bossing them around. Well, that rule has officially migrated from Russian language textbooks into developer handbooks. It’s basically the perfect way to describe the imperative programming style. The idea is simple: the system gets direct instructions — do this action, then the next one, and then another. It’s a classic step-by-step algorithm where the programmer fully dictates the order of operations. What’s fun is that even in Ruby, a language we usually associate with objects and methods, the imperative style feels right at home. Ruby lets you build a linear sequence of operations: declare variables, run calculations, print the result. Alright, no more spoilers — all the details about imperative style are waiting for you on the slides 😄 P.S. Even if you usually think in objects and methods, switching to imperative style from time to time helps you feel how your code behaves under the hood 😉 #imperativeprogramming #rubydev #codestyle #programmingbasics #rubylang #devtips #codingmindset #softwarecraft #rubytutorial #learncode

Let’s step away from development for a moment and talk about processes (no offense, developers 😉). Specifically — business processes. They’re the foundation of everything. The reality is that developers always build a system around the actual business needs, not the other way around. And the older a product gets, the more those processes tend to grow, gain odd nuances, and eventually start living by their own rules. Together with Daniil Davydov, we discuss what makes a process mature and manageable. We break down the importance of flexibility, realistic goals, and reliability — the qualities that keep a system from falling into chaos under load. And finally, we talk about transparency and a systems approach: without them, processes don’t scale and don’t stay stable for long. 📌The goal is simple: to show how to bring back clarity and predictability while staying within the familiar RoR stack — without sending your architecture into orbit. Check out the slides — that’s where the technical part is 😄 #processes #business #dev #teamwork #workflow #product #system #ror #tech #engineering

Some questions keep us awake at night. For example, evaluating a project by the number of lines of code committed per month. If you too wake up in a cold sweat, there is a solution. Today we’ll talk about DORA metrics: why they’re needed and what exactly they measure. We won’t do it alone, but together with Arina Goncharenko, a DevOps engineer from Lamoda Tech. So, DORA divides metrics into speed and stability: lead time for changes and deployment frequency show how quickly you deliver code, while change failure rate and mean time to restore indicate how reliably releases work. Together they help identify bottlenecks and understand where improvement is needed. 👀 These indicators are important not for comparing yourself with other teams, but for your own growth: DORA emphasizes that metrics serve as both leading and lagging indicators. 📌You can read more about what DORA metrics are and how they are used to detect issues with long recovery times in our cards. And keep an eye on our updates — there will be plenty of useful information 😉 #devops #dora #dorametrics #cicd #observability #leadtime #deploymentfrequency #mttr #changefailurerate #engineeringmetrics

Go is the kind of language your mom would approve of — clean, simple, and well-behaved. But the deeper you dig into the code, the more hidden traps you find that no one talks about on GitHub. Today we’re unpacking the classic Go mistakes that can wreck your code and confuse even experienced devs 😅 Embedded types look handy at first, but they can easily create method conflicts. Maps suddenly “leak” when multiple goroutines write to the same one without synchronization. Errors are returned as a second value — and just as easily ignored until they show up as production bugs. Then there’s everyone’s favorite interface{} — it looks universal, but strips away type safety, turning your project into a mess of manual checks. Add pointer receiver confusion, where a single wrong choice means your type no longer satisfies an interface, and your “simple” language becomes a full-blown puzzle. 📌Go forgives a lot — but not carelessness. Check out the slides for 5 common traps so you can skip stepping on the same ones 😌 #golang #godev #goprogramming #softwareengineering #backend #devtips #coding #cleanarchitecture #programminglife #golangcommunity

It may seem like DevOps developers and Marvel’s “new Avengers” have nothing in common, but that's not entirely true. What they have is Sentry! The punchline still needs a little polishing 😅 But the comic book character Sentry is actually quite similar to the tool we’re talking about today. As the name suggests, Sentry watches over errors inside your application and collects comprehensive context. And yes — it’s a true buddy for developers, testers, and DevOps. ⚙️Instead of guessing why something went wrong for users, Sentry shows the full picture: from the release down to the specific user. This way, bugs are caught before they flood your support inbox, and releases become more predictable and less stressful. 🔨In Sentry, each error is displayed as a handy card with environment, release, and the number of affected users. This lets developers instantly identify the root cause and assess its severity. Add in smart alerts, issue grouping, and integrations with Slack, GitHub, and Jira — and you’ve got the full toolkit. 📌In short, Sentry turns the chaotic “looks like prod just went down” into the clear “we know where, why, and who’s on it.” Find even more tips and insights about Sentry, other tools, and tech stacks on our website 👉 https://evrone.com/ #sentry #devops #bugtracking #errorhandling #monitoring #debugging #softwaredevelopment #developerlife #reliability #techtools

Today we’re diving into the acronym WASM. Its full name is WebAssembly. The “Web” part is obvious, but “Assembly” deserves a closer look. WASM is a portable bytecode format and a compact sandboxed virtual machine: one binary, many platforms, predictable execution, and strict access boundaries. Its core value lies in isolation and reproducibility. You build a module and run it across different environments without a dependency zoo—reducing deployment surprises and making it easier to scale computations confidently. 📡 WASI lets a module talk to the outside world. Think of it as a standard connector: access to files, network, and clocks, but everything is closed by default. You enable only what you need. 📀 Next comes the Component Model—a way to assemble applications from separate modules like building blocks, even if they’re written in different languages. The result: easier updates for individual parts and simpler guarantees of service speed and availability. 💡 How does it fit into the web stack? Picture it like this: the host is your main application, and the guest is a WASM module in its sandbox. The host calls the guest whenever you need to safely and independently execute a piece of logic (yes, even in web servers like angie). If you have any question about how to boost your code, ask us 😉 📌 Website link: https://lnkd.in/eSHjdCuv #webassembly #wasm #wasi #componentmodel #webdev #backenddevelopment #sandboxsecurity #crossplatform #performanceengineering #techexplained

Today’s topic is the Percolator. That coffee-brewing method where water runs through the grounds again and again… wait, wrong script. Let’s try again 🧐 In general search, a percolator is the reverse logic: we pre-store queries, then run new documents through them and instantly see what matched. This shines where the data stream is too heavy for manual handling. 💡Classic search answers “find a document for this query.” Percolator flips it: “which queries should fire on this document?” Two practical ways to do it: 🎛️ Elasticsearch: create an index that stores queries and call percolate for each new document, adding pre-filters and sharding by topic for speed and isolation. 📺 Sphinx (and compatible engines): keep queries separately, run the document through the percolation mechanism, and get matching IDs out. Plays nicely with RT indexes and metadata—if you design the schema up front. To argue less and measure more, look at benchmarks: p50/p95 latency, throughput, CPU and memory load, and the gap between cold and warm cache. 📌 More details and other cases are waiting on the our website. We’ll show configs and explain how to keep your SLAs without hacks 🤔 Website link 👉 https://evrone.com/cases #percolatorsearch #elasticsearch #sphinxsearch #informationretrieval #searchengineering #realtimeindexing #benchmarking #p95latency #throughput #sla

Let’s step away from pipelines and talk about human expertise. It’s the kind of capital we at Evrone have been compounding for years—and we’re not shy about it. Leveling up mentorship and keeping an atmosphere where a junior isn’t afraid to ask one more question… is hard work, honestly. 👀 📈 Plenty of studies agree: psychological safety is the prime engine of team effectiveness (and yes, for the next two minutes we’ll pretend we’ve got a Gestalt Institute diploma). So here’s what actually works. 💡 A mentoring culture shortens time-to-autonomy—boosting engagement and quality. Every junior has a clear growth roadmap; mid-levels level up into mentors with goals and metrics. Regular 1:1s, pair programming, and release debriefs. We convert individual know-how into shared practice, not a dusty Notion or Git archive. 💎 Processes & artifacts. A single wiki anyone can dive into: code-style standards, onboarding guides, postmortems, best practices. Cross-project reviews bring fresh eyes and transfer expertise across teams. 📲 Open internal meetups and AMAs lower barriers, speed up context sharing, and reinforce the mentoring culture. The result: a higher practice “rating”—fewer manual crutches, steadier delivery, happier stakeholders. Some may find this post secondary or “not that useful,” and that’s fine—it isn’t meant to reveal arcane coding secrets. Just think how many great ideas and people get fed into the process meat grinder without a helping hand—and go unnoticed. 📌 If your values are align with our company's policies and you want to work in a team full of pros and build something by making a difference, welcome to our website. We're counting on you 😉 Website link 👉 https://jobs.evrone.com/ #engineeringculture #mentorship #psychologicalsafety #knowledgesharing #pairprogramming #onboarding #codereview #crossprojectreviews #internalmeetups #techleadership