Dmitrii Sviridov - Резюме Golang Developer

MERLION (February 2022 — March 2023), Senior Golang Developer: Development and support microservices in Goland, writing tests (unit), mentoring other developers, conducting a code review, creating tasks for developers. LLC "Jupiter" (November 2016 — February 2022), Senior Backend Developer: Writing microservices in Go, code coverage with tests, code review, support for microservices in PHP (PHP Slim, Symfony, Yii2), SQL query optimization, database design, software architecture design, writing small CRM (for microservices) in React. InvestAZ (September 2014 — September 2016), Full Stack Developer: Writing Financial Services CRM Software in PHP and JS, writing tests, code review. LLC "ITigris" (January 2015 — July 2015), Full Stack developer: Writing a site for sale of glasses and lenses (PHP, Yii2, JS, jQuery) LLC "Petroservice" (April 2014 — August 2014), Full Stack developer: Support and development of a site for the sale and rental of real estate (PHP, JS (jQuery)). Writing tests, SQL query optimization. LLC "Lasmart" (August 2013 — March 2014), Programming Analyst: Development and support of CPM-systems with sales statistics (PHP, ExtJS, Microsoft SQL Server) LLC "SmartMuseum" (April 2012 — July 2013), Full Stack developer: Project development from scratch (PHP, js (jQuery), MySQL), application architecture design. LLC "Projectinvest" (June 2011 — November 2011), C++ programmer: Development of a program for processing, grouping and sorting documents (in C++)

Technical cybernetics, 2014 Peter the Great St. Petersburg Polytechnic University, Saint Petersburg

I am working in web development for a long time. I have a broad outlook in many of its areas in addition to my main activity (GO, php). For example, in my free time I freelanced in Django projects (about 10 projects) and wrote various asynchronous parsers in Python. Also, in my free time, I develop (rather just support) my small "pet projects": 1. animalpaw.ru - a site with articles, tests and descriptions of breeds of various animals (technologies used: React, NextJS, NestJS). I wrote almost all the articles myself (I bought some very cheaply, but subsequently almost completely rewrote them because of their low quality). There are recommender systems to help people choose a dog/cat breed. By the way, people use it. :) 2. calc-ok.com - site with various calculators (technologies used: Django, Wagtail, React, server configured with Ansible). It was created with the aim of studying Wagtail, but I don’t see any special prospects for this knowledge at the moment - so the site is actually abandoned. It is important to note that these sites were created not for making money, but for learning new technologies and keeping your knowledge up to date. In particular, this is how I learned Django, and then gained experience using NestJS and NextJS. I also write various libraries, which you can see in my GitHub profile: https://github.com/dimuska139 Links to my libraries are on the official website of Rawg (https://rawg.io/apidocs - "API wrappers by our community" - php and go clients) and Sendpulse (https://sendpulse.com/en/integrations/api - go-client). Also, a simple but useful library for normalizing email addresses https://github.com/dimuska139/go-email-normalizer deserves special attention. Of course, I know how to work with documentation (in Russian and English), I use Git (I once used Mercurial SCM), I cover code with tests, write migrations, optimize sql queries, write (generate) documentation - I think such things should be clarified not really needed. Don't forget about the README. I am stress-resistant, I can find a common language with different people, get out of conflict situations, I can not only defend a point of view, but admit my mistakes. Not toxic, but sometimes boring.

-

My failures:
1. Once, using MsSQL, I clicked "Drop and Create" (yes, in production) on the table with user
subscriptions to paid services. Backups were not made in that place of work. Fortunately, the data
was returned, because. they were cached in the admin panel in localStorage - we managed to get
them from there and load them back into the database table.
2. Once the task was set to remove quite a lot of records from the database. The process was slow
due to checking foreign keys, and I did not think of anything smarter than asking the devops to
disable their check (ALTER TABLE <tablename> DISABLE TRIGGER ALL). As a result, data integritywas violated.
3. Deployed with an incorrect WHERE clause in the SQL query, as a result of which it deleted a
huge bunch of records from the production database.
4. Released the internal library, increasing the patch version of the tag instead of the major one
(despite the fact that the changes broke backward compatibility) - as a result, several projects
could not send email notifications to users for 30 minutes.
5. Deployed with the index creation migration without CONCURRENTLY, locking the table.
6. Incorrectly explained the task to devops, as a result of which the prod balancer proxied half of
the traffic for staging.