DEV Community: Thels Katikireddi

Week Plan 11/08/2020

Thels Katikireddi — Mon, 09 Nov 2020 15:55:50 +0000

Easy Algorithm Problems

https://leetcode.com/problems/is-subsequence/ [Status: Moved from last week]
https://leetcode.com/problems/fibonacci-number/ [Status: Moved from last week]

Azure Fundamentals (AZ-900)

Azure Core-Services: https://docs.microsoft.com/en-us/learn/paths/distinguish-microsoft-azure-core-services/

Az-900-Cloud Concepts- Cloud services -3

Thels Katikireddi — Mon, 09 Nov 2020 13:46:05 +0000

Highlights from
https://docs.microsoft.com/en-us/learn/modules/explore-types-cloud-services/

There are three major categories: IaaS, SaaS, and PaaS.

The shared responsibility model ensures cloud workloads are run securely and in a well-managed way. Depending on the service you are using, the cloud provider is responsible for some aspects of the workload management, and the customer or end-user is responsible for other aspects of the workload management, and in some cases, both share a responsibility.

The following list of cloud service types describes the management responsibilities for the user and the cloud provider as compared to on-premises systems:

IaaS requires the most user management of all the cloud services. The user is responsible for managing the operating systems, data, and applications.
PaaS requires less user management. The cloud provider manages the operating systems, and the user is responsible for the applications and data they run and store.
SaaS requires the least amount of management. The cloud provider is responsible for managing everything, and the end user just uses the software.

Infrastructure as a Service (IaaS) is the most basic category of cloud computing services. With IaaS, you rent IT infrastructure servers and virtual machines (VMs), storage, networks, and operating systems from a cloud provider on a pay-as-you-go basis. It's an instant computing infrastructure, provisioned and managed over the internet.

IaaS characteristics
- Upfront costs. IaaS has no upfront costs. Users pay only for what they consume.
- User ownership. The user is responsible for the purchase, installation, configuration, and management of their own software operating systems, middleware, and applications.
- Cloud provider ownership. The cloud provider is responsible for ensuring that the underlying cloud infrastructure (such as virtual machines, storage and networking) is available for the user.
Common IaaS usage scenarios:
- Migrating workloads.Provides an easy migration path for moving existing applications to the cloud.
- Test and development. IaaS makes scaling development testing environments up and down fast and economical.
- Website hosting. Running websites using IaaS can be less expensive than traditional web hosting.
- Storage, backup, and recovery. IaaS is useful for managing unpredictable demand and steadily growing storage needs. It can also simplify the planning and management of backup and recovery systems.
Advantages:
- No CapEx: Users have no upfront costs.
- Agility: Applications can be made accessible quickly, and deprovisioned whenever needed.
- Consumption-based model: Organizations pay only for what they use and operate under an OpEx model.
- Skills: No deep technical skills are required to deploy, use, and gain the benefits of a public cloud.
- Flexibility: IaaS is the most flexible cloud service as you have control to configure and manage the hardware running your application.
Disadvantages:
- Management: The shared responsibility model applies; the user manages and maintains the services they have provisioned, and the cloud provider manages and maintains the cloud infrastructure.

Platform as a Service (PaaS) Provides an environment for building, testing, and deploying software applications. The goal of PaaS is to help create an application as quickly as possible without having to worry about managing the underlying infrastructure.

For example, when deploying a web application using PaaS, you don't have to install an operating system, web server, or even system updates. PaaS is a complete development and deployment environment in the cloud, with resources that enable organizations to deliver everything from simple cloud-based apps to sophisticated cloud-enabled enterprise applications.

Resources are purchased from a cloud service provider on a pay-as-you-go basis and accessed over a secure Internet connection.

