Programming Gyan

5 Steps to improve Programming Skills

2020-08-03T20:55:00.000+05:30

5 Steps to improve Programming Skills

I have certain steps you can follow to improve your programming skills now. The first thing you need is a programming knowledge and of course right you must have started with any of the language maybe C C++ Java Python or JavaScript and you might be knowing the syntax of it because that's what we do so when you say you are learning a programming language the first thing you learn is a syntax now different languages have different syntax and that's why you know once you learn one language let's just see it is easier for you to learn C++ and then Java because they all follow this same syntactical paradigm another thing is once you have learned this syntax the next thing you have to follow these five steps so that you can work on your skills

FIRST STEP

-> Practice algorithms and data structures now when you learn a language you feel you know everything but that's not the case because when you learn the language you learn syntax

-> If you do if you want to implement it let's say if I give you a problem statement and you have to convert that problem statement into a code and your software it's not the act process first you have to convert that problem statement into a solution and that will be only steps

-> That's what we call it as algorithms and then we convert that algorithm into code now when I give you an example let's say if you want to if you want to find a given number is all or even I know in your brain somewhere doesn't acquire them

-> What you do is you convert that into a code right but if we talk about big problem statements so first you have to convert that into algorithms and you need practice for that and so for practicing that you have to solve some existing algorithms

-> You know if you open any algorithm book you have this searching and sorting techniques so you have to look for those things first so practice those algorithms and also data structures like we have linked list we have leased right

-> So practice all those things like we have trees so practice all those things together because so there are some algorithms which works with this this data structures so that will be a first step

SECOND STEP

-> When you learn a language and when you implement that in your own way so if I give a problem statement you will write your own code but sometimes the code which you write is not the correct way

-> Not saying it will not give you the right output but sometime what also important is the way you write a code the the compactness of your code the efficiency the speed efficiency

-> Is also a way of any code you heard about design patterns right now to improve those things what I would recommend is just see some other people's code and nowadays we have this huge repository called as github

-> In fact not just github we have different de filmed websites available as well but github is my favorite so what you can do is try to read other people's code because it might give you a new way of writing code

-> The same thing which you are writing but a different way like the syntax will remain same the the output will remain same but the way right up code will change

-> So what you will do is just go to github and as there are some places available just have a look on those things and the way them the moment you watch those could have you when you see those codes it will make an impact on your brain and next time you have code it will be helpful

THIRD STEP

-> The way I have improved my programming skills is by participating in the competition so when I was in my college I used to participate in multiple colleges or multiple college events

-> So may be coding event or debugging event or maybe aqueous events so initially I used to lose all those games but then later on I started winning

-> I was practicing it so initially of course you will lose because you don't know how to compete and later on the mall the more you compete the more

-> How exactly the cool now nowadays if you don't want to visit any qualities you can do it online so we have this thing called as company do programming's so if you can compete with people you know on different websites like hacker ranked hike on earth

-> We have code chef so just compete with people because they will so what happens is this website they will give you a problem statement and you have to convert that wrong statement in to a solution so of course have to write of cool

-> When normally when you submit your code maybe they will not accept it they will reject your code and that's where the lightning starts because initially you will get rejected

-> I got rejected multiple times and later on luckily one of my quad code selected that's without that what motivates you right so you have to participate in competitions

-> Because it will teach you how to code second it will teach you how to code efficiently and third it will teach you how to debug and that's very important in fact in the description area

-> You will find a link to an article and it will be helpful for you so just with the article it will help you to participate in computer programming

FOURTH STEP

-> It might sound weird but don't stick to one language explore try to explore more languages the thing is will we all we all love some languages

-> For example I love Java there are people who love Python then we'll have some people love PHP don't stick to one language because your language might be best but all the languages

-> They have some good things and some bad things or some shortcomings so when you learn another another language it will teach you a different way of idea code

-> For example when I learn Scala I learned about how do we you how do we do functional programming which helped me in my java language right so learn other languages because they have some extra features which you can implement in your language

FIFTH STEP

-> Why you learn a programming language at the end you want to build project so why not start building a project from start I'm not saying from day one but after learning a programming language

-> We have syntax and then implementing all these steps it's time to take time for you to build a project now it can be any project doesn't matter

-> Because we all have some passion right something else like some hobby may be you like to watch movie may be you like to read a book maybe I like playing games or maybe your photographer

-> What you can do is you can build a project for yourself so the first project should be for yourself example if you love music make a music player if you if you like games make your own game

-> Then that will be your first step because when you are doing for something for yourself you will feel good about it right and of course you will get stuck somewhere

-> Because this is your first project and there's multiple way you can solve this just go to Google and serve and but such for your problem and trust me Google knows everything right

-> We also have set for this type of flaw it will help you with the code ok don't just copy paste the code because that's what most people do try to understand the code

-> What they are saying try it out and try to customize it the way you want now don't just copy-paste it because it might lead to bugs and trust me bugs are harmful

Now after these five steps let me just repeat those steps :-

-> First one is practice algorithms and data structures
-> Second one is read other people's code
-> Third one is community programming
-> Fourth one is explore other languages
-> Fifth one is build a project now

With this I have a bonus step for you which is quite important because at least for me and that is keep following telescope it will surely help you to improve your programming skills.

What is MVC (Model View Controller)

2020-08-03T20:46:00.000+05:30

What is MVC (Model View Controller)

-> This is not a new concept first of all and it is a thing that you see in your daily life as well I'll prove that in example just in a moment and also this is not specific to one programming language

-> It is a way of how you organize your code it is not like a specific thing for Ruby or PHP or for Java or for Swift it's just a way of how you organize your code and trust me you also see this kind of pattern every single day in your life

-> I can do a little bit better job in explaining what model-view-controller so yes you have seen model-view-controller probably a hundreds of time in your day-to-day life now

-> Let me try to explain what the model-view-controller is and where you see in your daily life so let's just see that this is you now you go to a restaurant and let's just assume this white entire animation kind of thing is a restaurant

-> You move on to a restaurant now what you do at a restaurant you don't just go to the kitchen and make a food by yourself you can do that at your home so what you wait you just go there and you wait for a waiter to come on now waiter comes to you

-> You just order the food to the waiter now waiter is not aware who you are or what you want to have it just gets that from you now whenever you sell the waiter that yes I want this the waiter just gets the order

-> Now waiter moves to the kitchen now in the kitchen waiter is not going to prepare your food, the food is prepared by the cook so let's bring up the cook now waiter will tell that the cook hey this is a guy out there

-> He wants this kind of food and now cook is the guy we're going to prepare the food for you but cook did not prepare the food magically he needs some ingredients to cook the food he'll open up the fridge

-> We'll put out something legitly you order an omelet so he'll get the egg sugar and whatever it needs so let's bring our fridge as well so now the fridge is there and cook will cook the food now cook

-> Will finally hand over the food to the waiter and probably the cook might hand over a couple of other foods as well like maybe a glass of soda or maybe my favorite icy or omelette that you have ordered now it's the job of the waiter to move those food outside the kitchen now waiter is actually aware

-> What kind of foods need to be served to you and how it should be served so waiters comes back to you and order and your order is now served so you might be wondering hey what this tool is all about and probably you might have anything guess that

-> This is all of your model-view-controller so this you guys is actually have you this waiter guy is actually the controller and yes you get that right this hood guy is model in itself and if you haven't guessed that yes the fridge guy is actually the data

-> So how about that this is a cool example and this is kind of a thing you see every day you have been going to restaurant every day and they are following a model-view-controller objectives throughout the year

-> So this is basically your model-view-controller now I can understand you have gone through with that restaurant example pretty easily and nicely now you want to understand how this is applied in the code

