Roadmap To Learn Data Science & Machine Learning | How To Learn Data Science & Machine Learning | Resources - Developer Tharun

1
Save hours of work with Version control system | keep gitlab github in sync | Become a better Site Reliability Engineer | Engineering 3:33

3 years ago3:33

3:33

Link to the article: https://dev.to/developertharun/8-ways-to-become-a-better-sre-right-now-8-non-technical-characteristics-to-have-3n4p Link to the YouTube video: https://youtu.be/2drsyhJzcao Subscribe the podcast if you like it! Thanks for listening. Thank you for listening to my Podcast. Follow my podcast if you find it helpful. Check out my other episodes. I talk about programming & software engineering. YouTube: https://youtube.com/c/developerTharun Blog Article on: https://tharunshiv.com Instagram: @developerTharun Dev.to: https://dev.to/developertharun Udemy: https://www.udemy.com/user/tharun-shiv/ LinkedIn: https://linkedin.com/in/tharunshiv…

1
Think before you hit ENTER! | Power of sudo | TMUX | Become a better Site Reliability Engineer | Engineering 2:59

3 years ago2:59

2:59

Link to the article: https://dev.to/developertharun/8-ways-to-become-a-better-sre-right-now-8-non-technical-characteristics-to-have-3n4p Link to the YouTube video: https://youtu.be/2drsyhJzcao Subscribe the podcast if you like it! Thanks for listening. Thank you for listening to my Podcast. Follow my podcast if you find it helpful. Check out my other episodes. I talk about programming & software engineering. YouTube: https://youtube.com/c/developerTharun Blog Article on: https://tharunshiv.com Instagram: @developerTharun Dev.to: https://dev.to/developertharun Udemy: https://www.udemy.com/user/tharun-shiv/ LinkedIn: https://linkedin.com/in/tharunshiv…

1
When you watch series while working on production | Attention is the key | Become a better Site Reliability Engineer | Engineering 3:04

3 years ago3:04

3:04

Link to the article: https://dev.to/developertharun/8-ways-to-become-a-better-sre-right-now-8-non-technical-characteristics-to-have-3n4p Link to the YouTube video: https://youtu.be/2drsyhJzcao Subscribe the podcast if you like it! Thanks for listening. Thank you for listening to my Podcast. Follow my podcast if you find it helpful. Check out my other episodes. I talk about programming & software engineering. YouTube: https://youtube.com/c/developerTharun Blog Article on: https://tharunshiv.com Instagram: @developerTharun Dev.to: https://dev.to/developertharun Udemy: https://www.udemy.com/user/tharun-shiv/ LinkedIn: https://linkedin.com/in/tharunshiv…

1
Stop being spoonfed right away | Become a better SRE Site Reliability Engineer | Engineering | Backend | Tharun Shiv | Developer Tharun 2:22

3 years ago2:22

2:22

Link to the article: https://dev.to/developertharun/8-ways-to-become-a-better-sre-right-now-8-non-technical-characteristics-to-have-3n4p Link to the YouTube video: https://youtu.be/2drsyhJzcao Subscribe the podcast if you like it! Thanks for listening.

1
Reason why you lag behind the team | Become a better SRE Site Reliability Engineer | Engineering | Backend | Tharun Shiv | Developer Tharun 3:47

3 years ago3:47

3:47

Link to the article: https://dev.to/developertharun/8-ways-to-become-a-better-sre-right-now-8-non-technical-characteristics-to-have-3n4p Link to the YouTube video: https://youtu.be/2drsyhJzcao Subscribe the podcast if you like it! Thanks for listening.

1
Communicate well or suffer | How to communicate well as an SRE / Engineer at work | Communication tips for work | Work from Home | Tharun Shiv 5:20

3 years ago5:20

5:20

