2
points
pavelevst
Joined 52 karma
- pavelevst parentLook for cheaper alternatives (many of them in Europe and not only), smaller companies than Microsoft usually have a human to deal with such cases, also their services costs 5-10x less
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.com- SEEKING WORK | Bali & Jakarta, Indonesia | Remote (US/EU/AU timezone)
Passionate 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.com- I’ve used core i9 mbp16 for almost 3 years and this week I’ve used M1 Pro mbp, seeing hide differences in performance and knowing the actual difference in tests of these 2, it make me think that apple international slowdown and heat up intel macs, like they did (and may be still do) with iPhones
I 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
- May be oot. As a maintainer I always try to accept help what people suggest, and make it even better. Without asking people to write tests or format code to match my preferences or make it cleaner…
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
- FFI implementation in bun.js using tinyCC I’m impressive, it brings whole new level of performance. Also doesn’t require to have libffi or additional compiler in a system. I hope more languages will have such functionality, it will bring us closer to possibility to use any existing code in language/runtime that we prefer
- I started with dynamic languages, ruby is my favorite, and I use it everywhere where it’s suitable. As I observe, over years static languages getting abit more dynamic or less explicit (as they can), and dynamic languages getting some support for type checking. I guess having both in one language would be a best thing. So when code gets larger or I want to be more confident in some part I can add type validation (it could be a code that run as shared library, or communication between modules)
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
- My team was migrating 1000+ VMs from aws to gcp, mostly for cost efficiency (and adoption of k8s for even better cost)
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!