-> Now first of all a lot of people believe that model-view-controller is a thing for only dotnet or may be only for Ruby or may be hungry for PHP but it's not it's the design pattern it's the way how you arrange your code

-> It's going to be possible in everywhere you might want to write an application and PHP Swift java.net Ruby Python you can just arrange your code like that now the whole advantage of this approach is you can write dumb code

-> The more the code is going to be dumb it's going to be more beneficial what I mean by that now all I'm trying to say is we are trying to reduce the dependency of each code in this file from each other

-> We want that if some data is being passed on this file it just process this data it shouldn't be worried about from where this data is coming up ROM or there shouldn't be any dependencies

-> Wherever I does that I always recommend to use the model-view-controller approach but let me give you also an example that this kind of approach although is good in most places but in some places it can be opposite of that

-> Like for example if there is a store which just sells the popsicles or ice creams it would be really bad approach if we use model-view-controller there because there is just one job to do just bring up the ice cream from the fridge and serve it that's it if you use it if you will use the model-view-controller approach there

-> It would be overused and overkill of the resources so at some point of that time model-view-controller is not a good approach but in most of the cases where application is pretty humongous pretty big then it's a good idea to use the model-view-controller approach

-> Now although we are not going into the in depth of what this model what is view what is controller because if I will be taking an example specifically for Android it would be really not a good thing for iOS if I will be taking an example directly from iOS it would not be a good approach for Android

-> So all I'm doing here is trying to generalize the thing as much as possible now one thing I would like to mention that a lot of people misunderstood the thing that your model is not the data again

-> I repeat your model is not the data the data is completely separate it needs to be cooked up so that is what the cook is doing in our example

-> In the real life example your data would be something fetching up from an API request or maybe from the firebase or wherever you guys fetching your data and your models should be the guy who should cook up these data should process the data

-> Finally controller should be responsible from taking the data filtering the request and let us say you have asked for a result of maybe top 10 wonders of the world

-> There can be hundreds of such wonders of the world now you are looking only for the ancient wonder of the world so it's the job of controller to filter out the data and just produce that on to the view.

Zoom Interview Tips Strategies Online Interviews And Calls

2020-08-03T20:31:00.000+05:30

Zoom Interview Tips Strategies Online Interviews And Calls

-> I gonna do the problem is not with the online interview the problem is with the way your interviewing and the way that technology is actually getting in your way instead of helping facilitate

-> The success of your online interview so in this blog I'm going to give you two strategies that's going to help you leverage technology and use it to your advantage in an online interview

-> Just making these two simple things is going to change the way you interview online

-> This is valid across multiple platforms Adobe Connect Skype zoom WebEx all those things so as
we know online interviews are becoming more more popular they're a dime a dozen chances are you've probably already had an online interview so many of you may be saying right now yeah well I just interview so much better in person well let me be real with you many employers are going to reach out with a video call to get to know you it's so much more convenient

-> They don't want to waste their time they don't want to waste your time so instead of calling you in to come into the office having you sit down

-> Do an interview why not just hop on a video call at least in the very beginning you'll probably be getting an online interview

-> So I'm going to teach you two ways to feel more comfortable and confident in an online interview so that you can be presenting the way you want to present and answering the questions

-> The way you want to be answering them and by the end of it you're really gonna feel like you can connect with the hiring manager the person who is interviewing you

-> You're probably gonna even want to have online interviews because it's so convenient and you're gonna see why you're gonna want it

-> Make eye contact or maybe it's more appropriate if we say camera contact and you'll see what so as you know an interpersonal communication it is imperative that we make eye contact same with public speaking

-> We need to be able to look the audience members in the eye share our thoughts with them because it's a way of connecting with the audience so why wouldn't the same be true in an online interview scenario

-> It is how do you make eye contact with the other person on the other side of the screen without them actually being in front of you by looking into the camera so you're looking into the camera as you respond because that translates into making eye contact with the person

-> The person on the other end of the screen will notice that you're actually looking them in the eye it doesn't even feel like an online call it really does feel like an in-person situation

-> Just as simple as looking into the camera now you want to avoid staring at the camera the whole time obviously that would make the person uncomfortable so instead you can you know add a little bit of eye movement but you don't want to do too much of it because that can be distracting

-> You certainly want to avoid looking up or down if that's just too obvious my recommendation would be to look at the screen at that point and they're not going to think anything strange of it

-> Because when you look down you avert your gaze from the camera you're actually looking at the image of them on the screen so that's not going to seem strange to them

-> You should be looking is at the camera to make eye contact and then looking down into the screen to halt look at the image of you right

-> If you want to check your hair or makeup or shirt and whatever do that before you get on the call right so if you're not able to avert your gaze from your own image on the screen

-> I would put a post-it so that you're not tempted to look because we want to minimize distractions on the screen so that the only place you can actually have access to is the camera so that you make eye contact

-> Why does this work it shows you have a secure handle on the interview and it also makes the person feel good because it shows that you're paying attention and that you're listening to what they have to say and everybody likes to feel listened to right it's really important to look in the camera

-> When you do you're tell me about yourself when you do tell me about your weaknesses when you're talking about how you would add value to the company

-> What your role would look like sharing an anecdote these are the parts of the interview where we really want to make sure that we're connecting with the hiring manager

-> Now when they ask you a question or when you need some thinking time it is okay to look down direct your gaze moreso to the screen in other words so to some of strategy one you're making a point of looking into the camera

-> So that you can essentially be making eye contact with the hiring manager it shows confidence it shows that you're poised and it shows that you have everything under control

-> Because you do even when it doesn't feel like it you can really project that impression onto them by doing something as simple as maintaining eye contact and maintaining eye contact will really give them the impression

-> She is really confident he is really confident so we all know that interviews can be over stressful and for some people

-> It's even more stressful when they feel like they can't connect with the personwho's interviewing them because it's not done in person right in an online interview situation but I'm telling you that you don't have to worry so we looked at the first strategy of making eye contact

-> Now we are looking at the second strategy which is having a safety net so you may be thinking okay so what's my safety net how in the world am

-> I going to feel even more secure about this whole thing well you're gonna have a minimized outline now it's really important and I really stress this and underline it and highlight you really have to make sure that you're not over stuffing your outline an outline is probably a generous term for it

-> What you really want is to have a few talking points you don't know what you're gonna get ahead of time in terms of the questions but you have some sense as to what you'll be speaking about so those are your talking points

-> That is what you want in your outline outline okay so make sure that it's not more than five words because then you're gonna fall into the trap of reading off the screen and that is super obvious right reading eyes

-> You see it sometimes in newscasters when they're reading the teleprompter you want to avoid that because it is really obvious

Top 10 Interview Tips To Crack Your Interview

2020-08-02T17:34:00.000+05:30

Top 10 Interview Tips To Crack Your Interview

We're going over ten tips to crack an interview please note I am NOT going to justify be on time with a tip if you're that much of a moron to be late you don't deserve the job

FIRST STEP
-> Conduct research prior to going to the interview I'm not talking about knowing what the company does you probably did that prior to actually applying I'm talking getting granular get more into it dive into Google dive into their website figure out this company so that when you go in you're ready to talk shop and if you know who you're actually going to be interviewing with in terms of like the person's name do research on them

SECOND STEP
-> You're not always going to know but a lot of times they're going to tell you you're going to be meeting with X he is or she is whatever all right do research on them LinkedIn is a beautiful thing and it's an amazing resource to get pretty a lot of info on a lot of people have the information in the back of your head all right and if you can use any of it in the general flow of conversation do it but don't go in there man like so your husband Rick looks fantastic after the nose job and Jack and Jamie are two boys my god you will look like a super stalker and this is counter productive to actually getting a job