PaaS characteristics
- No Upfront costs. There are no upfront costs, and users pay only for what they consume.
- User ownership. The user is responsible for the development of their own applications.
- Cloud provider ownership. The cloud provider is responsible for operating system management, and network and service configuration.
Common PaaS usage scenarios
- Development framework. PaaS provides a framework that developers can build upon to develop or customize cloud-based applications.
- Analytics or business intelligence. Tools provided as a service with PaaS allow organizations to analyze and mine their data. They can find insights and patterns, and predict outcomes to improve business decisions such as forecasting, product design, and investment returns. PaaS provides the same benefits and considerations as IaaS, but there some additional benefits.
Advantages:
- No CapEx: Users have no upfront costs.
- Agility: PaaS is more agile than IaaS, and users do not need to configure servers for running applications.
- Consumption-based model: Users pay only for what they use, and operate on an OpEx model.
- Skills: No deep technical skills are required to deploy, use, and gain the benefits of PaaS.
- Cloud benefits: Users can leverage the skills and expertise of the cloud provider to ensure their workloads are made secure and highly available. In addition, users can gain access to more cutting-edge development tools and toolsets. They then can apply these tools and toolsets across an application's lifecycle.
- Productivity: Users can focus on application development only, as all platform management is handled by the cloud provider. Working with distributed teams as services is easier, as the platform is accessed over the internet and can be made globally available more easily.
Disadvantages:
- Platform limitations: There may be some limitations to a cloud platform that could affect how an application runs. Any limitations should be taken into consideration when considering which PaaS platform is best suited for a workload.

Software as a Service (SaaS) is software that is centrally hosted and managed for the end customer. It allows users to connect to and use cloud-based apps over the internet. Common examples are email, calendars, and office tools such as Microsoft 365.

SaaS is typically licensed through a monthly or annual subscription, and Microsoft 365 is an example of SaaS software.

SaaS characteristics
- No Upfront costs. Users have no upfront costs; they pay a subscription, typically on a monthly or annual basis.
- User ownership. Users just use the application software; they are not responsible for any maintenance or management of that software.
- Cloud provider ownership. The cloud provider is responsible for the provision, management, and maintenance of the application software.
- Common SaaS usage scenarios Examples of Microsoft SaaS services include Microsoft 365, Skype, and Microsoft Dynamics CRM Online.

SaaS provides the same benefits as IaaS, but again there some additional benefits.

Advantages:
- No CapEx: Users don’t have any upfront costs.
- Agility: Users can provide staff with access to the latest software quickly and easily.
- Pay-as-you-go pricing model: Users pay for the software they use on a subscription model, typically monthly or yearly, regardless of how much they use the software.
- Flexibility: Users can access the same application data from anywhere.
Disadvantages:
- Software limitations: Since you are using as-is software you don't have direct control of features.

AZ-900 Cloud Concepts - Types of cloud models-4

Thels Katikireddi — Mon, 09 Nov 2020 12:53:59 +0000

Highlights from the below link
https://docs.microsoft.com/en-us/learn/modules/distinguish-types-cloud-models/

There are three different cloud deployment models:
Public Cloud, Private Cloud, and Hybrid Cloud.

A cloud deployment model defines where your data is stored and how your customers interact with it – how do they get to it, and where do the applications run? It also depends on how much of your own infrastructure you want or need to manage.

Public cloud

A public cloud is owned by the cloud services provider. It provides resources and services to multiple organizations and users, who connect to the cloud service via a secure network connection, typically over the internet.
Public cloud models have the following characteristics:
- Ownership - Resources are owned and operated by cloud service providers.
- Multiple end users - Public cloud modes may make their resources available to multiple organizations.
- Public access - Public access allows the public to access the desired cloud services.
- Availability - Public cloud is the most common cloud-type deployment model.
- Connectivity - Users and organizations are typically connected to the public cloud over the internet using a web browser.
- Skills - Public clouds do not require deep technical knowledge to set up and use its resources.
Advantages:
- No CapEx. You don’t have to buy a new server in order to scale.
- Agility. Applications can be made accessible quickly and de-provisioned whenever needed.
- Consumption-based model. Organizations pay only for what they use and operate under an OpEx model.
- Maintenance. Organizations have no responsibility for hardware maintenance or updates.
- Skills. No deep technical skills are required to deploy, use, and gain the benefits of a public cloud. Organizations can leverage the skills and expertise of the cloud provider to ensure workloads are secure, safe, and highly available.
Disadvantages:
- Security. There may be specific security requirements that cannot be met by using public cloud.
- Compliance. There may be government policies, industry standards, or legal requirements which public clouds cannot meet.
- Ownership. Organizations don't own the hardware or services and cannot manage them as they may wish.
- Specific scenarios. If organizations have a unique business requirement, such as having to maintain a legacy application, it may be hard to meet that requirement with public cloud services.

Private cloud

