Skip to content

Instantly share code, notes, and snippets.

View maximov-m's full-sized avatar
🇺🇦

Michael Maximov maximov-m

🇺🇦
16 followers · 24 following
View GitHub Profile
@maximov-m
maximov-m / test output
Created August 13, 2019 13:06
[INITIALIZED] : Modeling process has begun
[INITIALIZED] : Modeling process has begun
[INITIALIZED] : Modeling process has begun
@maximov-m
maximov-m / index.d.ts
Created August 14, 2019 08:05
// Type definitions for chai 4.2
// Project: http://chaijs.com/
// Definitions by: Jed Mao <https://github.com/jedmao>,
// Bart van der Schoor <https://github.com/Bartvds>,
// Andrew Brown <https://github.com/AGBrown>,
// Olivier Chevet <https://github.com/olivr70>,
// Matt Wistrand <https://github.com/mwistrand>,
// Josh Goldberg <https://github.com/joshuakgoldberg>
// Shaun Luttin <https://github.com/shaunluttin>
// Gintautas Miselis <https://github.com/Naktibalda>
@maximov-m
maximov-m / System design framework.md
Created September 25, 2022 20:10
System design framework part-1

System Design Framework

Цель интервью

  1. Дать достаточное кол-во сигналов для интервьюеру, что вы можете колаборировать, работать в команде проектировать и делать это сообща вместе
  2. Можно ли интервьюер представить вас в качестве члена команды? Сделать так что бы смог

L5-L6 отличаются интервью: На Л6 уровне нужно добавлять знания и показывать ваш личный экспирианс Систем дизайн это про общение с интервьюером

@maximov-m
maximov-m / System Design Framework (part 2).md
Created September 30, 2022 21:57

System design framework (part 2)

  • Основные форматы для коммуникации внутри системы: JSON, CSV, XML (SOAP - пахнет старостью)
  • Binary: Protobuff, Thrift, Avro (Schema-based, Hadoop and Kafka)
@maximov-m
maximov-m / System design thinkings |TOC.md
Created April 3, 2023 09:20

System requirements (functional and non-functional requirements)

Functional requirements (how to define, working backwards approach)

High availability (time-based and count-based availability, design principles behind high availability, processes behind high availability, SLO, SLA)

Fault tolerance, resilience, reliability (error, fault, failure, fault tolerance, resilience, game day vs chaos engineering, expected and unexpected failures, reliability)

Scalability (vertical and horizontal scaling, elasticity vs scalability)

Performance (latency, throughput, percentiles, how to increase write and throughput, bandwidth)

Durability (backup (full, differential, incremental), RAID, replication, checksum, availability vs durability)

Consistency (consistency models, eventual consistency, linearizability, monotonic reads, read-your-writes (read-after-write), consistent prefix reads)

Maintainability, security, cost (maintainability as

@maximov-m
maximov-m / cv.md
Created June 22, 2023 09:17

Main

  • The length of the CV should be 1-page
  • Readability is priority

Sections

There are several sections in the CV:

Contact info

  • The first one is information about you:
    • Name in large font
    • Contact details: LinkedIn, email, phone number, maybe GitHub