THIRD STEP
-> Review the one hundred and fifty most common interview questions that get asked pretty much in every interview think about your answer alright you don't need to memorize the questions but it's a good idea to have an idea of what they're gonna ask and how you're going to respond because if they shock you with why are you looking for a new job and you are dumbfounded like that whole sexual harassment thing kind of killed Nana who I feel the butterflies they're coming because you're getting close the day has arrived it's time to go to the interview

FOURTH STEP
-> All about making friends when you walk into the establishment I need you to be super charming to everybody the receptionist anybody who's walking through that office even other people if they're there actually for the same job you are you're talking you're engaging you're asking questions you're smiling you're being friendly because you never know who you're talking to and you never know if the receptionist has the ear of the person that's actually hiring you right you're in the room and the interview is under way you need to make sure that you remember

FIFTH STEP
-> Keep your answers short but concise not like one word of two words but elaborate as much as you need to to get your point across don't ramble because rambling will lead you down areas that you don't need to go keep it concise keep it consistent

SIXTH STEP
-> Utilizing body language in order to make a great impression this involves eye contact the way you sit your posture the way you stand the way you walk into a room gentlemen I have done a ton of videos talking about all of those things they're also listed in length in the description

SEVENTH STEP
-> About preparation I would recommend bringing some type of nice portfolio to keep your resume business cards and a notebook and in this notebook or on the sheet of paper you're going to have already written out some predetermined questions that you're going to be prepared to ask the interviewer which is actually

EIGHTH STEP
-> Have a list of questions that you're going to ask in most interviews the interviewer is going to ask you at some point hey what questions you have for me and if you're like none all right it means that you really haven't thought about things alright by having a list of questions that you're prepared to ask shows that you're detail-oriented and you're interested in that job

NINTH STEP
-> Selling yourself this is your opportunity to shine this is not an opportunity to be super modest but you have to delicate in the sense that you don't want to look like you're bragging yeah it was the best of that oh yeah nobody can touch me but you can be confident and deliver yourself in a positive proactive way and not look like an arrogant ass all right but it is not the time to be like well I'm not that great now Oh Jack take the Alpha M approach to self marketing promote promote promote at least that's what I do and

TENTH STEP
-> Before you walk out of that office you let them know that you are the man for the job and that you're interested in the job that you want the job let them know that you're excited and hope to be a part of what they have going on or that specific organization before you leave you get up you put your hand out and you shake that hand like a man even if you're shaking a woman I don't be all like oh right you don't need to kiss it you need to shake it.

Introduction To Test Driven Development (TDD)

2020-08-01T17:09:00.000+05:30

WHAT IS TDD :-

1. Test driven development (TDD) is developed which specifies and validates what the code will do

2. Test cases are created before code is written

3. The purpose of TDD is to make the code clearer, simple and bug free

4. TDD starts with designing and developing tests cases for every small functionality of an application

5. TDD instructs developers to write new code only if the test case of particular feature getting failed

6. There is a cycle which TDD follows :-

-> Write a test

-> Make it run

-> Change the code to make it right OR we can say to refactor the code

-> Repeat this process

7. Test-Driven Development as three steps :-

-> Red
-> Green
-> Refactor

8. So you don't have a piece of code, so first thing you would write is the first test condition for that particular thing

9. Let's I have a method which I have to write and I would probably identify the conditions which have to write and probably identify one of the conditions and write the test for it

10. So that's Red so because if you run that test the code would fail the test

11. Green is when you write the piece of code that is needed to make the test pass

12. So I had a failing test and now I write the code to make the test pass that's green so that's the step green

13. The last step is actually refactored where I need to make the code adhere to four principles of simple design if you don't know what four principles of simple design. So the third step is actually making the code better

14. One of the things about making the code better is to make it a date before principle of simple design at least and most important thing also is to keep it green that's basically it should just should always be passing while you refactor the code

15. Most important is refactor stage you can refactor both the test and the code so even the test is a piece of code which you are going to maintain over a period of time and it should be clear enough so you would go ahead and refactor the test as well and the code as well

16. So that's basically what tests reown development is all about there are three more logical to stay in development that's basically to say like how much code that you can write to make a test fail

LAWS OF TDD

So that's a four laws of test-driven development :-

-> The first law is no production code without failing this so if you don't see a red bar then you are not going to code so that's basically what it means if you write new piece of code only when you see the red bar so only when there is a failing test you write new code and when you add a new test it should be a small test you should not write probably five six conditions of this at the same time what the way it should be is you add a small piece of test probably one small condition

-> The next step you write just enough code to tear at make the test pass so as soon as you write the test you'd write the code which is needed to make that test passes you write a small test

-> Write the small piece of code to make it pass and you follow this in a cycle

-> So these are the three laws of TDD actually like I can act in a fourth law it says all these three steps like the three steps of TDD which is red green refactor usually you should be able to run within two minutes

CONCLUSION

1. In two minutes I should be able to do the three things that basically add a failing test right go to make it pass and then refactor

2. So regarding TDD there are few important things that you need to keep in mind. Make the right choice actually test-driven development is proven to be a success and it leads to maintainable code understandable code and it's known to improve your productivity the productivity improvement is more like after you get a little experience with testing and development.

Introduction To SSIS

2020-07-27T11:52:00.002+05:30

Introduction To SSIS

What is data integration and why do we need it.

-> Data integration is the teeth using various tools. Let's take example you have to understand the need of data integration

-> Suppose I am in a company where I have different departments now if the department has some data right so based on the company requirements to choose the database so for example my accounting team chooses SAT to store all the analytical data or you can say my sales team uses Salesforce CRM after manage all the customer details similarly different team uses different database my marking team is using Oracle manufacturing is using db2 and many more so all this depends on the requirements of the company

-> Now I have different databases where my different type of data is stored but let's say the manager asked me to analyze all the departments and tell me who brings the best revenue out of all the teams so what we do now any idea guys if you could suggest me with something or you could help me with this current problem okay

-> We can connect the databases this is absolutely right but let me tell you to connect the databases it's not free you need a connection object or adapter for it what about dealing with these connected databases will create more complexities for you because if you have large data say you have hundred databases and to connect all of them it will consume a lot of time okay but now what would the solution there here a simple solution would be data integration

-> Data integration what I mean is you can integrate all your data present in different databases and combine them at the same platform

-> Data integration is a process you follow to get data from multiple sources your data can be in any form it can be heterogeneous and homogeneous now by this term I mean data can be in structured form it can be semi structured form I can be unstructured so these are dissimilar data but if these dissimilar data are combined together into meaningful and valuable information wouldn't that be great so this exactly is data integration

-> Data integration was going recently but before that also people uses the data integration the people then realize the potential of data integration so they use different methods to achieve it so here I suggest some few ways from which you can achieve data integration such as data modelling where you first create a model and then perform operations on it then there is data profiling bit you take a sample data and check if there is some inconsistencies errors or some variations to it similarly

-> Advantages of data integration are it reduces complexity it means deliver data to any system so data integration is all about managing complexity streamlining these connections and making it easy to deliver data to any system, second advantage is data integrity now integrity has a major role in data integration so data indicative basically business with cleansing and validating your data so all of us need our data to be high quality and robust right

What is SSIS. How SSIS works

-> SSIS stands for sequence of integration services which is the service from Microsoft

-> SSIS is the service of Microsoft that basically performs data integration or you can say merging of data from different data sources which can be from flat file it can be from exit it can be for SCP all right pull or anything

-> So it is basically used to perform a broad range of data integration as well as data a transformation task so in a whole you can say it basically perform data migration so exercise is a platform for data integration and workflow applications by data integration