Subscribe to the podcast to get latest episodes 1. SRE is all about the right Mindset a. No blame game b. Thirst to solve As an SRE we deal with multiple components and are a bridge between the users and the application. Even though the application is well written, a bigger responsibility falls upon SRE to keep the applications and the services it uses up and running. In this process, there might be a few situations where one of the SRE does a mistake that causes a disruption or even an outage. When this happens, the first thing to happen shouldn't be to blame anyone for the outage, but the following has to be performed. i. Fix the issue ii. Write an RCA ( Root Cause Analysis ) that mentions why the issue occurred in the first place, the names can be anonymous. iii. Mention the first aid and the fix for the issue iv. Discuss how the issue can be prevented the next time v. Set an ETA for the fix Another aspect is to have the right mindset to solve problems. As an SRE you have the responsibility to optimize the infrastructure, fix issues, build automation tools, monitoring tools, and more, which requires a lot of problem-solving skills. Unless you have the thirst to solve the problems, you will only feel more stressed out, or even worse, would cause issues. 2. Communication a. Overcommunication is not a problem b. Be kind and show empathy Are you performing a production activity or even a stage change that could affect other teams? Have you made progress in the project that you are working on? Make sure to keep the necessary stakeholders in sync always. Write emails, send slack messages well in advance before the production activity, just before and after the activity. It might sound like over-communication, but trust me, as the company scales, you need to keep everyone relevant to the component that you are working on in sync. This way, if they have to take any actions from their side, they will do it, or if they face any issues post-activity they'll know who the right person to get in touch with is. One other important characteristic to have as a human being is to be kind and show empathy. This will apply to all levels of engineering on either side of the conversation, period. Whether someone asks a silly question, or does a mistake, or behaves rudely with you, you should never mirror that behavior. 3. Stay synced with the team a. Do not miss team meetings b. Prevent duplication of work c. Do not compete, but contribute In this work from home ( WFH ) period, the only time where you have an opportunity to speak to your teammates is during a team meet. The reason why this is special is, you get an opportunity to stay synced with your team on what they all are working on, whether they are blocked on any tasks, how you can contribute to their tasks and also you will be using this opportunity to convey on what you are working on and get help if necessary. This also prevents duplication of work. 4. Shadow teammates on tasks and issues The best way to learn is by doing it hands-on and the best way to begin would be by watching how it is done. I also believe that the best way to retain the learned information is by performing it repeatedly. This also includes watching your teammates perform the activities. It ensures that the activity is done without any mistakes when there are several eyes to watch it. 5. No Spoon-feeding, do homework Do not expect all details to be taught by your teammates and seniors. Read the documentation, watch tutorials, read engineering blogs, practice on your own, and suggest improvisations. Even a well-built system will have much more efficient solutions, that you can propose…

1
Why you should stop blaming others right away? | Tharun Shiv | SRE Mindset | Become a better Site Reliability Engineering 2:34

3 years ago2:34

2:34

Subscribe to the podcast to get latest episodes 1. SRE is all about the right Mindset a. No blame game b. Thirst to solve As an SRE we deal with multiple components and are a bridge between the users and the application. Even though the application is well written, a bigger responsibility falls upon SRE to keep the applications and the services it uses up and running. In this process, there might be a few situations where one of the SRE does a mistake that causes a disruption or even an outage. When this happens, the first thing to happen shouldn't be to blame anyone for the outage, but the following has to be performed. i. Fix the issue ii. Write an RCA ( Root Cause Analysis ) that mentions why the issue occurred in the first place, the names can be anonymous. iii. Mention the first aid and the fix for the issue iv. Discuss how the issue can be prevented the next time v. Set an ETA for the fix Another aspect is to have the right mindset to solve problems. As an SRE you have the responsibility to optimize the infrastructure, fix issues, build automation tools, monitoring tools, and more, which requires a lot of problem-solving skills. Unless you have the thirst to solve the problems, you will only feel more stressed out, or even worse, would cause issues. 2. Communication a. Overcommunication is not a problem b. Be kind and show empathy Are you performing a production activity or even a stage change that could affect other teams? Have you made progress in the project that you are working on? Make sure to keep the necessary stakeholders in sync always. Write emails, send slack messages well in advance before the production activity, just before and after the activity. It might sound like over-communication, but trust me, as the company scales, you need to keep everyone relevant to the component that you are working on in sync. This way, if they have to take any actions from their side, they will do it, or if they face any issues post-activity they'll know who the right person to get in touch with is. One other important characteristic to have as a human being is to be kind and show empathy. This will apply to all levels of engineering on either side of the conversation, period. Whether someone asks a silly question, or does a mistake, or behaves rudely with you, you should never mirror that behavior. 3. Stay synced with the team a. Do not miss team meetings b. Prevent duplication of work c. Do not compete, but contribute In this work from home ( WFH ) period, the only time where you have an opportunity to speak to your teammates is during a team meet. The reason why this is special is, you get an opportunity to stay synced with your team on what they all are working on, whether they are blocked on any tasks, how you can contribute to their tasks and also you will be using this opportunity to convey on what you are working on and get help if necessary. This also prevents duplication of work. 4. Shadow teammates on tasks and issues The best way to learn is by doing it hands-on and the best way to begin would be by watching how it is done. I also believe that the best way to retain the learned information is by performing it repeatedly. This also includes watching your teammates perform the activities. It ensures that the activity is done without any mistakes when there are several eyes to watch it. 5. No Spoon-feeding, do homework Do not expect all details to be taught by your teammates and seniors. Read the documentation, watch tutorials, read engineering blogs, practice on your own, and suggest improvisations. Even a well-built system will have much more efficient solutions, that you can propose…

1
Stop running a service as a Root user RIGHT NOW! | Production Hardening | Tharun Shiv | Vulnerability | Secure your servers 2:59

3 years ago2:59

2:59

Link to the complete episode: https://anchor.fm/dashboard/episode/e1cjm7b Hey there! Follow the podcast if you like the episode This is Tharun. In the Developer Tharun Podcast, I speak about Software Engineering Thank you for Listening In this Episode Ways in which you can secure your vault server Hashicorp Vault is a secrets management engine And more... Thank you for listening to my Podcast. Follow my podcast if you find it helpful. Check out my other episodes. I talk about programming & software engineering. YouTube: https://youtube.com/c/developerTharun Blog Article on: https://tharunshiv.com Instagram: @developerTharun Dev.to: https://dev.to/developertharun Udemy: https://www.udemy.com/user/tharun-shiv/ LinkedIn: https://linkedin.com/in/tharunshiv…

