Gopal Singh

I am a full stack developer, uh, mostly working on the back end side. And we have worked, But, uh, for, uh, mostly on the buttress and then, uh, core PHP and, uh, for Ionic applications. And, uh, if, Uh, we talk about the academic session, and I have completed my, uh, BCA in the U of C degree, And the first position is, uh, MCA that is masters of computer applications. Okay. And, uh, currently, I am working as a full time freelancer on Upwork, uh, mostly on Upwork, and, uh, I have a good clients and have a strong profile in The, uh, top rated, uh, developers on the uh

If we talk about the mentoring a junior developer, so, uh, we I would, uh, say, he will just, try their best and then if they get stuck somewhere, they can research on the Google management then, uh, depends, like, if they need help, uh, I can so, uh, guide them with the best practices and the recommended process and to improve their technical skills, uh, they should keep learning. And whenever uh, they do something, they make a note and make a note to improved data skills. For example, if they have done a task and they, uh, in future they need a reference, they can look back on their how they did they complete it and what they did for that. And they should uh, keep learning, that is the best thing to improve the technical school skills. Uh, and do not worry about the remembering this index. Just the logics app and how we can, uh, do, uh, anything, uh, which which needs to be implemented with the advanced practice, that is the best way.

What techniques do you like to keep your code clean, maintain and testable? Uh, to keep the code clean, uh, it should be, like, clear, like, what we are doing. Uh, and, uh, we should, uh, keep a track of, like, what what variables we are using. We are using the meaningful in full variable names, and we are not taking additional not required memory to implement anything on whatever we are doing. And uh, always comment, uh, comment out their code. Our code to, um, understand, like, if someone uh, someone else, uh, need to work on the uh, project you did, and it should be, uh, easy to understand and what how things are going up there. So it would be uh, data to and if we are making changes, we need to make, uh, make uh, take off, uh, versions, and we can use, like, uh, versioning tools, uh, GitHub, or would be s v n. So what whatever the changes at the end, we should be making it uh, commendable and we can use the username and the quote merge effector. So that should be doable. And for uh, the testing, uh, I think it is always good to have if we do all the things, uh, in the recommended

Yeah. For example, uh, we can make improvements, uh, like, we in the in the internal functions, speed don't don't need to Yeah, like there is another problem in the making object of the class, So we can improve that, uh, by doing something, and it would be, uh, great if we can make it more improved. And, uh, to be honest, I don't understand, But I don't do not work on the c sharp, so I don't have much idea on that.

The repository being quoted and enjoyed its made scoring statement. Like, uh, it it should be in the particular, uh, like it should be in the m a c, uh, structure and it should be everything should be enclosed with the classes and if required any interfaces and if we need if we are doing any, uh, enhancements Like the existing classes. We should extend the, uh, existing classes and then we can to make the new classes and, uh, everything should be, uh, comment commented it should be I think that's

Can can this code in training singleton pattern Is an any of the digitization is implemented. No. I don't know the c

Because, uh, where is, keyword, so it is, uh, that is the wrong thing there in the code.

What challenges have you faced in the meeting, customer needs, and requirements? How did you Uh, Jellins, um, mostly the Jellins is, uh, when we don't know what exactly is required and so that requirement and specifications plays Big role in the customer needs and requirements to be fulfilled. Otherwise, if we are not, Not even started in the, uh, correct direction. We we can can't expect it to be fulfilling uh solution. So that is thing and That's all. I think the communication is the, um, most important. So if they we are working in the milestones and we keep communicating about the requirements and needs, and it would give a fulfilling product that is

Today's is would you recommend improving the performance of RESTful APIs? Uh, I don't know c but, uh, like, uh, in the RESTful APIs, uh, normally the recommendation would be to, uh, less shash usage of the memory and, uh, it should not not take much time to, uh, give a response, so it should be, uh, like fast enough and if the code is sharp is short and reusable. That is the thing to make a good API, shell I think depending if we talk about the performance

To the it will be, uh, easy to, uh, go in a way so that we write and solid principle that, uh, I think we it will, uh, be, uh, very plus in