-> We already know the data is retrieved and combined in a structure which has a unified view next we have workflow now a workflow can do several things sometimes you just need some steps or path in the path that institution which is either based on time period or maybe a parameter that is passed or queried from the database now after identifying it you can choose any path you want to take this is

-> We've already discussed that exercise is a platform for data integration and growth to applications so these two things are carried out using an exercise package we'll be talking about exercise package in for the most light to air

-> Three major components the first is operational data followed by an ATM process and then the data warehouse so let's understand each one of them in detail now so the first component is operational data now what exactly it is so an operational data or you can say an ODS which stands for operational data store which is a database that is used to integrate data from multiple sources also one key point of operational data is analyzer master date of tow where the data is not pass back to operational systems it may be passed for for the operations and the data warehouse for reporting but it is not passed back to the operational system

-> ETL is a process responsible for putting data out of the source which can be of any format it can give excellent flat file and placing the hole into a data warehouse also an ETL process ensures that the data stored in the warehouse is relevant it is useful to the business users it is accurate and it is high quality also it is easy to access so that the warehouse is used efficiently and effectively by the business users so it will help the organization to make meaningful data-driven decisions by interpreting and transforming large amount of structured and unstructured data even though

-> ETL is a three word concept but it is actually divided into four phases so the

(a). First phase is capture it is also known as an extract phase so in this case it basically takes the source data or metadata which can be present in any format

(b). The next process is scrub subscribe basically identify errors in your original data for checking these errors and inconsistencies it uses some artificial intelligence techniques to verify the quality of the data should verify its quality of the data and basically ensure that the quality of the data is met or not thirds

(c). The transformation is another process where your source data is converted to the required format you want the transformation is modeling or changing your data to meet the requirements it can be with respect number of rows and column processing if you want to increase the number of rows or columns you get transform it accordingly

(d). Final stage is load and index so in this date it knows the data and validates number of flows that is processed meets the required number of rows once your loading is done indexing helps you track the number of rows or the amount of data you are loading into the warehouse so it basically checks the data through indexing and identify the data is inside format

What is data warehouse. What the data warehouse is

-> Data warehouse is a single complete and consistent tour of data which is formulated by combining the data from various sources and then they combine the data from different sources they are not simply saying just go and take data from different sources and combine them together it has to be a purpose for it so we as an analyst or consultant

-> What a big system is all this will become secondary and it will naturally come to you so

-> Data warehouse is a technique where you pull the data or assemble the data from various sources and combine them

-> Data warehouse is a structure of their analytics various queries can be fired and you can get faster query responses if you compare it to the database

What Is Dependency Injection

2020-07-27T11:52:00.001+05:30

What is dependency injection and why everyone want to use

-> Dependency in software programming software what we do is we build good right we build objects if you are working with object-oriented programming so we build objects right and those objects are dependent some on some other objects

-> So we create this object graph right so a one object is depend upon some other object and that object depends on what that object

-> To give you an example in real life let's say if you want to buy a laptop if you want to build a laptop let's say you are a laptop manufacturer now in this case in laptop you have certain parts right we have a ram you have a hard drive you have a screen and of course what makes a good laptop is good parts right example if you buy a laptop from any company the same company they have a low range laptop and a high range laptop what changes is the type of hard drive we use the type of RAM we use

-> So of course all these components are not built by the same company so let's say if you buy a Apple machine of course Apple will not be building all the step by themselves they will be buying it from some other companies may be the screen of MacBook is from Samsung may be the hard drive is from Itachi may be the RAM is from Sanders so all these different company they help one company to build a project or build a machine

-> Now the same way if you want to build a project and if you want to let's say if you have an object and that option is depending on some other object in this case you will not be building all this stuff by yourself of course you will be having classes for that right so in Java what we do is we first grade class and then we create object now to get an example let's say we have a class here which is class let's a laptop and in the inside class laptop we need a object of hard drive we need her object of RAM now how will it do it of course you will be saying new right and when you say hard drive of course you need a point class right

-> Let's say we have hitachi hard drive now let's say if you build a MacBook with Hitachi hard drive what if in future you want to change it because we want to achieve this concept of loose coupling right

-> I am sure you know about this concept of tight coupling and loose coupling that's what we have learned in software engineering when you say loose coupling it means one optic is not totally depend up on other object it may get replaced example if you have with a hard drive in future you might want to use Samsung hard drive it should pass it should be possible right and that's why we use this concept of abstraction what we do is we say ok for each class let's say Hitachi hard drive let's create abstract class or the interface for less hard drive so when you instantiate it it will be something like hard drive ABC or hard drive obj equal to new Hitachi hard drive so that in future

-> You can change it from Hitachi hard drive to Samsung hard drive it should be that easy but there's a question here we are hard coding it right we are saying hey we I'm going for a new with a hard drive and that's a bad thing because the moment you say hard coding the moment you say new you are going for tight coupling that's that's what we don't want

-> So we want someone else to give me those dependency or that's important down here so the laptop object is dependent on the hard drive object that's a dependency so we want to inject the hard drive object inside inside this laptop class and the way you can do that is by using some service which will be external service they will inject the dependency okay

-> How it is possible so we have this concept of dependency injection containers now they are responsible to create a object for you of course the object has to be created so they are responsible to create the object for you and then they will be injecting in your class okay but we're to mention that I want to inject and how it will create the object and that's where we have to figuration now there are different ways of configuring it example if you are using Java

-> In Java we have Spring Framework and in Spring Framework we need to do so a lot of configuration but earlier days we used to work with Spring Framework ways to configure everything using XML okay so that's how you can configure

-> So create XML file and in the next sample file you can mention hey if someone is asking for hard drive give this object okay now when you say XML it means you can edit XML in future right so that is not a tight coupled okay but still as a jar of Rama you don't want to focus more on XML and that's where in we have spring boot in Java using which what you can do is just we will be having some class as hatachi hard drive right or Samsung hard drive so on top of these classes you will simply write add component

-> So you simply like add component which makes them dependent which makes them a component of a spring framework which will be generated as per requirement okay those object are ready with Spring Framework but what about this class how will this mention that you want this object so on top of your hard drive what you can say is you can say Auto wired

-> Let's say your Spring Framework says or your spring boot with the help of Spring Framework says ok here someone is asking for hard drive ok so this class needs a hard drive and I do have a component there so I can connect them like that subtype so Auto wired and just imagine so beautiful they are getting connected again the implementation you will say later but this is this is the main idea behind dependency injection right but why we need this is it only because of tight coupling

-> The answer is yes we don't want to achieve tight coupling we want loose coupling plus there is one more important factor which is testing you need to test your software right now we always test our software as a whole but sometime we need to not sometimes always we should all we should also be testing your each component each unit now the thing is

-> Let's say if you want to test a laptop and laughed when you said when you test a laptop you should also test the hard drive but don't you think when you buy a hard drive like when Apple bought hard drive from Samsung they must have tested that hard drive right why you need to test the hard drive again and again

-> So what you want is when you are testing a laptop you want to separate the hard drive right so in in fact in Jogja world what you can think is you have a plus and that class is working with a database object now you are testing this class right you don't want to test the database object so you can create a mock object of this of this class only

-> If they are loosely coupled so if you have a mock object you can easily test this class without affecting your database okay and to achieve that feature you have to make sure that your software is loosely coupled and that's why we have so many words right

-> We have loosely coupled we have dependency injection so that's so amazing about a pencil injection you just need to implement it so that you can test it better you can maintain it better and how it exactly works.

Introduction To SCRUM Framework

2020-07-25T14:19:00.001+05:30

WHAT IS SCRUM

1. Scrum as a lightweight framework that utilizes principles and practices that assist teams in delivering working software in short cycles to the customer enabling rapid feedback continuous improvement and quick response to change