1
8 ways to become to better SRE today! Site reliability Engineering | 8 tips to follow as an SRE | SRE Mindset | Non Technical SRE 22:02

3 years ago22:02

22:02

Site reliability engineering Site Reliability Engineering, also popularly referred to as the SRE, is a role in Computer Science Engineering where the main purpose is to provision, maintain, monitor, and manage the infrastructure in order to provide maximum application uptime and reliability. SRE is an emerging role, but the tasks that the SRE does were always there ever since the first application that was developed. The scope of the software developers ends where they write code to develop the application and right from setting up the infrastructure, the various services that run on them, the network connectivity that is required, providing a platform for the application to run and making sure every part of the application is up and running reliably 24x7 is the duty of an SRE. In fact, we can consider Site Reliability Engineers are the strong bridge between the users and a reliable application. Now, in order to explain the different responsibilities of an SRE, I have divided it into 4 different categories. I have always seen SRE this way, and definitely not as some ad-hoc process. The four categories in which I would classify the tasks of a Site Reliability Engineer are: Create Monitor Manage Destroy Let's dive deep into each one of them. Create 1. Provision virtual machines / PXE Baremetals SREs are responsible for provisioning the virtual machines with the requested resources in terms of CPU, memory, disks, network configurations, and operating system. They are also responsible to be rack aware during provisioning. Example operating systems involve Linux Ubuntu, CentOS, Windows. 2. Setup services Example technologies involve NGINX, Apache, RabbitMQ, Kafka, Hadoop, Traefik, MySQL, PostgreSQL, Aerospike, MongoDB, Redis, MinIO, Kubernetes, Apache Mesos, Marathon, MariaDB, Galera. 3. Optimize the infrastructure Since there are several components and services that are being used in the infrastructure, there is a scope for improvements in terms of performance, efficiency, and security. The SRE optimizes the components by keeping them up to date, choosing the right service for the right job, patching the servers. 4. Write monitoring scripts When the SRE are involved in maintaining an infrastructure of any size, they never underestimate any component of the infrastructure and write a monitoring script to monitor the components and metrics of each and every one of them. This provides the ability to get real-time alerts on any of the components malfunctioning and also a better view of the infrastructure. The SRE uses programming languages like Bash, Python, Golang, Perl, and tools like daemon processes, Riemann, InfluxDB, OpenTSDB, Kafka, Grafana, Prometheus, and APIs to monitor the infrastructure 5. Write automation scripts If there are more than 10 steps to be performed and chances are that the task has to be performed more than once, the SRE never hesitate to automate the task. This saves time and also prevents human error. The SRE uses programming languages like Bash, Python, Golang, Perl, Ansible to automate the tasks. 6. Manage users on the machines…

1
How a Site Reliability Engineer destroys the infrastructure? SRE | Tharun Shiv 5:54

3 years ago5:54

5:54

Site reliability engineering Site Reliability Engineering, also popularly referred to as the SRE, is a role in Computer Science Engineering where the main purpose is to provision, maintain, monitor, and manage the infrastructure in order to provide maximum application uptime and reliability. SRE is an emerging role, but the tasks that the SRE does were always there ever since the first application that was developed. The scope of the software developers ends where they write code to develop the application and right from setting up the infrastructure, the various services that run on them, the network connectivity that is required, providing a platform for the application to run and making sure every part of the application is up and running reliably 24x7 is the duty of an SRE. In fact, we can consider Site Reliability Engineers are the strong bridge between the users and a reliable application. Now, in order to explain the different responsibilities of an SRE, I have divided it into 4 different categories. I have always seen SRE this way, and definitely not as some ad-hoc process. The four categories in which I would classify the tasks of a Site Reliability Engineer are: Create Monitor Manage Destroy Let's dive deep into each one of them. Create 1. Provision virtual machines / PXE Baremetals SREs are responsible for provisioning the virtual machines with the requested resources in terms of CPU, memory, disks, network configurations, and operating system. They are also responsible to be rack aware during provisioning. Example operating systems involve Linux Ubuntu, CentOS, Windows. 2. Setup services Example technologies involve NGINX, Apache, RabbitMQ, Kafka, Hadoop, Traefik, MySQL, PostgreSQL, Aerospike, MongoDB, Redis, MinIO, Kubernetes, Apache Mesos, Marathon, MariaDB, Galera. 3. Optimize the infrastructure Since there are several components and services that are being used in the infrastructure, there is a scope for improvements in terms of performance, efficiency, and security. The SRE optimizes the components by keeping them up to date, choosing the right service for the right job, patching the servers. 4. Write monitoring scripts When the SRE are involved in maintaining an infrastructure of any size, they never underestimate any component of the infrastructure and write a monitoring script to monitor the components and metrics of each and every one of them. This provides the ability to get real-time alerts on any of the components malfunctioning and also a better view of the infrastructure. The SRE uses programming languages like Bash, Python, Golang, Perl, and tools like daemon processes, Riemann, InfluxDB, OpenTSDB, Kafka, Grafana, Prometheus, and APIs to monitor the infrastructure 5. Write automation scripts If there are more than 10 steps to be performed and chances are that the task has to be performed more than once, the SRE never hesitate to automate the task. This saves time and also prevents human error. The SRE uses programming languages like Bash, Python, Golang, Perl, Ansible to automate the tasks. 6. Manage users on the machines…