A private cloud is owned and operated by the organization. They have their own datacenter and provide self-service access to compute resources to users within their organization.
Private cloud models have the following characteristics:
- Ownership. The owner and user of the cloud services are the same.
- Hardware. The owner is entirely responsible for the purchase, maintenance, and management of the cloud hardware.
- Users. A private cloud operates only within one organization and cloud computing resources are used exclusively by a single business or organization.
- Connectivity. A connection to a private cloud is typically made over a private network that is highly secure.
- Public access. Does not provide access to the public.
- Skills. Requires deep technical knowledge to set up, manage, and maintain.
- Use cases: Store Organization Sensitive data, Govt Data etc.
Advantages:
- Control. Organizations have complete control over the resources.
- Security. Organizations have complete control over security.
- Compliance. If organizations have very strict security, compliance, or legal requirements, a private cloud may be the only viable option.
- **Specific scenarios. If an organization has a specific scenario not easily supported by a public cloud provider (such as having to maintain a legacy application), it may be preferable to run the application locally.
Disadvantages:
- Upfront CapEx. Hardware must be purchased for start-up and maintenance.
- Agility. Private clouds are not as agile as public clouds, because you need to purchase and set up all the underlying infrastructure before they can be leveraged.
- Maintenance. Organizations have the responsibility for hardware maintenance and updates.
- Skills. Private clouds require in-house IT skills and expertise that may be hard to get or be costly.

Hybrid cloud

A hybrid cloud combines both public and private clouds, allowing you to run your applications in the most appropriate location.
Hybrid cloud models have the following characteristics:
- Resource location. Specific resources run or are used in a public cloud, and others run or are used in a private cloud.
- Cost and efficiency. Hybrid cloud models allow an organization to leverage some of the benefits of cost, efficiency, and scale that are available with a public cloud model.
- Control. Organizations retain management control in private clouds.
- Skills. Technical skills are still required to maintain the private cloud and ensure both cloud models can operate together.
Advantages:
- Flexibility. The most flexible scenario: with a hybrid cloud setup, an organization can decide to run their applications either in a private cloud or in a public cloud.
- Costs. Organizations can take advantage of economies of scale from public cloud providers for services and resources as they wish. This allows them to access cheaper storage than they can provide themselves.
- Control. Organizations can still access resources over which they have total control.
- Security. Organizations can still access resources for which they are responsible for security.
- Compliance. Organizations maintain the ability to comply with strict security, compliance, or legal requirements as needed.
- Specific scenarios. Organizations maintain the ability to support specific scenarios not easily supported by a public cloud provider, such as running legacy applications.
Disadvantages:
- Upfront CapEx. Upfront CapEx is still required before organizations can leverage a private cloud.
- Costs. Purchasing and maintaining a private cloud to use alongside the public cloud can be more expensive than selecting a single deployment model.
- Skills. Deep technical skills are still required to be able to set up a private cloud.
- Ease of management. Organizations need to ensure there are clear guidelines to avoid confusion, complications, or misuse.

Week Plan 11/1/2020

Thels Katikireddi — Mon, 02 Nov 2020 16:37:23 +0000

Week Plan:

Easy Algorithm Problems
- https://leetcode.com/problems/is-subsequence/ [Status Not complete: Moving to Next Week]
- https://leetcode.com/problems/fibonacci-number/ [Status Not complete: Moving to Next Week]
Azure Fundamentals (AZ-900)
- https://docs.microsoft.com/en-us/learn/paths/explore-microsoft-azure-cloud-concepts/ [Status: Completed remaining modules] https://dev.to/thelsk7/az-900-cloud-concepts-cloud-services-5gp4

Summary:

Completed Pending Azure Cloud concepts modules.
Algorithm problems is still not completed. Got distracted due to Elections and other personal work.

Kaigen:

Avoid distractions and work on the weekly goal. Try to spend at least 30 minutes to 1 hour each day on the weekly goal.

AZ-900 Cloud Concepts - Why Cloud Services-2

Thels Katikireddi — Sat, 31 Oct 2020 23:31:52 +0000

Highlights from Module https://docs.microsoft.com/en-us/learn/modules/discuss-why-cloud-services/

Quick refresh before taking exam.

Discuss why cloud services