2. It promotes delivering value as in working software to the customer in an incremental and iterative way

3. It is not a process or technique for developing software rather it is a framework within which various processes techniques and practices are employed in scrum

4. The iterations that deliver working software to the customer are called sprints. In each iteration or sprint results in potentially shippable software.

SCRUM FRAMEWORK

Product Owner And Product Backlog :-

1. The product owner owns the product backlog and in collaboration with the team develops the user stories or requirements for the project

2. The product backlog is prioritized with the higher priority items occupying the top of the product backlog in collaboration with the product owner the team decides how to group the user stories into releases based on the product roadmap once the release planning has been completed

5. The user stories are then selected for a sprint the duration of the sprint is going to be two to four weeks once the sprint backlog has been determined the team then disaggregates each user story into tasks

What is Sprint Planning :-

1. During each sprint the user stories are developed as the code is written it is integrated into the system and daily scrums are held at the end of a sprint there is a sprint review where the working software is demonstrated and presented to the customer for acceptance the team then conducts a spring retrospective.

2. During the retrospective the team looks at primarily three things

-> What went well
-> What did not go well
-> What should be done differently

3. Going forward the team's velocity is then updated as are the information radiators which transparently display the status and progress of the project and then the cycle repeats itself until the project is complete.

4. A sprint is an iteration in scrum at the beginning of a project the scrum team determines the duration of Sprint's for the project most Sprint's are going to be two to four weeks in duration factors affecting sprint duration include the stability of the product backlog

5. Once a sprint has begun the duration is never changed nor are any user stories added or removed therefore if many changes are expected a shorter sprint duration would be best however if the product backlog is relatively stable a longer sprint duration may be appropriate overhead there are overhead costs associated with each sprint for example every spent is going to have a sprint planning meeting a sprint review and a sprint retrospective if a team has been able to lower these overhead costs by automated testing continuous integration etc

6. These costs can be absorbed team making shorter Sprint's more desirable however if these overhead costs remain high the team may need to use longer duration sprints a team may be tempted to extend the duration of Sprint's in an effort to hide their inefficiencies remember agile projects favor shorter duration Sprint's and it is the scrum masters responsibility to coach and mentor the team so it can reduce waste irregularities and overuse and make the Sprint shorter the goal of a sprint is to deliver working software

7. Conclusion of each sprint the team should be able to deliver near releasable or potentially shippable software this is not easy especially for an existing product with a lot of legacy features but it can be done with the right technical practices and mature development processes once the sprint duration has been determined and the user stories for the sprint have been selected the duration of the sprint cannot be altered nor can any user stories be added or removed

8. The Sprint will end at the appointed time irrespective of whether the team has met the sprint goals or not this allows for effective continuous improvement if the team is unable to deliver the working software as planned the team will have to figure out why that happened and then make changes to improve going forward the product owner may choose to cancel or terminate a sprint in specific situations for example a significant change in priorities or a mid-course correction may render the current sprint backlog invalid given that we are only talking about a couple of weeks of work the cancellation of a sprint would be an extremely rare event a sprint will begin with a sprint planning meeting and end with a sprint review and retrospective

SCRUM Backlogs :-

There are three backlogs used in scrum :-

1. Product Backlog :- The product backlog is the master container of all the user stories for the project the product backlog is continually pruned or prioritized so that maximum value is delivered to the customer

2. Release Backlog :- The release backlog is a subset of the product backlog releases support the product roadmap and each release is populated with user stories necessary for that release

3. Sprint backlog :- The sprint backlog is a subset of the release backlog and contains the user stories to be developed in the sprint as we said the product backlog contains the user stories for the entire project and it is the responsibility of the product owner

SCRUM Ceremonies :-

There are four scrum ceremonies :-

1. Sprint planning :- The sprint planning meeting is time boxed at two hours for each week of the sprint if the Sprint is going to be two weeks in duration then the time box will be four hours if the Sprint is going to be four weeks in duration then the time box for the sprint planning meeting will be eight hours it should be attended by the complete scrum team including all roles the most important aspects of this meeting are the team's capacity and the definition of done there are two approaches to selecting user stories for a sprint one is based on the velocity of the team the other is commitment driven team buy-in is critical and the goals of the sprint should be clearly understood and the desired outcome should be clearly articulated with the definition of done then there's

2. Daily scrum :- The daily scrum the time box for the daily scrum is 15 minutes regardless of the duration of the sprint length the entire scrum team including all roles should attend the daily scrum each development team member individually answers three questions what did i do yesterday what am i going through today and what are my impediments this is how the team members coordinate their work and the scrum master learns of the impediments he or she should be taking care

3. Sprint review :- The Sprint review takes place at the end of the Sprint and is time boxed at one hour for each week of the Sprint so if the Sprint were four weeks in duration the Sprint review meeting would be four hours it should be attended by the complete scrum team including all roles plus any other stakeholders who are interested in project success the purpose of the review is to demonstrate working software and obtain and assess feedback feedback may range from full acceptance of the completed software to complete rejection

4. Sprint retrospective :- The Sprint retrospective takes place after the conclusion of the Sprint review and is time boxed at 45 minutes for each week of the sprint so if the Sprint has two weeks in duration then the retrospective would be one and a half hours in length it should be attended by the complete scrum team including all roles however the product owners attendance is considered optional during the retrospective the team answers for questions what worked well what did not work well what should be done differently and what still puzzles us one or several problem detection techniques may be used in the retrospective and this ceremony is a vital part of continuous improvement at the conclusion of the retrospective the teams velocity and the projects information radiators are updated then the next sprint planning meeting takes place and this cycle continues until the project is complete

SCRUM Artifacts :-

1. Artifact for a scrum team it is the primary reporting mechanism for team members and there may be a different definition of done at various levels definition of done for a feature or user story

2. The definition of done for a sprint and the definition of done for a release it's really just a checklist of activities that add verifiable and demonstrable value to the product it's created by the scrum master in consultation with the team a sample list of the items for the definition

3. The story is fully implemented or code completed as described automated unit tests have been developed with at least 80% code coverage automated unit tests and acceptance tests in the story are passing high priority test cases have been automated and added to the regression suite note

4. This is only meant to be an example each team's definition have done will vary slightly depending on the maturity of the team and the specific situation of the team.

What Is AGILE Methodology? Difference Between Agile And Waterfall Model

2020-07-24T14:00:00.001+05:30

What Is AGILE Methodology

1. Agile methodology is an iterative process of development and testing in SDLC process. In this methodology development and testing activities are concurrent unlike waterfall model. In this model business stakeholders and developers and clients work together to develop a product

2. It's very difficult in the waterfall model to go back and change something when the application is in testing stage but that is possible in agile model because in agile model development and testing goes concurrently. Sometimes changes are required because there might be possibility for some errors to come. Waterfall model is not suitable for long and ongoing projects but agile is perfectly suitable for that

3. You can understand the agile model with the better example like suppose we are developing an application similar to what's app with the help of waterfall model but it takes one year to build that application because waterfall model is not good for bigger and complex applications and after one year what's app has many new features and that new application does not have that new features, so the conclusion is market is changing very fast and according to that we have to change also. But we can develop that new application faster with the help of agile model which can help us to create the application faster and application takes less cost also

4. You may not be doing agile development is a lot like running a restaurant everyone has their own specific tasks but they have to work together so all the pieces come together at the right time

5. They have to beable to make all sorts of meals based on whatever customers happen to want each day the team is only successful when the product is satisfactorily delivered to the customer

6. The process in a restaurant starts with the food orders the server collects the orders on tickets that the kitchen then works through in software development business units ask for the products they want developed providing their user stories and requirements