1
How a Site Reliability Engineer maintains the infrastructure? SRE | Tharun Shiv 5:48

3 years ago5:48

5:48

Site reliability engineering Site Reliability Engineering, also popularly referred to as the SRE, is a role in Computer Science Engineering where the main purpose is to provision, maintain, monitor, and manage the infrastructure in order to provide maximum application uptime and reliability. SRE is an emerging role, but the tasks that the SRE does were always there ever since the first application that was developed. The scope of the software developers ends where they write code to develop the application and right from setting up the infrastructure, the various services that run on them, the network connectivity that is required, providing a platform for the application to run and making sure every part of the application is up and running reliably 24x7 is the duty of an SRE. In fact, we can consider Site Reliability Engineers are the strong bridge between the users and a reliable application. Now, in order to explain the different responsibilities of an SRE, I have divided it into 4 different categories. I have always seen SRE this way, and definitely not as some ad-hoc process. The four categories in which I would classify the tasks of a Site Reliability Engineer are: Create Monitor Manage Destroy Let's dive deep into each one of them. Create 1. Provision virtual machines / PXE Baremetals SREs are responsible for provisioning the virtual machines with the requested resources in terms of CPU, memory, disks, network configurations, and operating system. They are also responsible to be rack aware during provisioning. Example operating systems involve Linux Ubuntu, CentOS, Windows. 2. Setup services Example technologies involve NGINX, Apache, RabbitMQ, Kafka, Hadoop, Traefik, MySQL, PostgreSQL, Aerospike, MongoDB, Redis, MinIO, Kubernetes, Apache Mesos, Marathon, MariaDB, Galera. 3. Optimize the infrastructure Since there are several components and services that are being used in the infrastructure, there is a scope for improvements in terms of performance, efficiency, and security. The SRE optimizes the components by keeping them up to date, choosing the right service for the right job, patching the servers. 4. Write monitoring scripts When the SRE are involved in maintaining an infrastructure of any size, they never underestimate any component of the infrastructure and write a monitoring script to monitor the components and metrics of each and every one of them. This provides the ability to get real-time alerts on any of the components malfunctioning and also a better view of the infrastructure. The SRE uses programming languages like Bash, Python, Golang, Perl, and tools like daemon processes, Riemann, InfluxDB, OpenTSDB, Kafka, Grafana, Prometheus, and APIs to monitor the infrastructure 5. Write automation scripts If there are more than 10 steps to be performed and chances are that the task has to be performed more than once, the SRE never hesitate to automate the task. This saves time and also prevents human error. The SRE uses programming languages like Bash, Python, Golang, Perl, Ansible to automate the tasks. 6. Manage users on the machines…

1
How a Site Reliability Engineer monitors the infrastructure? SRE | Tharun Shiv 7:45

3 years ago7:45

7:45

Site reliability engineering Site Reliability Engineering, also popularly referred to as the SRE, is a role in Computer Science Engineering where the main purpose is to provision, maintain, monitor, and manage the infrastructure in order to provide maximum application uptime and reliability. SRE is an emerging role, but the tasks that the SRE does were always there ever since the first application that was developed. The scope of the software developers ends where they write code to develop the application and right from setting up the infrastructure, the various services that run on them, the network connectivity that is required, providing a platform for the application to run and making sure every part of the application is up and running reliably 24x7 is the duty of an SRE. In fact, we can consider Site Reliability Engineers are the strong bridge between the users and a reliable application. Now, in order to explain the different responsibilities of an SRE, I have divided it into 4 different categories. I have always seen SRE this way, and definitely not as some ad-hoc process. The four categories in which I would classify the tasks of a Site Reliability Engineer are: Create Monitor Manage Destroy Let's dive deep into each one of them. Create 1. Provision virtual machines / PXE Baremetals SREs are responsible for provisioning the virtual machines with the requested resources in terms of CPU, memory, disks, network configurations, and operating system. They are also responsible to be rack aware during provisioning. Example operating systems involve Linux Ubuntu, CentOS, Windows. 2. Setup services Example technologies involve NGINX, Apache, RabbitMQ, Kafka, Hadoop, Traefik, MySQL, PostgreSQL, Aerospike, MongoDB, Redis, MinIO, Kubernetes, Apache Mesos, Marathon, MariaDB, Galera. 3. Optimize the infrastructure Since there are several components and services that are being used in the infrastructure, there is a scope for improvements in terms of performance, efficiency, and security. The SRE optimizes the components by keeping them up to date, choosing the right service for the right job, patching the servers. 4. Write monitoring scripts When the SRE are involved in maintaining an infrastructure of any size, they never underestimate any component of the infrastructure and write a monitoring script to monitor the components and metrics of each and every one of them. This provides the ability to get real-time alerts on any of the components malfunctioning and also a better view of the infrastructure. The SRE uses programming languages like Bash, Python, Golang, Perl, and tools like daemon processes, Riemann, InfluxDB, OpenTSDB, Kafka, Grafana, Prometheus, and APIs to monitor the infrastructure 5. Write automation scripts If there are more than 10 steps to be performed and chances are that the task has to be performed more than once, the SRE never hesitate to automate the task. This saves time and also prevents human error. The SRE uses programming languages like Bash, Python, Golang, Perl, Ansible to automate the tasks. 6. Manage users on the machines…

