Navneet Nandan Jha
@navneet066.bsky.social
Infrastructure Architect | Sr. Software Engineer @WidasConcepts | Opensource Enthusiast | K8S, CK{A,AD,S} | Opinions are my own
Linkedin: https://www.linkedin.com/in/navneet066
Linkedin: https://www.linkedin.com/in/navneet066
April 1, 2025 at 12:47 PM
Attending CiliumCon here in #kubecon Europe.
Liz Rice just explained some critical key points when doing the configurations of cilium.
#KubeCon #ciliumcon #kubernetes #devOps #ebpf #networking
Liz Rice just explained some critical key points when doing the configurations of cilium.
#KubeCon #ciliumcon #kubernetes #devOps #ebpf #networking
April 1, 2025 at 8:57 AM
Attending CiliumCon here in #kubecon Europe.
Liz Rice just explained some critical key points when doing the configurations of cilium.
#KubeCon #ciliumcon #kubernetes #devOps #ebpf #networking
Liz Rice just explained some critical key points when doing the configurations of cilium.
#KubeCon #ciliumcon #kubernetes #devOps #ebpf #networking
A good illustration of the image of how ImagePullBackOff and OOMKilled happens
#kubernetes #devOps #sre #k8s #container #cncf
#kubernetes #devOps #sre #k8s #container #cncf
February 27, 2025 at 3:53 PM
A good illustration of the image of how ImagePullBackOff and OOMKilled happens
#kubernetes #devOps #sre #k8s #container #cncf
#kubernetes #devOps #sre #k8s #container #cncf
Evening walk in Pforzheim.
February 23, 2025 at 9:22 PM
Evening walk in Pforzheim.
6 Common API Architecture Styles
#APIDesign
#softwareArchitecture
Follow
@navneet066.bsky.social
and www.linkedin.com/in/ninadurann for more such contents.
#APIDesign
#softwareArchitecture
Follow
@navneet066.bsky.social
and www.linkedin.com/in/ninadurann for more such contents.
November 21, 2024 at 9:41 AM
6 Common API Architecture Styles
#APIDesign
#softwareArchitecture
Follow
@navneet066.bsky.social
and www.linkedin.com/in/ninadurann for more such contents.
#APIDesign
#softwareArchitecture
Follow
@navneet066.bsky.social
and www.linkedin.com/in/ninadurann for more such contents.
Stack Overflow views decreased by more than 50% after ChatGPT was released.
Our good old friend is not gaining much traction since AI came in picture.
Now stack overflow’s turn to come up with better approaches.
#devops #stackoverflow #devsecops #artificialintelligence #AI #devsecops
Our good old friend is not gaining much traction since AI came in picture.
Now stack overflow’s turn to come up with better approaches.
#devops #stackoverflow #devsecops #artificialintelligence #AI #devsecops
November 15, 2024 at 4:08 PM
Stack Overflow views decreased by more than 50% after ChatGPT was released.
Our good old friend is not gaining much traction since AI came in picture.
Now stack overflow’s turn to come up with better approaches.
#devops #stackoverflow #devsecops #artificialintelligence #AI #devsecops
Our good old friend is not gaining much traction since AI came in picture.
Now stack overflow’s turn to come up with better approaches.
#devops #stackoverflow #devsecops #artificialintelligence #AI #devsecops
November 3, 2024 at 7:59 PM
Diwali is almost here!
October 29, 2024 at 6:52 PM
Diwali is almost here!
Understanding ansible directory structure.
#ansible
#devops
#devsecops
#automation
#follow
for such contents follow below:
1. www.linkedin.com/in/govardhan...
2. @navneet066.bsky.social
#ansible
#devops
#devsecops
#automation
#follow
for such contents follow below:
1. www.linkedin.com/in/govardhan...
2. @navneet066.bsky.social
October 23, 2024 at 7:00 PM
Understanding ansible directory structure.
#ansible
#devops
#devsecops
#automation
#follow
for such contents follow below:
1. www.linkedin.com/in/govardhan...
2. @navneet066.bsky.social
#ansible
#devops
#devsecops
#automation
#follow
for such contents follow below:
1. www.linkedin.com/in/govardhan...
2. @navneet066.bsky.social
15. Rule of Optimization: Prototype before polishing. Get it working before you optimize it.
16. Rule of Diversity: Distrust all claims for “one true way”.
17. Rule of Extensibility: Design for the future, because it will be here sooner than you think.
16. Rule of Diversity: Distrust all claims for “one true way”.
17. Rule of Extensibility: Design for the future, because it will be here sooner than you think.
October 22, 2024 at 8:29 PM
15. Rule of Optimization: Prototype before polishing. Get it working before you optimize it.
16. Rule of Diversity: Distrust all claims for “one true way”.
17. Rule of Extensibility: Design for the future, because it will be here sooner than you think.
16. Rule of Diversity: Distrust all claims for “one true way”.
17. Rule of Extensibility: Design for the future, because it will be here sooner than you think.
12. Rule of Repair: When you must fail, fail noisily and as soon as possible.
13. Rule of Economy: Programmer time is expensive; conserve it in preference to machine time.
14. Rule of Generation: Avoid hand-hacking; write programs to write programs when you can.
13. Rule of Economy: Programmer time is expensive; conserve it in preference to machine time.
14. Rule of Generation: Avoid hand-hacking; write programs to write programs when you can.
October 22, 2024 at 8:28 PM
12. Rule of Repair: When you must fail, fail noisily and as soon as possible.
13. Rule of Economy: Programmer time is expensive; conserve it in preference to machine time.
14. Rule of Generation: Avoid hand-hacking; write programs to write programs when you can.
13. Rule of Economy: Programmer time is expensive; conserve it in preference to machine time.
14. Rule of Generation: Avoid hand-hacking; write programs to write programs when you can.
9. Rule of Representation: Fold knowledge into data so program logic can be stupid and robust.
10. Rule of Least Surprise: In interface design, always do the least surprising thing.
11. Rule of Silence: When a program has nothing surprising to say, it should say nothing.
10. Rule of Least Surprise: In interface design, always do the least surprising thing.
11. Rule of Silence: When a program has nothing surprising to say, it should say nothing.
October 22, 2024 at 8:26 PM
9. Rule of Representation: Fold knowledge into data so program logic can be stupid and robust.
10. Rule of Least Surprise: In interface design, always do the least surprising thing.
11. Rule of Silence: When a program has nothing surprising to say, it should say nothing.
10. Rule of Least Surprise: In interface design, always do the least surprising thing.
11. Rule of Silence: When a program has nothing surprising to say, it should say nothing.
6. Rule of Parsimony: Write a big program only when it is clear by demonstration that nothing else will do.
7. Rule of Transparency: Design for visibility to make inspection and debugging easier.
8. Rule of Robustness: Robustness is the child of transparency and simplicity.
7. Rule of Transparency: Design for visibility to make inspection and debugging easier.
8. Rule of Robustness: Robustness is the child of transparency and simplicity.
October 22, 2024 at 8:24 PM
6. Rule of Parsimony: Write a big program only when it is clear by demonstration that nothing else will do.
7. Rule of Transparency: Design for visibility to make inspection and debugging easier.
8. Rule of Robustness: Robustness is the child of transparency and simplicity.
7. Rule of Transparency: Design for visibility to make inspection and debugging easier.
8. Rule of Robustness: Robustness is the child of transparency and simplicity.
3. Rule of Composition: Design programs to be connected to other programs.
4. Rule of Separation: Separate policy from mechanism; separate interfaces from engines.
5. Rule of Simplicity: Design for simplicity; add complexity only where you must.
4. Rule of Separation: Separate policy from mechanism; separate interfaces from engines.
5. Rule of Simplicity: Design for simplicity; add complexity only where you must.
October 22, 2024 at 8:19 PM
3. Rule of Composition: Design programs to be connected to other programs.
4. Rule of Separation: Separate policy from mechanism; separate interfaces from engines.
5. Rule of Simplicity: Design for simplicity; add complexity only where you must.
4. Rule of Separation: Separate policy from mechanism; separate interfaces from engines.
5. Rule of Simplicity: Design for simplicity; add complexity only where you must.
Better software according to Unix Philosophy as described in The Art of Unix Programming
1. Rule of Modularity: Write simple parts connected by clean interfaces.
2. Rule of Clarity: Clarity is better than cleverness.
Continued in comments ...
1. Rule of Modularity: Write simple parts connected by clean interfaces.
2. Rule of Clarity: Clarity is better than cleverness.
Continued in comments ...
October 22, 2024 at 8:18 PM
Better software according to Unix Philosophy as described in The Art of Unix Programming
1. Rule of Modularity: Write simple parts connected by clean interfaces.
2. Rule of Clarity: Clarity is better than cleverness.
Continued in comments ...
1. Rule of Modularity: Write simple parts connected by clean interfaces.
2. Rule of Clarity: Clarity is better than cleverness.
Continued in comments ...
DevOps Vs DevSecOps 👇
𝗗𝗲𝘃𝗢𝗽𝘀 focuses on collaboration and automation between development and operations.
𝗗𝗲𝘃𝗦𝗲𝗰𝗢𝗽𝘀 extends this approach to include security as a core consideration throughout the software development lifecycle.
Courtesy: @techopsexample
www.linkedin.com/posts/techop...
#devops
𝗗𝗲𝘃𝗢𝗽𝘀 focuses on collaboration and automation between development and operations.
𝗗𝗲𝘃𝗦𝗲𝗰𝗢𝗽𝘀 extends this approach to include security as a core consideration throughout the software development lifecycle.
Courtesy: @techopsexample
www.linkedin.com/posts/techop...
#devops
October 21, 2024 at 7:38 AM
DevOps Vs DevSecOps 👇
𝗗𝗲𝘃𝗢𝗽𝘀 focuses on collaboration and automation between development and operations.
𝗗𝗲𝘃𝗦𝗲𝗰𝗢𝗽𝘀 extends this approach to include security as a core consideration throughout the software development lifecycle.
Courtesy: @techopsexample
www.linkedin.com/posts/techop...
#devops
𝗗𝗲𝘃𝗢𝗽𝘀 focuses on collaboration and automation between development and operations.
𝗗𝗲𝘃𝗦𝗲𝗰𝗢𝗽𝘀 extends this approach to include security as a core consideration throughout the software development lifecycle.
Courtesy: @techopsexample
www.linkedin.com/posts/techop...
#devops
October 21, 2024 at 4:09 AM
A clear visualization of API performance shows its impact across various architectures.
#systemdesign
#api
#Kubernetes
#caching
#loadbalancing
#softwareDesign
Follow me for for more such content.
#systemdesign
#api
#Kubernetes
#caching
#loadbalancing
#softwareDesign
Follow me for for more such content.
October 20, 2024 at 5:18 PM
A clear visualization of API performance shows its impact across various architectures.
#systemdesign
#api
#Kubernetes
#caching
#loadbalancing
#softwareDesign
Follow me for for more such content.
#systemdesign
#api
#Kubernetes
#caching
#loadbalancing
#softwareDesign
Follow me for for more such content.