7. In other words their order tickets the agile team has to take all those tickets and figure out how to make all the products so that they all get delivered at the right time to the various business teams that's called the Kanban process based on the Japanese word Kanban for the tickets to used in project planning

Difference Between Agile And Waterfall Model

QUALITY :-

Agile is a continuous and iterative development approach. Thus it provides the scope of iterative testing throughout the process which helps to improve the deliverables throughout the process and ensures quality. Backed by open communication between the teams and clients it assures quality deliverables.

In Waterfall development testing is an entirely separate phase after development and all the testing like unit testing, functional, non-functional, integration, and system testing happen sequentially and takes place near the end of the project life cycle. Thus fixing bugs sometimes become an overhead for the development team.

FLEXIBILITY :-

Agile is so popular, and one of the main reasons behind it is its flexibility. The iterative delivery model of agile allows both the project team and customers to foreseeing the shape of the product gradually before it is finalized. Furthermore, the flexible nature of agile considerably prevents scope creep. An agile project is a contract with the flexibility of modifications.

The steps of the waterfall depend sequentially on each other. If one step is not finished successfully, you cannot start the next step. Moreover, if anything goes wrong at any step post-execution, you need to reiterate all the previous steps. This enhances the possibility of scope creep. Besides, in the waterfall, a contract is inflexible as the project team, and stakeholders agree upon the final product beforehand.

CUSTOMER SATISFICATION :-

Customer involvement is a critical criterion in an agile project. As a result, they can actively participate in development. From a developer’s perspective, it is an advantage as they can get clarification promptly due to the onsite availability of the customers. Whereas, it gives cost benefit from a project management perspective as any additional requirement from client end during development will cost the client.

Interview Tips - How to Introduce Yourself

2020-07-22T23:29:00.003+05:30

Interview Tips - How to Introduce Yourself

If there's one thing scarier than sky diving and that's being asked to tell me something about yourself by a group of strangers in a formal setting.We'll going to give you a ten step process to help you answer this trick question which appears in every job interview.In this article we'll going to learn ten step process to help you introduce yourself in any job interview in fact you can use this in any selection interview.

We'll learn some rules that go along with each step and also about some common mistakes and how you can correct and also we give you some stock phrases that you can use in your introduction if english is not your first language and in the end of this blog we give you a complete introduction that you can use with your own customization.

Tell me about yourself. lf this question comes in a number of different forms for example walk me through your background or take us through your resume but whatever it is this is a trick question because the interviewers asking us to tell them about ourselves and in fact they know everything about us by seeing that resume so exactly what are they asking us to tell them they're asking us for two things one they want to know our attitude towards work what kind of a person am i - they want to know whether I'm a good fit for the job and what I can contribute to the company so we need to catch their attention and keep them interested.

Chances are they've had a full day looking at hundreds of applicants that look exactly like you here's your opportunity to prove to them that you are best suited for the job and now on to that 10 step process :-

FIRST STEP :-
One is called greetings now formal greetings are highly recommended like good morning before 12 known good afternoon after 12 known and good evening anytime after 4:30 or 5:00 in the evening all the way till midnight rules smile be confident and make goodeye contact and common mistakes are like saying hey hi what's up and also fumbling between the good morning and the good afternoon.

SECOND STEP :-
Thank you for the opportunity this is an optional step and depending upon the situation you could either say thank you for shortlisting me for the final interview or thank you for this opportunity to talk about myself now this will not only create a good impression but it'll also help both you and the interviewer relax a bit step

THIRD STEP :-
Your name now I'm Dinesh Wadhwani or you can also say my name is or my name's the rule is to smile to be proud of your name and to enunciate it clearly and some common mistakes here are a saying myself Dinesh Wadhwani or calling yourself mister or miss now the question you have right now is should I use my full name and the answer is yes always please use your full name because simply using your first name may sound a little casual. Category two type of questions are about why you're qualified step number four position and company if you have work experience then this is the time to tell them about the position you held the name of the company the number of years any awards that you've won and what impact you've had on the company what difference you've made to them for example for the last five years I have been the sales manager at dot leading a small sales team and our team was awarded the best sales team of the year for two years in a row I have worked closely with clients and built some key relationships example I am an HR manager at blah blah blah looking after the key functions of recruitment compensation Learning and Development I have over 5 years of experience in the field and we have been able to increase our employee productivity by 8 percent during this period now the rules for this step one sound enthusiastic about your work Two don't sound very pompous like I am a leader I've done everything try to make it sound like you're a good team player rule number three tell them something over and above what they can already read in your resume.

FOURTH STEP :-
Make a claim try to give some proof to make it credible and believable the question you want to ask me right now is should I start with my most recent position and go backwards or should I start with my earliest work experience and come forward and the answer to that is always start with your most recent position and talk about it and go backwards only if it's highly relevant or very important otherwise your resume covers all of that.

FIFTH STEP :-
Qualifications if you're a fresher you're not going to be able to answer step number four and you're going to jump right into step number five solet's see some examples I'm a recent MBA from - - - with prior work experience inthe pharmaceutical sector or I have completed a bachelor's in mass media degree with a specialization in public relations and corporate communicationsor I am currently pursuing a five-year integrated law program at - school with a focus on cyber law if your college is prominent and well-known mention it otherwise let it pass common mistake I am a bmm from NMIMS mm-hmm so if you are a fresher than just one line like I'm a software engineer from so-and-so school doesn't seem enough so this is your chance to add achievement-oriented mini stories for example I was part of the research project on how modern technologies changed the way of teaching in the future where we worked with an ed tech company to evaluate the efficiency of some tech based teaching interventions make sure you talk about a project in an area that's relevant to the employer and if the area is not directly relevant how about you talk about some skills that could be relevant for example you've recently done a project called the impact of gaming consoles on the youth and you're just about to appear for an interview with a food marketing companyso how about you say this to them this project helped us understand the motivations of today's youths and how to attract their attention with our products and services you can also talk about any training program courses or other experiences that you might have had during your graduation question should I mention my CGPA when I'm just a fresher well normally I would avoid it because it's already there on your resume but if you want to highlight your academic achievements how about saying something like I've consistently been in the top 1% or 5% of my class

SIXTH STEP :-
Additional qualifications this may include any outside courses that you did skills that you gained or awards that you want for example I have completed a six-month computer animation course from ... I'm proficient in German and Spanish I have learnt dotnet Java and Python on Coursera which have helped me incompleting a project on so on and so forth

SEVENTH STEP :-
Now use some adjectives to describe yourself to the interviewer for example you could be versatile easy going solution-oriented determined team player or just someone who enjoys working with others now if at this point you're worrying about English and you're saying hey English is not my first language and how am I going to be able to say all of this then I'm gonna introduce you to this app called Cambly that I use a lotwhere you can connect with English tutors from around the world and there are native speakers and you can brush up your conversational English so let's quickly call one of them up and find out what they have to say about tell me something about yourself well I think it's very good to be authentic you know authentic is yes so it means to be very real and be yourself you should definitely use a complicated vocabulary and complicated grammatical structures as long as it doesn't interfere with who you are and how you present yourself

EIGHTH STEP :-
Hobbies and passion this is optional but you want to include this if this helps you build a connect with the interviewer if you think they are significant or it helps you establish some skills that you want to demonstrate to them for example I am a trained singer and the daily riyaaz has taught me self discipline and dedicationor I am a keen runner and this not only helps me keep fit but also helps menet work with other runners in the community I recommend that you keep this section very brief

NINTH STEP :-
Family now this is optional I would typically leave it out of a standard introduction but you can choose to useit strategically if you wish for example my mother has been a housewife andduring my vacations I helped her set up a small tailoring boutique at home with my savings from work or my father is a farmer and I helped set up a process where he could directly sell his produce at the farmers market and bypass the middlemen alternatively you can use this technique to answer this question on family when the interviewer poses this question to you later on during the interview and category three type of questions is why you're here