1
How a Site Reliability Engineer is a Creator of the infrastructure? SRE | Tharun Shiv 5:35

3 years ago5:35

5:35

Site reliability engineering Site Reliability Engineering, also popularly referred to as the SRE, is a role in Computer Science Engineering where the main purpose is to provision, maintain, monitor, and manage the infrastructure in order to provide maximum application uptime and reliability. SRE is an emerging role, but the tasks that the SRE does were always there ever since the first application that was developed. The scope of the software developers ends where they write code to develop the application and right from setting up the infrastructure, the various services that run on them, the network connectivity that is required, providing a platform for the application to run and making sure every part of the application is up and running reliably 24x7 is the duty of an SRE. In fact, we can consider Site Reliability Engineers are the strong bridge between the users and a reliable application. Now, in order to explain the different responsibilities of an SRE, I have divided it into 4 different categories. I have always seen SRE this way, and definitely not as some ad-hoc process. The four categories in which I would classify the tasks of a Site Reliability Engineer are: Create Monitor Manage Destroy Let's dive deep into each one of them. Create 1. Provision virtual machines / PXE Baremetals SREs are responsible for provisioning the virtual machines with the requested resources in terms of CPU, memory, disks, network configurations, and operating system. They are also responsible to be rack aware during provisioning. Example operating systems involve Linux Ubuntu, CentOS, Windows. 2. Setup services Example technologies involve NGINX, Apache, RabbitMQ, Kafka, Hadoop, Traefik, MySQL, PostgreSQL, Aerospike, MongoDB, Redis, MinIO, Kubernetes, Apache Mesos, Marathon, MariaDB, Galera. 3. Optimize the infrastructure Since there are several components and services that are being used in the infrastructure, there is a scope for improvements in terms of performance, efficiency, and security. The SRE optimizes the components by keeping them up to date, choosing the right service for the right job, patching the servers. 4. Write monitoring scripts When the SRE are involved in maintaining an infrastructure of any size, they never underestimate any component of the infrastructure and write a monitoring script to monitor the components and metrics of each and every one of them. This provides the ability to get real-time alerts on any of the components malfunctioning and also a better view of the infrastructure. The SRE uses programming languages like Bash, Python, Golang, Perl, and tools like daemon processes, Riemann, InfluxDB, OpenTSDB, Kafka, Grafana, Prometheus, and APIs to monitor the infrastructure 5. Write automation scripts If there are more than 10 steps to be performed and chances are that the task has to be performed more than once, the SRE never hesitate to automate the task. This saves time and also prevents human error. The SRE uses programming languages like Bash, Python, Golang, Perl, Ansible to automate the tasks. 6. Manage users on the machines…

1
A beginner's intro to Encryption and Decryption in cryptography | Tharun Shiv 8:58

3 years ago8:58

8:58

Encryption and it's types, decryption

1
18 ways to attack a Vault Server | Hashicorp Vault Server hardening | Production hardening | Secure a Linux server | Site reliability engineering | Tharun Shiv 31:02

3 years ago31:02

31:02

Hey there! Follow the podcast if you like the episode This is Tharun. In the Developer Tharun Podcast, I speak about Software Engineering Thank you for Listening In this Episode Ways in which you can secure your vault server Hashicorp Vault is a secrets management engine And more... Thank you for listening to my Podcast. Follow my podcast if you find it helpful. Check out my other episodes. I talk about programming & software engineering. YouTube: https://youtube.com/c/developerTharun Blog Article on: https://tharunshiv.com Instagram: @developerTharun Dev.to: https://dev.to/developertharun Udemy: https://www.udemy.com/user/tharun-shiv/ LinkedIn: https://linkedin.com/in/tharunshiv…

1
#2 How does WhatsApp encrypt end to end backups - Part 2 | A system perspective | Cryptography | Tharun Shiv | About encryption & Decryption 25:37

3 years ago25:37

25:37

link to the previous episode: https://anchor.fm/developertharun/episodes/1-How-does-WhatsApp-encrypt-end-to-end-backups---Part-1--A-system-perspective--Cryptography--Tharun-Shiv--About-encryption--Decryption-e1cgt6j Hey there! Follow the podcast if you like the episode This is Tharun. In the Developer Tharun Podcast, I speak about Software Engineering Thank you for Listening In this Episode How whatsapp encrypts backups safely Encryption and decryption And more... Thank you for listening to my Podcast. Follow my podcast if you find it helpful. Check out my other episodes. I talk about programming & software engineering. YouTube: https://youtube.com/c/developerTharun Blog Article on: https://tharunshiv.com Instagram: @developerTharun Dev.to: https://dev.to/developertharun Udemy: https://www.udemy.com/user/tharun-shiv/ LinkedIn: https://linkedin.com/in/tharunshiv…

