idexter.dev

Talks

Mon, 25 May 2020 17:01:46 +0300

This page presented the list of technical talks and events I have participated in.

Profiling Go Applications (Ru) / “First Go-meetup 2021” (21 Feb 2021)
Dependency Injection and it’s friends (in Go) (RU) / “Online meetup - Quarantine, Go away!” (30 May 2020)
I was a host at Room #2 at Stay home and GOnline (RU) (25 April 2020)
Make a releases in a proper way with GoReleaser (RU) / “March of the Go Meetup” (15 March 2019)
Microservices with “go-micro” (RU) / “Happy new Go year Meetup” (5 January 2019)

Library

Thu, 30 Apr 2020 01:03:36 +0300

I think, that self-education it’s one of the best investment you can do. So here you can see books I have read which most influenced me and made me who I am as an engineer.

Management & Soft-skills Link to heading

The Goal: A Process of Ongoing Improvement / by Eliyahu M. Goldratt, Jeff Cox
The Choice / by Eliyahu M. Goldratt
Peopleware: Productive Projects and Teams / Tom DeMarco, Timothy Lister
Kanban: Successful Evolutionary Change for Your Technology Business / by David J. Anderson and Donald G. Reinertsen
SCRUM: Applying Agile Project Management Successfully / by Roman Pichler
Soft Skills: The software developer’s life manual / by John Sonmez
The Passionate Programmer: Creating a Remarkable Career in Software Development / by Chad Fowler
The Pragmatic Programmer: From Journeyman to Master / by Andrew Hunt
So Good They Can’t Ignore You: Why Skills Trump Passion in the Quest for Work You Love / by Cal Newport
Out of the Crisis / W. Edwards Deming
Kanban Method. Basic Practice / Alexey Pimenov

Software Engineering & Software Architecture Link to heading

Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems / by Martin Kleppmann
Code Complete: A Practical Handbook of Software Construction / by Steve McConnell
Domain-Driven Design: Tackling Complexity in the Heart of Software / by Eric Evans
Implementing Domain-driven Design / by Vaughn Vernon
Clean Architecture: A Craftsman’s Guide to Software Structure and Design / by Robert C. Martin
The Clean Coder: A Code of Conduct for Professional Programmers / by Robert C. Martin
Building Microservices: Designing Fine-Grained Systems / by Sam Newman
Software Requirements (third edition) / Karl Wiegers and Joy Beatty

Math, Computer Science & Programming Languages Link to heading

Math Geek: From Klein Bottles to Chaos Theory, a Guide to the Nerdiest Math Facts, Theorems, and Equations / by Raphael Rosen
Code: The Hidden Language of Computer Hardware and Software / by Charles Petzold
Structure and Interpretation of Computer Programs (SICP)
The Go Programming Language / by Alan A.A. Donovan & Brian W. Kernighan
Concurrency in Go: Tools and Techniques for Developers / by Katherine Cox-Buday
Writing An Interpreter In Go / by Thorsten Ball

DevOps & SRE Link to heading

The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win / by Gene Kim, Kevin Behr, George Spafford
Effective DevOps: Building a Culture of Collaboration, Affinity, and Tooling at Scale / by Jennifer Davis
Practical DevOps / by Joakim Verona
Continuous Integration: Improving Software Quality and Reducing Risk / by Andrew Glover, Paul Duvall, and Steve Matyas
Release It!: Design and Deploy Production-Ready Software / by Michael T. Nygard
Cloud Native DevOps with Kubernetes / by John Arundel, Justin Domingus

About me

Thu, 30 Apr 2020 01:03:13 +0300

My name is Anton. I’m an experienced business-oriented Engineering Manager 💻 with Software Engineering and SRE background. I’m focused on helping software development teams overcome the barriers between engineers and business and move forward predictably, creating reliable products by leveraging SRE and adopting a DevOps culture.

Some issues I can solve Link to heading

Your software development process is unpredictable, and you don’t trust your developers.
The engineering team spends a lot of time on code reviews and testing, but the process does not give the desired result.
Your services and applications are unstable and constantly crashing, and it’s hard for developers to figure out root outage causes.
Each release always breaks something. The process is stressful, and it takes a long time to restore the data and roll back the changes has been made.
You are afraid to release on Fridays and weekends. Your developers don’t understand how their software works in a production environment.
You want to move faster, but you are unable to release on a daily basis.
Your developers, QA engineers and system administrators are constantly fighting with each other.
You do not have high-quality technical documentation and important knowledge about your system is stored in engineers heads.

As a professional Link to heading

I have been doing Software Engineering since 2002 and doing it on a commercial basis since 2005. In 2009, I graduated “Norilsk Industrial Institute” as a specialist in “Automation of Technological Processes and Factories” (in Metallurgy). For about 5 years I was working on Norilsk Nickel as an Automation Engineer. I used to work with really complex technological equipment in dangerous metallurgical production. This experience helped me to establish my own view on the problems of modern software development and find approaches how to solve them.