https://github.com/ivankatliarchuk/ivankatliarchuk
https://github.com/ivankatliarchuk/ivankatliarchuk
Last synced: 5 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/ivankatliarchuk/ivankatliarchuk
- Owner: ivankatliarchuk
- License: cc0-1.0
- Created: 2021-03-07T13:53:33.000Z (about 5 years ago)
- Default Branch: main
- Last Pushed: 2024-03-28T22:48:24.000Z (about 2 years ago)
- Last Synced: 2024-10-06T04:06:44.785Z (over 1 year ago)
- Size: 5.38 MB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
### Hi there 👋, [Ivan][website] is here
My primary interests lie in Software Engineering as well as SRE, SecDevOps and SDLC
### Connect with me:
[][linkedin]
[][medium]
[][github]
---
### **Fun Facts**
- My first coding achievement
* 1990, OMK Software, Buran game for DOS operating system. Reverse engineer code from cassette tape to a paper.
- 1995 tried Windows 95
---
### **Platform Engineering & SRE Milestones**
- **2011** – Early adoption of Pivotal Cloud Foundry (PCF) & BOSH for cloud-native platforms for on-prem and early days hyperscalers.
- **2015** – Led the first production proof-of-concept (PoC) comparing Kubernetes and Pivotal Platform.
- **2018** – Scaled to **1,000+ applications** running across multiple Kubernetes clusters.
- **2020** – Established platforms supporting **1,000+ customers**, managing multi tenant environments.
- **2023** – Empowered **thousands of customers** to create on-demand Kubernetes clusters **as effortlessly as deploying an application**.
---
### **SecDevOps work**
- System security audits
- Defined custom system security controls and where possible automated them with Policies as Code
- Supply chain security (SLSA, NIST, ....)
---
**How I do Pull Request Reviews**
- Code Quality: Ensuring the code is clean, efficient, and follows project standards.
- Simplicity: Ensuring each PR addresses a single purpose, such as refactoring, implementing a new feature, or adding tests and etc. Focused changes are easier to review, test, and release. This make reviews faster to review and approve.
- Good Test Coverage: Adding or updating tests is key to keeping the codebase stable and future-proof.
If you not agree, someone else could approve your code.
[Styleguide](https://google.github.io/styleguide/go/) and [effective-go](https://go.dev/doc/effective_go) that I use for Go projects
[PR strategies I usually follow](https://artsy.github.io/blog/2021/03/09/strategies-for-small-focused-pull-requests/)
**Recent Posts:**
**Languages and Tools I Use:**





























[website]: https://ivankatliarchuk.github.io
[medium]: https://medium.com/@ivan.katliarchuk
[linkedin]: https://www.linkedin.com/in/ivankatliarchuk
[github]: https://github.com/ivankatliarchuk