TENTH STEP :-
This is the point where you tell the interviewer two things one why are you here why are you applying for this job and two why are you a right fit for this job you can also use your future plans and connect them to the company's goals for example although I love my current role I feel I'm now ready for a more challenging assignment and this position really excites me this is a very general statement and you can make it more specific and suited to the company or you can show off your research that you've done about the company and add a little bit of flattery to it as well at this point for example with my passionfor sport and my skills of data analytics I wish to work for a leading innovative sports analytics company like yours and I do believe I can make apositive impact and you can end your introduction by saying that's all from me thank you some rules to follow for step number ten a read the Job Description so you can get some words from there that you can cleverly fit into this answer and second sound enthusiastic about the position and now some final tips tip number one write down your personal introduction and makesure you've included your top selling points for that position this will vary from company to company so make sure you change that and customize that everytime you walk into an interview tip number two jot down and learn only keypoints don't memorize the entire introduction or you're gonna sound like a robot let a little bit of spontaneous he come in and don't worry too much about the grammatical errors that you think you might make the third tip is very important limit your entire introduction to about a minute two minutes is long I would think one minute tops rule number four maintaing good eye contact and look confident while giving all these answers if they're more than one people sitting in the room and only one person has asked you the question don't answer the entire question looking at just that one person look at everyone around the room smile relax breathe and remain confident use a story telling mode to tell about your accomplishments you can use hand gestures if you wish don't go over the top but you can use some hand gestures also sound excited happy about everything that you've done in the past and everything that you're going to do in the future and now let's put it all together and this is your sample introduction on

Tell me something about yourself :- Good afternoon thank you for short listing me for the interview my name is Dinesh Wadhwani I'm the sales team leader at PQR for the past five years making significant in roads into new territories with our products I have worked intensively in both the rural and semi-urban markets understood the dynamic and build some strong distributor relationships I'm an MBA from XYZ with a strong background in marketing during work breaks I enjoy trekking and mountaineering this activity has shown me that good strategy consistency and determination can help you overcome any obstacle I'm a person who thrives in a fast-paced environment and right now I'm looking for an opportunity to apply my marketing expertise along with my creative problem-solving skills to an innovative marketing company like yours

What Is Azure Devops

2020-07-15T17:45:00.000+05:30

WHAT IS AZURE DEVOPS :-

AZURE DEVOPS INTRODUCTION :-

1. Azure devops is set of modern services which is used to :-

-> Plan smarter - To do the proper planning at the time for every new sprint
-> Collaborate better - Work properly and if any error will come in qa testing then we can create the QA bug also to get the developer know about errors and they will fix easily
-> Ship faster - To deploy properly

2. Azure DevOps is all that you need to assemble your product from start to finish.

3. We can understand in a simple way (Dev+Ops= DevOps), which means a combination of development and operation processes for software development.

4. Azure devops is developed and managed by Microsoft

5. Azure DevOps requires no extra configuration. A user just needs to sign up from their Microsoft account to set up a domain, create a project, adding a new user.

AZURE DEVOPS KEYWORDS :-

There are many azure devops keywords they are :-

A. Organization :-
-> Azure DevOps organization is basically by default an account name/ Domain name but we can change it as well.
-> Azure DevOps account and deal with various domains inside, which means we can create multiple organizations with a single Microsoft account.
-> We can configure access control and security for an individual organization as well.

B. Projects :-
-> We can split Azure DevOps organization into multiple projects and can configure access control, pipeline, build process, board and code for an individual project.

C. Boards :-
-> Track the work with kanban board (board which have all the details of the particular project)
-> Work with backlog (for example in a project 3 teams are there all 3 teams work will be there in backlog i.e in backlog team work OR stories will be there)
-> Team dashboard ( each team has dashboard in which stories or work related to particular team will be there)
-> Reporting (Used to do the tasking in every story)

D. Repos :-
-> This will help to store and manage our code in a systematic way.
-> In short if we say then it is used to manage the repo code on the server.

E. Pipeline :-
-> Pipeline in devops is a set of process which is used to make available your project code to users
-> For example when you are working on some story or requirement then that feature functionality will be available for you only but when you deploy your code then it will be available to multiple users
-> And it use to automatically build and test your code project and make it available to other users.

F. Test Plans :-
-> Azure test plans support advance test management solutions for customer feedback, UAT, Automation testing, and manual testing.
-> Azure test plans provides several tools to test our application

G. Artifacts :-
-> Azure Artifacts is one of the extensions of Azure DevOps which helps us to create, host, manage and share packages across the team.
-> Azure Artifacts supports multiple types of packages e.g NPM, Nuget, Maven, Python, etc.
-> Azure Artifacts allows team to share nuget packages from public to private sources

WHAT CAN AZURE DEVOPS DO :-

A. Develop :-
-> To manage our workspace and code repository multiple types of version control are already integrated with Azure DevOps. Almost all features related DevOps already inbuilt inside.

B. Package :-
-> As we know we have already an inbuilt extension available, Azure Artifacts, so we don't need to go anywhere for any type of packages.

C. Testing :-
-> As we know Testing is an important part of the DevOps process. So Azure DevOps provides multiple types of inbuilt testing templates and management tools.

D. Release :-
-> As we know the software release process is a very critical moment of DevOps. So Azure DevOps has already multiple types of inbuilt features to make the process easy and risk-free.

E. Configure / Operate :-
-> As per my experience, it's very easy to configure and operate, because Azure DevOps has a simple process to configure organization, kanban, sprints, etc..

F. Monitor :-
-> Each phase of the DevOps life cycle should be monitor because it helps to ensure the health, performance, and reliability of your application.

G. Reporting :-
-> Azure DevOps has a dashboard where we can see reports, a summary and can generate an analytical report with BI integration.

Top 12 C# Interview Questions & Answers

2020-07-14T11:00:00.000+05:30

Top 12 C# Interview Questions & Answers

Q1. CAN YOU STORE DIFFERENT DATA TYPES DATA IN AN ARRAY IN C# ?

ANS: Yes we can create an object array, we can add any types to the object array including non primitive data types data like customer, employee etc. But we have to override ToString method if we want meaningful output. And we can do that in two ways first by creating the the normal array of particular size and second is we can create the arraylist with the help of collections.

Q2. WHAT IS JAGGED ARRAY IN C# ?

ANS: A jagged array is an array of arrays. For example there are 3 employees and each employee has different numbers of qualifications and we have to print them then at that condition we will use jagged array.

Q3. WHY AND WHEN WE USE ABSTRACT CLASSES IN C# . GIVE AN EXAMPLE WHERE WE COULD USE AN ABSTRACT CLASS IN C# ?

ANS: Let's understand this by an example :- suppose we have two separate classes first is FullTimeEmployee and second is ContractEmployee. We have many common details in this two classes which we have to maintain in both classes hence we have to maintain many duplicate code in both the classes which is not the good programming. To avoid this we can simply move the common code of both the classes into the newly created base class. But the question is this new class will be the concrete (non abstract class) OR abstract class. This question comes in mind because if we make the base class as a concrete class then nothing stopping us to create the object of base class because according to this example in our organization we only create the object of contract and full time employee not base employee class. So that's why we have to create that base class as a abstract class because we don't want to create the object of base class.

Q4. WHAT IS THE ADVANTAGE OF USING INTERFACE ?

ANS:

1. Interface allow us to develop loosely coupled system (system OR code which is not depends on each other)

2. Interface are very useful for dependency injection

3. Interfaces make unit testing and mocking very easier