Cloud Computing is the delivery of computing services—servers, storage, databases, networking, software, analytics, intelligence and more—over the internet (the cloud), enabling faster innovation, flexible resources, and economies of scale. You typically pay only for cloud services you use, helping lower your operating costs, run your infrastructure more efficiently, and scale as your business needs change.
The company providing these services is referred to as a cloud provider. Ex: Microsoft Azure, Amazon Web Services (AWS), and the Google Cloud Platform (GCP). The cloud provider is responsible for the physical hardware required to execute your work, in addition to keeping it up to date.
Cloud computing providers offer a wide range of services. Typically, these services include:
- Compute power - such as Linux servers or web applications.
- Storage - such as files and databases.
- Networking - such as secure connections between the cloud provider and your company.
- Analytics - such as visualizing telemetry and performance data.
Compute power:
- A VM is an emulation of a computer - just like your desktop or laptop you're using now. Each VM includes an operating system and hardware that appears to the user like a physical computer running Windows or Linux. You can then install whatever software you need to do the tasks you want to run in the cloud.
- VMs aren't the only computing choice - there are two other popular options: containers and serverless computing.
- Containers provide a consistent, isolated execution environment for applications. They're similar to VMs except they don't require a guest operating system. Instead, the application and all its dependencies is packaged into a "container" and then a standard runtime environment is used to execute the app. This allows the container to start up in just a few seconds, because there's no OS to boot and initialize. You only need the app to launch.
- The open-source project, Docker, is one of the leading platforms for managing containers. Docker containers provide an efficient, lightweight approach to application deployment because they allow different components of the application to be deployed independently into different containers. Multiple containers can be run on a single machine, and containers can be moved between machines. The portability of the container makes it easy for applications to be deployed in multiple environments, either on-premises or in the cloud, often with no changes to the application.
- Serverless computing lets you run application code without creating, configuring, or maintaining a server. The core idea is that your application is broken into separate functions that run when triggered by some action. This is ideal for automated tasks - for example, you can build a serverless process that automatically sends an email confirmation after a customer makes an online purchase.
- The serverless model differs from VMs and containers in which you only pay for the processing time used by each function as it executes. VMs and containers are charged while they're running - even if the applications on them are idle. This architecture doesn't work for every app - but when the app logic can be separated to independent units, you can test them separately, update them separately, and launch them in microseconds, making this approach the fastest option for deployment.

