Skip to content

Instantly share code, notes, and snippets.

@senthilkumar-e
senthilkumar-e / CKA_Notes.txt
Created October 24, 2021 06:21 — forked from iamavnish/CKA_Notes.txt
CKA Notes
# Namespace / Service
- A pod can access a service in its own namespace by just using service name.
A pod can access a service in a different namespace by using below format.
<svc-name>.<ns-name>.<svc>.<cluster.local>
e.g db-service.dev.svc.cluster.local
- When a service is created, a DNS entry is added automatically in this format:
db-service.dev.svc.cluster.local
Here db-service is service name, dev is namespace, svc represents service and cluster.local is domain.
@senthilkumar-e
senthilkumar-e / beautiful_idiomatic_python.md
Created June 28, 2021 14:05 — forked from 0x4D31/beautiful_idiomatic_python.md
[Beautiful Idiomatic Python] Transforming Code into Beautiful, Idiomatic Python #python

Transforming Code into Beautiful, Idiomatic Python

Notes from Raymond Hettinger's talk at pycon US 2013 video, slides.

The code examples and direct quotes are all from Raymond's talk. I've reproduced them here for my own edification and the hopes that others will find them as handy as I have!

Looping over a range of numbers

for i in [0, 1, 2, 3, 4, 5]:
@senthilkumar-e
senthilkumar-e / FB-PE-InterviewTips.md
Created July 25, 2020 04:20 — forked from ameenkhan07/FB-PE-InterviewTips.md
Facebook Production Engineering Interview

What to Expect and Tips

• 45-minute systems interview, focus on responding to real world problems with an unhealthy service, such as a web server or database. The interview will start off at a high level troubleshooting a likely scenario, dig deeper to find the cause and some possible solutions for it. The goal is to probe your knowledge of systems at scale and under load, so keep in mind the challenges of the Facebook environment.
• Focus on things such as tooling, memory management and unix process lifecycle.

Systems

More specifically, linux troubleshooting and debugging. Understanding things like memory, io, cpu, shell, memory etc. would be pretty helpful. Knowing how to actually write a unix shell would also be a good idea. What tools might you use to debug something? On another note, this interview will likely push your boundaries of what you know (and how to implement it).

Design/Architecture 

Interview is all about taking an ambiguous question of how you might build a system and letting