52 karma · joined March 9, 2015
Location: Georgia, Batumi
Remote: yes please
Willing to relocate: yep
Technologies: Ruby (10+ys), Java, js, rust, devops, k8s
Résumé/CV: https://www.linkedin.com/in/pavelevstigneev/
Email: pavel.evst@gmail com Location: Indonesia
Remote: Yes
Willing to relocate: Yes
Technologies: Ruby, Java, Golang, Javascript, fullstack, devops, PostgreSQL, Kafka, tech lead
Résumé/CV: https://drive.google.com/file/d/1Dcr9VQxgjc_KkwFEz07PMG42sPDoG9RK/view?usp=sharing https://www.linkedin.com/in/pavelevstigneev/
Email: pavel.evst@gmail.comPassionate engineer having 15 years experience in startups. Specialize on backend, full stack, devops, mostly worked on payment systems and large loads, engineering management, optimizing cloud cost. I love to work with ruby, nodejs, java/kotlin, golang, rust, kubernetes
LinkedIn: https://www.linkedin.com/in/pavelevstigneev/
Github: https://github.com/paxa
Résumé/CV: https://drive.google.com/file/d/1Dcr9VQxgjc_KkwFEz07PMG42sPD...
Email: pavel.evst@gmail.com
Location: Indonesia, Jakarta
Remote: Yes
Willing to relocate: Yes
Technologies: Ruby, Java, Go, Javascript, Rust, k8s & infra, engineering management
Résumé/CV: https://docs.google.com/document/d/1TQrO7wd5YwlB-e6a0h0xOkyuU5u0pB5MA9AKYAPObpQ/edit?usp=sharing
Email: pavel.evst@gmail.comI also remember my macbook unibody 2008 and mbp 2012, with them I could do a lot with 4gb ram, even on hdd, nowadays 8gb is kinda too small for most of programming jobs, it look like macs keep getting better hardware every year and macOS using it more and more aggressively
I often fix some code in my fork, open a pr, but author asking for tests or change something but I simply have no time for it, and for author it will be much easier because he/she is familiar with code style, testing framework, etc. And problem remain unfixed in main repo
I also think that parameter strong typing and splitting code into service helps to design better, more clear messaging between components. Having done that for some time we can train ourselves to always pay attention to it, and it will help up to build larger code bases in a maintainable way. (I think larger code bases are more efficient from “time spent” point of view)
I often see people do same mistake: they trying very hard not to repeat themselves, and the highly reusable functions become very dangerous piece to refactor. I would rather have code copied in different modules, unless it’s very general thing that never change like array sorting or date formatting
We used kafka mirrormaker 1, with 2 ways sync (new cluster have separate topics for write that are synced to old cluster, and all topics from old cluster synced to new cluster) For postgres failover switch to new master required about 1-2 minutes of downtime
We migrated ~80 microservices within 8 months and now our infra cost about 1/4 of what we paid to aws, completely worth the effort!
But rails and ruby still has many good parts. For example global classes and ruby threads to save per request context.
Also if your company has many js and backend libraries, you need to use them, at least on one place