1
#1 How does WhatsApp encrypt end to end backups - Part 1 | A system perspective | Cryptography | Tharun Shiv | About encryption & Decryption 9:24

3 years ago9:24

9:24

Hey there! Follow the podcast if you like the episode This is Tharun. In the Developer Tharun Podcast, I speak about Software Engineering Thank you for Listening In this Episode How whatsapp encrypts backups safely Encryption and decryption And more... Thank you for listening to my Podcast. Follow my podcast if you find it helpful. Check out my other episodes. I talk about programming & software engineering. YouTube: https://youtube.com/c/developerTharun Blog Article on: https://tharunshiv.com Instagram: @developerTharun Dev.to: https://dev.to/developertharun Udemy: https://www.udemy.com/user/tharun-shiv/ LinkedIn: https://linkedin.com/in/tharunshiv…

1
What is Site Reliability Engineering [ SRE ] | How to think like an SRE | Responsibilities of an SRE | SRE vs System Admin vs DevOps 23:59

3 years ago23:59

23:59

Hey there! Follow the podcast if you like the episode This is Tharun. In the Developer Tharun Podcast, I speak about Software Engineering Thank you for Listening In this Episode Site reliability engineering The 4 aspects of Site Reliability Engineering according to me And more... Thank you for listening to my Podcast. Follow my podcast if you find it helpful. Check out my other episodes. I talk about programming & software engineering. YouTube: https://youtube.com/c/developerTharun Blog Article on: https://tharunshiv.com Instagram: @developerTharun Dev.to: https://dev.to/developertharun Udemy: https://www.udemy.com/user/tharun-shiv/ LinkedIn: https://linkedin.com/in/tharunshiv…

1
Hashicorp Vault | Dev and Prod server setup | Unseal | Policies | TLS setup | Developer Tharun 11:53

3 years ago11:53

11:53

Hey there! Follow the podcast if you like the episode This is Tharun. In the Developer Tharun Podcast, I speak about Software Engineering Thank you for Listening In this Episode Vault server setup flow What is seal/unseal of Vault server? Policies Difference between server in Dev mode & Prod mode And more... Vault stores data in encrypted format. The encryption key that is being used to encrypt/decrypt the data is also stored along with rest of the data in the keyring. When a Vault server starts, it knows where the data resides through the configuration that we provide Vault with but doesn't know how to decrypt the encryption key that is present in the keyring along with the Vault encrypted data. Here comes the master key that is used to decrypt the encryption key which is also present alongside all other Vault data. This master key is also encrypted and we need a special key that can decrypt the master key, this key is known as Unseal key. The Unseal key is generated during the init process using an algorithm known as 'Shamir's secret sharing', where the unseal key is split into certain number of unseal keys 'X' and every time we want to unseal the Vault server we will need a certain number of unseal keys 'Y' and these 'X' and 'Y' values can be decided by the Vault architect when initializing the Vault server. The main intention of creating several unseal keys is to distribute these unseal keys among several stakeholders such that, a minimum number of stake holders are needed to unseal the server or perform major operations on the server. What are policies? Policies help you create rules that define access to various secrets. We can create policies that allow certain level access like create access, update access, read access, delete access and so on. We then assign this policy to a particular authentication mechanism of a user. This user will have only those access mentioned in the policies attached to his credentials. This way, Vault makes sure that we provide minimal and only necessary access to Vault stakeholders. Thank you for listening to my Podcast. Follow my podcast if you find it helpful. Check out my other episodes. I talk about programming & software engineering. YouTube: https://youtube.com/c/developerTharun Blog Article on: https://tharunshiv.com Instagram: @developerTharun Dev.to: https://dev.to/developertharun Udemy: https://www.udemy.com/user/tharun-shiv/ LinkedIn: https://linkedin.com/in/tharunshiv…

1
Hashicorp Vault | What & Why? | All you need to know about Vault | Secrets management 9:05

3 years ago9:05

9:05

Hey there! Follow the podcast if you like the episode This is Tharun. In the Developer Tharun Podcast, I speak about Software Engineering Thank you for Listening In this Episode What is Hashicorp Vault? What are the problems around secrets management? What problems does it solve? Features of Hashicorp Vault And more... Thank you for listening to my Podcast. Follow my podcast if you find it helpful. Check out my other episodes. I talk about programming & software engineering. YouTube: https://youtube.com/c/developerTharun Blog Article on: https://tharunshiv.com Instagram: @developerTharun Dev.to: https://dev.to/developertharun Udemy: https://www.udemy.com/user/tharun-shiv/ LinkedIn: https://linkedin.com/in/tharunshiv…

1
Server virtualization for roadrunners | Hypervisor 11:51

