Developer Tharun

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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

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:

1. Create
2. Monitor
3. Manage
4. Destroy

Let's dive deep into each one of them.

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.

Example technologies involve NGINX, Apache, RabbitMQ, Kafka, Hadoop, Traefik, MySQL, PostgreSQL, Aerospike, MongoDB, Redis, MinIO, Kubernetes, Apache Mesos, Marathon, MariaDB, Galera.

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.

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

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.

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:

1. Create
2. Monitor
3. Manage
4. Destroy

Let's dive deep into each one of them.

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.

Example technologies involve NGINX, Apache, RabbitMQ, Kafka, Hadoop, Traefik, MySQL, PostgreSQL, Aerospike, MongoDB, Redis, MinIO, Kubernetes, Apache Mesos, Marathon, MariaDB, Galera.

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.

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

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.

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:

1. Create
2. Monitor
3. Manage
4. Destroy

Let's dive deep into each one of them.

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.

Example technologies involve NGINX, Apache, RabbitMQ, Kafka, Hadoop, Traefik, MySQL, PostgreSQL, Aerospike, MongoDB, Redis, MinIO, Kubernetes, Apache Mesos, Marathon, MariaDB, Galera.

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.

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

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.

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:

1. Create
2. Monitor
3. Manage
4. Destroy

Let's dive deep into each one of them.

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.

Example technologies involve NGINX, Apache, RabbitMQ, Kafka, Hadoop, Traefik, MySQL, PostgreSQL, Aerospike, MongoDB, Redis, MinIO, Kubernetes, Apache Mesos, Marathon, MariaDB, Galera.

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.

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

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.

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:

1. Create
2. Monitor
3. Manage
4. Destroy

Let's dive deep into each one of them.

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.

Example technologies involve NGINX, Apache, RabbitMQ, Kafka, Hadoop, Traefik, MySQL, PostgreSQL, Aerospike, MongoDB, Redis, MinIO, Kubernetes, Apache Mesos, Marathon, MariaDB, Galera.

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.

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

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.

Encryption and it's types, decryption

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.

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.

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.

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.

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.

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

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.

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.

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.

Programming not only consists of coding, learning and applying it. It is also necessary to keep yourself fit. 

In this podcast I have with me dp_says who is a national level badminton player, who has spent his entire life into sports and fitness. He shares with us, few of his unbiased tips and tricks on how to stay fit durign this lockdown and what his daily routine is.

This is Tharun Shiv and you're listening to the Developer Tharun's podcast

My Programming Blog: https://tharunshiv.com

Instagram: @developerTharunduring,,

Dev.to: tharunshiv

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

Most of us want to achieve big in our life, how 'big' that is, is debatable and is unique to each one of us. But there is only one thing that will lead you there. In this podcast I exactly discuss that with dp_says. 

How do you achieve your goals?

What should you be cautious about?

Hope you like this podcast, This is Tharun Shiv, and you're listening to my podcast. Thanks for listening.

We will look at how to start with Programming , which is the best programming language to learn in 2019, 2020, 2021...

Find me on Instagram at : https://instagram.com/developer_tharun

Happy new year! Its new year 2019. I hope y’all really enjoyed the holidays, cause its Christmas time followed by the new year..

Every new year comes up  with a special topic called a New year resolution. Everyone knows that. Now if you don't know what a new year resolution is, then it is nothing but a set of decisions that a person takes and makes sure that he keeps up with it throughout his life.

Have you made up your new year resolution yet? If yes , then let me know. Cause I’m coming up with reasons why you shouldn’t have a resolution and reasons why you should have them. And if you should have them then how do you make some and achieve them. As a bonus I will be sharing the 10 tactics to make the new year the new better you.

Hi there, I’m Tharun. You’re listening a being a pro, a one stop destination where you can learn what being a pro is like. 

Now talking about my personal experience about the new year resolutions, I’ve had a pretty bad record of keeping up with them , the reason not being the fact that I became worse, the reason was the I became better in the fields that I had not planned for in the beginning of the year.

Now I think this is one of the main reasons why you should not care about having a new year resolution. If you’re spending time charting up what you want to do, how much you want to do and then if you’re finding something better than what you had planned, then you would be definitely making a switch, which makes the planned resolutions a waste.

So who doesn’t need a new year resolution? 

1. If you are determined enough and all you see is your Goals Goals Goals… and nothing else in your way.
2. If you are surrounded by like minded and motivated people who will always inspire you and motivate you to move forward no matter what.

Now this is not always gonna happen. Everyone is neither a self-motivated person as a beginner nor would they have amazing people around them. And also When you’re training yourself to become a professional ,then there will be several options out there and you will take the most time deciding between them. So if you think that you’re gonna settle up with one technology, then chances are that due to say business needs, feature needs, client needs you may tend to deviate into a better or worst track.

10 Tactics to make 2019 a WOW.

1. Exercise first thing every morning
2. Read for 60 minutes  each day, whether its a book or a course or some new talent or language.
3. Speak your truth even when its scary. I personally do this always, and trust me, each and every time it turns out to be Gold.
4. Delete the dream stealers from your life. Quality matters not quantity. Have 3 good friends, more than enough.
5. Be around art+nature often.
6. Do a one page plan to make 2019 great.
7. Write in a journal daily
8. Do the things that terriffy you, in a positive way.
9. Be the kindest person you know, you never know who will repay for your kindness. But at the same time dont give kindness with an expectation.
10. Make personal mastery job number 1. Work towards self development and thats not the only thing that strengthens you , but also helping others will improve your personal skills.