Title : What means deep dive into skills, technology (feat. Obsidian)
I am using Obsidian for personal usage to organize my thoughts and follow the trails of questions I have.
This is my graph view screenshot of my Obsidian
As you can see, there are many nodes and flows
During tech interviews, both as an interviewer and interviewee, it's common to encounter questions that lead to others, as well as inquiries about deep dive experiences.
For Example - In Tech Interview
💡 Q: How can a client reach a service with pod in Kubernetes?
A: k8s services like NodePort, LoadBalancer help clients reach podsQ: Then how does a NodePort service deliver traffic (packet) to a specific pod?
A: There are selectors, labels and DNS resolver inside Kubernetes to reach a pod
Q: Then what component of k8s has DNS resolver?
A: Maybe CoreDNS does...
It is very hard to know all core concepts, right?
So, by using obsidian you can organize your thought and information well . Maybe you can create documents like below for example
[[How k8s service deliver packet to Pod?]]
-> [[What is k8s Service?]]
-> [[What is kube-proxy?]]
-> [[What is CoreDNS?]]
-> [[How DNS resolver work?]]
-> [[What is NodePort]]
-> [[What is LoadBalancer]]
...
Thus, I am using Obsidian to effectively respond to these questions and to habituate myself to this train of thought
Obsidian allows easy linking or creation of documents(nodes) using the [[ ]] tags on page.
Someday, I plan to write on my blog about the things I'm organazing, but I'm currently only drafting because my illustration skills are lacking
What I want to say through this article is how, as someone who didn't know what it meant to deep dive into a skill to become a good engineer, I started studying this way.
This helped me recognize my shortcomings and inspired me about how I could grow and develop myself further
I wrote this hoping to provide good insights for those who are about to start this kind "Deep Dive" study.