4 years ago11:51

11:51

Introducing Virtualization I know the article made you hungry, let’s get back to the topic. You need to know two basic things: Host machine: Imagine a huge machine on which multiple other smaller machines will be created Guest machine: The multiple smaller machines that are created on top of the huge machine, that uses the resources provided by the huge machine is a guest machine. Virtualization creates a software representation of the underlying hardware resources on a host and shares it among the virtual machines that are created on top of it. Each virtual machine has its own operating system and applications, thereby being able to utilize the resources of a host machine by its guest machines in an isolated manner. A virtual machine ( VM ) is an isolated guest machine that has it’s own operating system and applications. Each VM is completely independent of other VMs running on the same host machine. If you remember our x84 vs x64 architecture systems blog post , the x84 systems are not capable of running more than one operating system or application at a time. The concept of multi-processing came up only with the x64 systems introducing the dual-core, quad-core so on. Because of this reason, the earlier datacenters which were based on x84 systems had to increase the number of servers, whereas the server utilization remained underutilized. Today, this is not the scenario. Virtualization has gone beyond just server virtualization and has reached network virtualization, disk virtualization, and so on. But how is this possible? Hypervisor — The hero of our story The concept of Virtual Machines is made possible only because of the thin layer of software known as the Hypervisor, which is installed on the host machine. The hypervisor enables the virtualization of resources and isolation between the Virtual machines that are created on the same host. This enables efficient and transparent utilization of data center resources. Types of Hypervisors: Type one hypervisors ( Bare-metal hypervisors ) Type two hypervisors ( Hosted hypervisors ) Type one hypervisors Type 1 hypervisors as depicted above lay directly above the physical server and host the virtual machines on top of them. They are also known as bare-metal hypervisors. It has shown far better performance than type two hypervisors. Dynamic resource allocation in Type 1 hypervisor allows VMs to consume resources only as much as they need to be fully functional, even if you allocate more than that. For example, if you allocate 32GB of RAM to a VM, it will not reserve all 32GB of RAM to the VM, but only that resource which it needs to fully function. ( This is not the case with Type 2 hypervisors ). Example: The open-source KVM ( Kernel-based Virtual Machine ) Type two hypervisors Type 2 hypervisors as depicted above have an operating system on top of the physical server layer, over which a type two hypervisor is installed. So, there is a host operating system ( a software layer ) that comes in between the physical server and the type two hypervisor.…

1
x86 vs x64 systems for roadrunners | Developer Tharun 6:49

4 years ago6:49

6:49

x86 Systems x86 is a generic name that is used to refer to all Intel processors that were released after the original 8086 or 8088 variant of Intel processors . The variants like 80286, 80386, 80486 so on.. were named using the convention x86, where the 80 is implicit, and x can be replaced with a number conveniently. These are backward compatible systems. 8086 or 8088 are the various names that are used to Identify the microprocessors of Intel that were released in the 1970s. Registers used in the early x86 systems A Register is a tiny memory holding electronic device that is used by the processor to either store instructions, data or address. These are fundamental units that are used when executing a computer instruction to perform a task. x86 systems ranged from 8-bit, 16-bit and then 32bit . What do these bits refer to? They are the highest number of bits in a single register that exists in the system. Maximum memory limit When we say 32-bit, the number will contain 32 digits with each of them being either 0 or 1. The number system used here is Binary System ( power 2 ). Hence, the maximum possible value here will be 2³², which is 42,94,967,295. These are the maximum number of memory locations that a 32-bit register can access. We can only attach that memory device which the register can completely make use of. Thus, a 32-bit register can cater a maximum of 4GB of RAM . This is because, if each memory location that the register points to can hold 1 byte of data, then 42,94,967,295 bytes = 4.29 G. Although this is theoretical, the actual RAM that can be used will be less than around 3.5G, because of certain parts of the register being used to store other types of data. x64 Systems For the systems that evolved to use 64-bit registers , they initially named it x86–64, but since this sounds longer, the naming was changed to x64 systems. x64 is a generic name that is used to refer to all Intel processors that are 64-bit processors. The x64 systems as mentioned above contains registers that are even capable of storing 64bits in a single register. Theoretical Maximum memory limit When we say 64-bit, the number will contain 64 digits with each of them being either 0 or 1. The number system used here will be Binary system just like the 32-bit family. Hence, the maximum possible value here will be 2⁶⁴. Thus each 64-bit register can cater a maximum of around 18 Quintillion bytes of memory. ( One Quintillion is 10¹⁸ ). Therefore it will be able to handle the usual RAM that we come across everyday effortlessly, including enterprise production servers. Processing power of x64 systems x64 systems come with configurations like dual core, quad core, octa core and so on, which depicts the number of processors that work simultaneously in an integrated circuit. This enables the Operating system to perform tasks parallely. While dual-core has two cores than one single core, every task that it does need not be twice as fast as a single core machine. This is because, even the operating systems and programs that is using the processors should be able to perform parallely using multi processors. Roadrunners is a series that is aimed at delivering concepts as precise as possible. Here, a roadrunner is referred to a person who does things super fast & efficient. Are you a roadrunner? https://medium.com/@tharunshiv/x86-vs-x64-systems-for-roadrunners-18de2d488020…