Storage
- The advantage to using cloud-based data storage is you can scale to meet your needs. In some cases, the storage can even expand and contract automatically - so you pay for exactly what you need at any given point in time.
Explore key cloud concepts
Cloud services have characteristics and considerations, some of which are outlined and explained below:
- High availability. The ability to keep services up and running for long periods of time, with very little downtime, depending on the service in question.
- Scalability. The ability to increase or decrease resources for any given workload. You can add additional resources to service a workload (known as scaling out), or add additional capabilities to manage an increase in demand to the existing resource (known as scaling up). Scalability doesn't have to be done automatically.
- Elasticity. The ability to automatically or dynamically increase or decrease resources as needed. Elastic resources match the current needs, and resources are added or removed automatically to meet future needs when it’s needed (and from the most advantageous geographic location). A distinction between scalability and elasticity is that elasticity is done automatically.
- Agility. The ability to react quickly. Cloud services can allocate and deallocate resources quickly. They are provided on-demand via self-service, so vast amounts of computing resources can be provisioned in minutes. There is no manual intervention in provisioning or deprovisioning services.
- Fault tolerance. The ability to remain up and running even in the event of a component (or service) no longer functioning. Typically, redundancy is built into cloud services architecture, so if one component fails, a backup component takes its place. This type of service is said to be tolerant of faults.
- Disaster recovery. The ability to recover from an event which has taken down a cloud service. Cloud services disaster recovery can happen very quickly, with automation and services being readily available to use.
- Global reach. The ability to reach audiences around the globe. Cloud services can have a presence in various regions across the globe, which you and your customer can access, giving you a presence in those regions even though you may not have any infrastructure in that region.
- Customer latency capabilities. If customers are experiencing slowness with a particular cloud service, they are said to be experiencing some latency. Cloud services have the ability to deploy resources in datacenters around the globe, which addresses any customer latency issues.
- Predictive cost considerations. The ability for users to predict the costs they will incur for a particular cloud service. Costs for individual services are made available, and tools are provided to allow you to predict the costs a service will incur. You can also perform analysis based on planned growth.
- Technical skill requirements and considerations. Cloud services can provide and manage hardware and software for workloads. Getting a workload up and running with cloud services demands less technical resources than having IT teams build and maintain a physical infrastructure for handling the same workload. A user can be an expert in the application they want to run without requiring skills to build and maintain the underlying hardware and software infrastructure.
- Increased productivity. On-site datacenters typically require a lot of hardware setup (otherwise known as racking and stacking), software patching, and other time-consuming IT management chores. Cloud computing eliminates the need for many of these tasks. This allows IT teams to spend time focusing on achieving more important business goals.
- Security. Cloud providers offer a broad set of policies, technologies, controls, and expert technology skills that can provide better security than most organizations can otherwise achieve. The result is strengthened security, which helps to protect data, apps, and infrastructure from potential threats.
- * The concept of economies of scale is the ability to reduce costs and gain efficiency when operating at a larger scale in comparison to operating at a smaller scale. Cloud providers such as Microsoft, Google, and Amazon are large businesses, and are able to leverage the benefits of economies of scale, and then pass those benefits on to their customers.
There are two approaches to investment, commonly referred to as:
- Capital Expenditure (CapEx): This is the up front spending of money on physical infrastructure, and then deducting that up front expense over time. The up front cost from CapEx has a value that reduces over time.
- Operational Expenditure (OpEx): This is spending money on services or products now and being billed for them now. You can deduct this expense in the same year you spend it. There is no up front cost, as you pay for a service or product as you use it.
CapEx computing costs:
- Server costs
- Storage costs
- Network costs
- Backup and archive costs
- Organization continuity and disaster recovery costs
- Datacenter infrastructure costs
- Technical personnel
OpEx cloud computing costs
- Leasing software and customized features
- Scaling charges based on usage/demand instead of fixed hardware or capacity
- Billing at the user or organization level
Benefits of CapEx
- With capital expenditures, you plan your expenses at the start of a project or budget period. Your costs are fixed, meaning you know exactly how much is being spent. This is appealing when you need to predict the expenses before a project starts due to a limited budget.
Benefits of OpEx
- Demand and growth can be unpredictable and can outpace expectation, which is a challenge for the CapEx model.
- With the OpEx model, companies wanting to try a new product or service don't need to invest in equipment. Instead, they pay as much or as little for the infrastructure as required.
- OpEx is particularly appealing if the demand fluctuates or is unknown. Cloud services are often said to be agile. Cloud agility is the ability to rapidly change an IT infrastructure to adapt to the evolving needs of the business.
Define consumption-based models
- Cloud service providers operate on a consumption-based model, which means that end users only pay for the resources that they use. Whatever they use is what they pay for.
- A consumption-based model has many benefits, including:
- No upfront costs.
- No need to purchase and manage costly infrastructure that they may or may not use to its fullest.
- The ability to pay for additional resources when they are needed.
- The ability to stop paying for resources that are no longer needed.
Kinds of services you'll find on Azure:
- Compute services such as VMs and containers that can run your applications
- Database services that provide both relational and NoSQL choices
- Identity services that help you authenticate and protect your users
- Networking services that connect your datacenter to the cloud, provide high availability or host your DNS domain Storage solutions that can accommodate massive amounts of both structured and unstructured data
- AI and machine-learning services can analyze data, text, images, comprehend speech, and make predictions using data — changing the world of agriculture, healthcare, and much more. And many more!

Two Sum - Leet Code

Thels Katikireddi — Sat, 31 Oct 2020 17:28:00 +0000

I worked on the TwoSum leet code problem this week.
https://leetcode.com/problems/two-sum/

After reading and viewing multiple problems solving approaches. I have listed the steps I am using to solve the problems. Want to use the post as a future reference.

Do not immediately start coding once you see the problem.

Step A (Analyze): Analyze and note the important points

two number add up to the target
exactly one solution
do not use same element twice
return indices answer in any order.
[Note: we need to retrun indices sometimes in rush to get to solution we might miss this and return numbers]
In real interview ask and clarify any questions
Datatype of num. i.e Is num an integer ?

Num range ?
Case where there is no match ?

Step T (Test Cases):

If no test data write test cases and confirm Think of possitive, edge and negative test cases
T1: [2,7,11,15] target = 9 => [0,1] Since we can have negative numbers add test case on negative numbers
T2: [2,7,-11,15] target = 4 => [2,3] Reason to pick target 4: If you are using element twice you get wrong answer [0,0] and also it covers the negative numbers case
T3: [2,7,11,-15] target -4 => [2,3]

Step B (Brute Force):

Think of BruteForce and calculate its time complexity
Take two for loops to get each pair in the array of size N and check if it adds up to target.
Time complexity is O(N^2)

Step O (Optimize):

BUD technique from Cracking the Coding Interview book.
Look for BUD: (Bottlenecks, Unnecessary Work, Duplicated work)
Goal is to get to linear time O(N) or close to linear time.
- Bottleneck is iterating the array twice.

Step S (Solution):