4. Interface helps us to achieve abstraction and that abstract class will be implemented in another class and another advantage is like by seeing the interface class we can get to know how much functions we have to implement

Q5. CAN WE STORE DIFFERENT LIST TYPES DATA IN A SINGLE LIST ?

ANS: Yes by creating a list of list of objects.

Q6. CAN AN ABSTRACT CLASS HAVE A CONSTRUCTOR ?

ANS:

1. Yes an abstract class have a constructor. An abstract class constructors is used to initialize fields of the abstract class.

2. You would provide a constructor for an abstract class if you want to initialize certain fields of the abstract class before the instantiation of a child class takes place.

3. An abstract class constructor can also be used to execute code that is relevant for every child class. This prevents duplicate code.

4. You cannot create an instance of an abstract class, we can create the instance of the classes that are derived from the abstract class. So, when an instance of derived class is created, the parent abstract class constructor is automatically called.

Q7. CAN AN ABSTRACT METHOD CAN BE CALLED FROM ABSTRACT CLASS CONSTRUCTOR ?

ANS: Yes we can do that. For example we have created a abstract base class and in that we have created and abstract method and an concrete constructor and called the abstract method under that constructor. We have created child class in that we have inherited the base class and and overridden the base class abstract method and just by creating the object of that child class in the main method we can indirectly call the base class abstract method because whenever the object of child class be created then base class parameters and functions will be inherited in child class so at that time base class constructor will call and call the abstract class method (for which definition is provided in child class). In this way we can call the abstract method from abstract class constructor.

Q8. DIFFERENCE BETWEEN INT AND INT32 ?

ANS:

1. Both int and int32 allow us to create a 32 bit integer.

2. Whether we use int OR int32 the behavior will be identical

3. Int32 is not allowed when creating an enum

4. To use INT32 we need to use (using System) declaration but when we are using int we need not have to use that.

Q9. REVERSE EACH WORD IN A STRING USING C# ?

ANS:

1. Split the input string using a input space as a separator

2. Split method returns a string array that contains each word of the input string

3. Select method constructs a new string array by reversing each character in each word

4. Join method join each reverse character word in a string array

Q10. C# ABSTRACT CLASS VIRTUAL METHOD. AN ABSTRACT CLASS HAS A DEFAULT IMPLEMENTATION OF A METHOD. THE METHOD DEFAULT IMPLEMENTATION IS NEEDED IN SOME CLASS BUT NOT NEEDED IN SOME CLASS. HOW CAN YOU ACHIEVE?

ANS:

1. If you need default implementation of a abstract base class method than do not override the abstract base class default implementation method in child class. Just make the abstract base class method as virtual method

2. If you do not need default implementation of abstract base class method then override this default implementation method in child class to get the new implementation and just make the abstract base class method as virtual method

Q11. DIFFERENCE BETWEEN IS AND AS KEYWORD IN C# ?

ANS:

1. The is operator is used to check if the run-time type of an object is compatible with the given type. If it is compatible then it will return true else false. The is operator returns boolean type

2. The as operator is used to perform conversion between compatible reference types. as operator is not of boolean type. It will return null if conversion between compatible reference types is not matched.

3. The is operator returns true if the given object is of the same type else it will return false whereas as operator returns the object when they are compatible with the given type. Else it will return null

Q12. WHAT IS SEALED KEYWORD IN C# ?

ANS:

1. Sealed classes are used to restrict the inheritancefeature of object-oriented programming.
2. Reason why you would want to sealed class is that it improves performance a little bit. If you know that you are not going to be using inheritance on them.

Meaning Examples and Definitions of the SOLID principles in Software and Object Oriented Design

2020-06-28T11:47:00.000+05:30

S.O.L.I.D: The First 5 Principles of Object Oriented Design

WHAT IS SOLID PRINCIPLES :-

1. SOLID principles is a coding standard through which we have a clear concept for developing software in a proper way to avoid bad design

2. It was introduced by Robert C martin

3. When we apply SOLID principles then it makes our code more easier to read

4. It helps us to achieve better testability of code by creating test classes of the classes.

5. This principle is an acronym of the five principles which is given below :-

A. SINGLE RESPONSIBILITY PRINCIPAL

1. One class should only serve one purpose. All the methods and properties should all work towards the same goal

2. So whatever the responsibility of the class it should handle that responsibility only

3. For example : If a class is creating to retrieve the data from the table so it should do the retrieve operation only. It should not perform the other operations in that class. If they want to perform other operations then they have to create other class for that

B. OPEN CLOSED PRINCIPAL

1. Software entities such as classes, functions etc should be open for extension but closed for modification

2. Any new functionality should be implemented by adding new classes and methods instead of changing the current ones OR existing ones

3. For example : If existing functionality is already written to select the data from a particular table and we have to add one more functionality to delete the data from the table then instead of modifying that in existing class we will create new class to add that new functionality OR just we with the help of inheritance we will inherit the existing Functionality and write our own Functionality in derived class

4. Or we can understand like this like one function is already there in order to add a new functionality we can extend that function but we cannot modify that that is why it said like this open for extension but closed for modification.

C. LISKOV SUBSTITUTION PRINCIPLE

1. Derived types must be completely substitute for their base types

2. This principal is extension of the open close principal

3. For example : two classes are there first is animal and second is dog so we can create the object like below

4. Animal obj = new dog(); - Because dog should have all the fields for animal class

5. But we cannot create object like below

6. Dog obj = new animal();

7. Similarly like another example is there : Two classes are there first is employee and second is temporary employee so we can create the object like this Employee obj = new Temporary employee(); but not like this Temporary employee obj = new Employee();

D. INTERFACE SEGREGATION PRINCIPAL

1. A client should not be forced to implement an interface that it doesn't use

2. This rule means that we should break our interfaces in many smaller ones so they better satisfy the exact needs of our clients

3. For example : one interface class is created in which two abstract functions are declared one is to select the data from database and another is to delete the data from table

4. One class is created in which we have implemented the above interface two methods which is fine

5. But I have created the other class in which I need only to select the data from DB but if I will not implement the second function then it will give error to me because that function is abstract function

6. So the solution is for second class we will create the seperate interface in which I will create abstract function and implement in that class then that will be fine

E. DEPENDENCY INVERSION PRINCIPLE

1. High level modules should not depends on low level modules.Both should depend on abstraction

2. The interaction between high level and low level modules should be thought as an abstract interaction between them

3. For example : Two classes are there first one is car and second is Scorpio, Scorpio class has one function drive which car class is using but suppose that if sometime Scorpio function drive become change then it will create the problem for class car. So the solution for this is to create a interface between them and use that interface in child class so whenever Scorpio function be change then it should change in interface also

Programming Gyan

Top 30 OOPS Interview Questions And Answers

Top 25 HR Interview Questions And Answers For Freshers

Top 17 Web Developer Interview Questions And Answers

TOP 20 Software Engineer Programming Interview Questions And Answers

Top 23 SQL Interview Questions Answers

5 Steps to improve Programming Skills

What is MVC (Model View Controller)

Zoom Interview Tips Strategies Online Interviews And Calls

Top 10 Interview Tips To Crack Your Interview

Introduction To Test Driven Development (TDD)

Introduction To SSIS

What Is Dependency Injection

Top 23 WEB API Interview Questions And Answers

Introduction To SCRUM Framework

What Is AGILE Methodology? Difference Between Agile And Waterfall Model

Interview Tips - How to Introduce Yourself

Top 12 LINQ Interview Questions & Answers

What Is Azure Devops

Top 12 C# Interview Questions & Answers

Meaning Examples and Definitions of the SOLID principles in Software and Object Oriented Design

S.O.L.I.D: The First 5 Principles of Object Oriented Design