1
Ep. 5 : App Development Guide • How to make the most out of Engineering? | Developer Tharun Shiv 19:02

4 years ago19:02

19:02

Thank you so much for tuning into this podcast, in this episode, we discuss about the App Development. What is App Development? Different types of app development Comparing Java, Kotlin, React Native, Flutter When to use what? What should you do after studying? How to become a pro in app dev? In this series I talk about the the fields that you can explore as a computer science engineer. we talk about web development, app development, system administration, data science, artificial intelligence, machine learning deep learning, blockchain. We will be diving deeper into each one of these topics in the upcoming podcasts. You are listening to the third episode of how to make the most out of your engineering hope you like it, thank you.…

1
Ep. 4 : Webdev Backend & Database • How to make the most out of Engineering? | Developer Tharun Shiv 9:33

4 years ago9:33

9:33

Thank you so much for tuning into this podcast, in this episode, we discuss about the webdev backend part. What is backend? The programming languages that you can use for backend The libraries and frameworks of JavaScript that you can use for backend development What is a Database? What are the 4 main operations called CRUD that you need to know? What are REST APIs and example to understand them About Authentication In this series I talk about the the fields that you can explore as a computer science engineer. we talk about web development, app development, system administration, data science, artificial intelligence, machine learning deep learning, blockchain. We will be diving deeper into each one of these topics in the upcoming podcasts. You are listening to the third episode of how to make the most out of your engineering hope you like it, thank you.…

1
Ep. 3 : Webdev Frontend • How to make the most out of Engineering? | Developer Tharun Shiv 12:53

4 years ago12:53

12:53

Thank you so much for tuning into this podcast, in this episode, In this series I talk about the the fields that you can explore as a computer science engineer. we talk about web development, app development, system administration, data science, artificial intelligence, machine learning deep learning, blockchain. We will be diving deeper into each one of these topics in the upcoming podcasts. You are listening to the third episode of how to make the most out of your engineering hope you like it, thank you.…

1
Ep. 2 : Be an Explorer • How to make the most out of Engineering? | Developer Tharun Shiv 13:54

4 years ago13:54

13:54

Thank you so much for tuning into this podcast, in this episode, I talked about the the fields that you can explore as a computer science engineer. we talk about web development, app development, system administration, data science, artificial intelligence, machine learning deep learning, blockchain. We will be diving deeper into each one of these topics in the upcoming podcasts. You are listening to the second episode of how to make the most out of your engineering hope you like it, thank you.…

1
Ep. 1 : How much to Study • How to make the most out of Engineering? | Developer Tharun Shiv 11:34

4 years ago11:34

11:34

In this episode I talked about how much each one needs to study during their college. To become successful out of college doesn't mean that you will have to study everything and spend all day studying. based on your future goals you will have to tune the time that you put into studying college stuff. The earlier you realise this the better it is for your future. So in this podcast developer Tharun talks about his own experience at college. Welcome to the series of how to make the most out of engineering, each one of this episode we will be looking at each of the aspects that you need to know and improve at college. every minute is precious with that being said four years of college should not be wasted. Thank you so much for listening to the podcast this is Tharun I hope you enjoy episode.…

1
6 Best resources to learn ANY technology/programming concept - Video | Written | Audio - Tharun 7:48

4 years ago7:48

7:48

5 years ago10:53

10:53

When you start doing something there will be a hundred critics, demotivators, competitors on the way. The ones who learn from all these incidents and improve are the only ones who succeed. Success isn't easy. In this episode dp_says talks about his important Badminton match and what he learned from it for a couple of minutes and then I narrate a motivational story about a painter Panda who is the cousin of the Kung Fu Panda. This story was narrated to me by a YouTuber Hitesh Choudhary. Hope you enjoy this episode. - Tharun Shiv from Developer Tharun…

Amazon eGift Card - Amazon Logo (Animated)

Amazon Basics Multipurpose Copy Printer Paper, 8.5 x 11 inches, 20 lb, 1 Ream, 500 Sheets, 92 Bright, White

Mini Mic Pro Wireless Microphone for iPhone, iPad, Android, Lavalier Microphone for Video Recording - 2 Pack iPhone Mic Crystal Clear Recording with USB-C for Podcast, ASMR

Podcasts Worth a Listen

Developer Tharun « » Roadmap to learn Data Science & Machine Learning | How to learn Data Science & Machine learning | Resources - Developer Tharun - Ep. 18

In this Episode

Thank you for listening to my Podcast. Follow my podcast if you find it helpful. Check out my other episodes. I talk abour programming, web development, data science and other experiences of mine with programming.

YouTube: https://youtube.com/c/developerTharun

Blog Article on: https://tharunshiv.com

Instagram: @developerTharun

Dev.to: https://dev.to/developertharun

Udemy: https://www.udemy.com/user/tharun-shiv/

LinkedIn: https://linkedin.com/in/tharunshiv