Mantain a map to store the expected Num (Target - elementValue ) as key and element index as value.
At each index first check if the elemenet is in expectedNum map.
- If yes return the current index and the expectNum index in an array
- If no return store the expected Num (Target - elementValue ) and current index in the map.
- Time Complexity is O(N)

Step C (Code):

class Solution {
public:
    vector<int> twoSum(vector<int>& nums, int target) {

       /* Algorithm
        1. expectedMap = {}
        2. for i in range(len(nums)):
              if nums[i] in expectedMap:
                 return [i,expectedMap[nums[i]]
              else:
                 num2 = target - nums[i]
                 expectedMap[num2] = i         
        */

        //Map to store the expected Num with which we can make target
        map<int, int> expectedMap;
        vector<int> result;

        for (auto i = 0; i < nums.size(); i++) {

            //check if the num is in expected map 
            auto it = expectedMap.find(nums[i]);          

            if (it != expectedMap.end()) {
                result.push_back(i);
                result.push_back(it->second);
                return result;
            }
            else {
                //Find the num to make the target and store it in map
                auto num2 = target - nums[i];               
                expectedMap.insert(make_pair(num2, i));
            }
        }

        return result;

    }
};

Step V (Verify with test data):

Iterate your code with test data before submitting it.

SUBMIT the code.

Lessons from mistakes:

Check if we are storing the correct num in the map
Iterate the code with the test data and check what variable hold at each steps

Tips:

When you are stuck start with a smaller problem size.
Check if sorting the array can improve the performance.
Does using additional data structure like map improve the performance.
Two pointers

Please share your inputs which can help me to improve.

AZ-900 Cloud Concepts -Azure Fundamentals-1

Thels Katikireddi — Sat, 31 Oct 2020 13:53:04 +0000

Highlights from https://docs.microsoft.com/en-us/learn/modules/get-started-with-azure-fundamentals/

Quick refresh before taking exam.

Get Started with Azure Fundamentals

Azure services range from computers running in the cloud for you to run your software, to storage, to many other capabilities like Artificial Intelligence and IoT.
Cloud computing is the delivery of computing services—including servers, storage, databases, networking, software, analytics, and intelligence—over the Internet (“the cloud”) to offer faster innovation, flexible resources, and economies of scale.
Azure Benefits:
- Be future ready - Continuous innovation from Microsoft supports your development today, and your product visions for tomorrow.
- Build on your terms - You have choices. With a commitment to open source, and support for all languages and frameworks, build how you want, and deploy where you want to.
- Operate hybrid seamlessly - On-premises, in the cloud, and at the edge—we’ll meet you where you are. Integrate and manage your environments with tools and services designed for hybrid cloud.
- Trust your cloud - Get security from the ground up, backed by a team of experts, and proactive compliance trusted by enterprises, governments, and startups.
AZ-900 Study Areas

Understand cloud concepts - 15-20%

Understand core Azure services - 30-35%

Understand security, privacy, compliance, and trust - 25-30%

Understand Azure pricing, service level agreements, and lifecycle - 20-25%
Options to purchase Azure:
- Azure.com : Buying directly through Azure.com is the fastest and easiest way for organizations of all sizes to get started with Azure.
- Microsoft representative: Buying Azure through a Microsoft representative is intended for large organizations or customers who already work with one. You'll also manage your Azure deployments and usage, and you will also get a monthly bill from Microsoft for the services used.
- Microsoft partner: If you buy Azure as a managed service through your partner, your partner will provide you with access to Azure, manage your billing, and provide support.

Week Plan 10/25/2020

Thels Katikireddi — Sun, 25 Oct 2020 23:11:55 +0000

This is my first blog and I am planning to learn and blog on the below items this week.

Easy Algorithm Problems
- https://leetcode.com/problems/two-sum/
  - [Status Done: https://dev.to/thelsk7/two-sum-leet-code-n21]
- https://leetcode.com/problems/is-subsequence/
  - [Status InProgress: Moved to Next Week]
- https://leetcode.com/problems/fibonacci-number/
  - [Status InProgress: Moved to Next Week]
Azure Fundamentals (AZ-900)
- https://docs.microsoft.com/en-us/learn/paths/explore-microsoft-azure-cloud-concepts/
- [Status: InProgress 75 % complete] Moved to Next Week https://dev.to/thelsk7/az-900-cloud-concepts-azure-fundamentals-1-27hj https://dev.to/thelsk7/az-900-cloud-concepts-azure-fundamentals-1-27hj