Dhiraj Chaudhary

Okay, so I believe in Indore, and I've been working as a Ruby on Rails developer for the last four and a half years. And, I've worked in 2 companies previously. In one company, I worked for three and a half years, and another company for one quarter, one year, and two months, basically. So, in that time, I worked with Ruby on Rails. I worked with JavaScript, using jQuery, AJAX, Axios, and the database technologies I've worked on are MySQL and Postgres, basically. And, other than that, I have a good knowledge of our specs, the test cases that cover the controllers, the request specs, basically, the model specs, the service specs, and also the database schema specs as well. So, I basically covered that. And, I work with front-end technologies like React as well. And, Vue.js is basically used on the products I've worked on. And, I have experience working with product-based companies as well as startups as well. So, I have knowledge about connecting with developers around the world, I've worked with developers from the UK, the US, Ukraine, Russia, many places, working for foreign clients like US clients, UK clients, and Canadians as well. So, I'm having knowledge about connecting with people from different areas as well, working on teams also, having experience managing teams as well for a few months, at least. And, I have knowledge of sprint planning, scrums as well, how we do management, and I have knowledge of the version control system like Git, for more than four years, basically. And, I've used multiple technologies inside them. I've used Liquid as well. I have knowledge about the CICD tool, Jenkins as well. So, basically, the deployment part as well, I know. I have knowledge of the cloud platform that we're using, Google Cloud Platform. I have knowledge about that as well. So, I have a pretty good understanding of multiple areas that I've worked on, three projects basically till now. So, yeah, that's

So, basically, how can we ensure that our code adheres to solid principles. We look at the code and follow the standards provided by Ruby on Rails. We follow the naming conventions that Ruby on Rails provides. We have to follow every line of RuboCop issues as well, and solve them. Our code should be in an optimized manner, in the safest manner as well, so it's not vulnerable to any particular part or scenario. It should be clear, and everything should work perfectly in an optimized manner. Our code should be durable and exist for a longer period of time. Our code should be independent. They should follow all the basic ops concepts that we have in Ruby on Rails, and not go against them. We should utilize all the functionality provided by Ruby on Rails in our code whenever it's necessary, instead of using external gems unless it was necessary. That way we can cover all the solid principles, which can make our code and platform more secure and safe.

Yeah, okay. So, basically, I was working on a project where I had to build the auctions functionality. So, when the options were available, we had to create the tutorial. Like, basically, an automatic auction should happen where participants would automatically enter their own values, and the changes would be reflected on the front end. So, basically, the view was the real view in which we had multiple slots, with multiple line items. And, basically, each line item had its own particular values, including quantity and amount values. To solve this, it was a kind of complex view, so the value should change on an emitted basis, and the amount should reflect on the front end. And the request should also be made to the back end, basically. So, for that purpose, I had to use JavaScript. And, it was the most challenging part for me because, to deal with it, there were multiple data complexities that we were facing. Multiple scenarios were there, which needed to be solved in a timely manner, without breaking other things, because it was a complex area. So, it was one of the hardest parts that I dealt with, creating the auctions and their values. And, to fill out the values that we were having, we had to give out the particular amount for particular line items, and for all the multiple values that we had. So, it was kind of a hard thing to do.

JavaScript was basically the right solution because we needed the exact change at the right time only at that particular moment. Basically, if you like, we have to reflect any particular value or a particular click only. So without any reload, reloading the page, we needed JavaScript for that purpose because JavaScript was the more advanced part. And, it suits with Ruby on Rails perfectly. Like, with Ruby on Rails, it adds up perfectly for our particular use case that we needed, to be on the same view and to be on the same page and without reloading, reflecting the value there. So also, for the particular Ajax calls that we needed, like, in our past project. So for that, we were using JavaScript as well. So it perfectly connects with that multiple use cases where there are many which were helping us from that.

I basically am not having the idea about client 6, 69 yet. However, I may be having the idea about the CICD, the Jenkins there that we were having for the deployment purpose while Google Cloud Platform was there to deploy our code to the server, basically, to run the application. So I'm having the idea about that where we are configuring the environment, configuring the setup, we are doing using multiple services to run the instance, the project ID. The project, basically, we got created on that instance, applying that, configuring our application there, installing all the requirements that we needed, and running our application, and maintaining it at the end. So that's the same done with the AWS as well, where we are creating our instance. We are having our EC2 there, basically. And then going with the database services as well, then the storage part as well. Yet. So, and at the end, configuring that and maintenance. So that's how I've done. I haven't used Cloud 69. Cloud 66, basically, but went ahead with that.

I haven't actually used DigitalOcean for my project yet. I haven't had the chance.

We are making our show action, but we are not rendering any particular page here. And we are not giving directly, but okay. You know, we are having the page. It will be there. That's for a simple view only. This is not an API based. I think the application controller, users controller is for their user. Basically, what we are doing here is that we are actually fetching the user from the params we have, and then we are giving a condition if the user is nil. Like, if the user is not present, then we fetch, send it, and redirect it to the dashboard. The landing page, we can say, the root URL we have. There, we are redirecting if the user is not present. There are no issues other than that.

I think communication can be between, like, if we can store the values in the cache, the cookies, we can have them. Inside them, we can store the village, which can be used afterwards. So, basically, that we can do that or asynchronous communication you're saying.

We have to particularly create a good structure which can be perfectly fine. Like, it should not fail while we have created the application, and it should not be causing any issues. The complexity should be 0. It should be maintainable. We can say it should be easily maintainable even if we are getting any issues and can be easily modified, making it modifiable as well. Like, we can modify them. So that's what we can do to create any particular Rails application. The architect should be correct there. For things to be perfectly covered previously. Even before creating, we should be perfectly clear about all those scenarios, cover everything there, and have everything planned on that purpose.

I worked on a particular controller, the particular area of the project, which was previously built but needed changes because it was built on old concepts, and the code was not well-refactored, it was in very bad condition. So, basically, I had to create the whole functionality of setting up a new controller for that purpose. I said I modified that controller from scratch. Like, I went ahead and created the functionality there, did all the refactoring of the code that was necessary, covered all the parts that could create issues, and there were many issues at that moment as well. So, we went ahead and solved all those issues. All those issues were fixed inside the fix. Like, all the things we were having in the past were fixed, and we created well-maintained code that was optimized and followed the current principles, including the standard of the code that we need to follow, and we followed all of that.