I started to code for quite a long time now, later I mastered the skilled for techno-functional opportunities because I talk well, I plan well and of course, I listen well. Most of the problems that I have received to puzzle out would are usually the same old base group problem.

I must say, coders, these days learn a hell lot of framework and they get professional exposure to that. I have seen coders that can code complex systems in some time and solve complex problems. I have even met people who never use stack overflow to look over a problem or a coding issue.

Personally, at my workplace which has great architects and coders and technical niche personnel that a configuration itself can solve their problems. But there is something when it comes to debugging or solving problems out of the box, going to the core of the problem and solving it or at least get a workaround. I have made myself a person like that, taking complex problems and solving it using my design patterns which do not have a patent yet. I learnt this while I was in my grad days, to understand the problem to the core and go logical by nature.

I have a weirdly wired person with a combination of solving a logical problem with the analytical method and analytical problem with logic in mind. To be a person like that, you’ll have to wire your brains with threads. Yeah! Multi-threading I mean and be good with the basics of course.

I came across a really good article, from Kesk -*- (40 Tips that will change your coding skills forever) and I agree in what he has said and trust me, that will help you out. I would surely make a video on that, and filter down a few.

Whenever you come across a problem: Trust me, you usually are not the one for the first time in history. Secondly, in case you are the first one to encounter a particular problem, rely on community support as well, and even contribute to it. Lastly, if you want to understand the problem, learn Data Structures and Design Patterns and master it. Learn recognizing a problem and if it is a big one, break it into pieces. You can use the same method while you are developing something.

Lets drill down a bit for Kesk’s article and make sure how it fits in :

1. Take the code and break down big pieces of code into small functions. : This method called as Modulating or using subroutines to break complex problems. But you’ll have to understand the concept of the time complexity and space complexity of the problem. It’s easy to say — to break the code in sub routines and imply the logical bind mechanism called as merge to achieve a task. But if you many of it, basically it will take more space and time. So, use the critical ones and modularization based the given priorities (Example: a Login or Authentication Module can independently invoke security protocols)
2. If by the time you leave work you haven’t solved the problem. Turn off the computer and leave it for the next day. Don’t think about the problem anymore. (A relaxed mind also ways gets a solution, or share your problems with people who you think can help out) : The work life has made us too logical in nature and we return to our human minds when we are tired. Logic is a mechanical by nature but, you are still human.

#design-patterns #coding #programming #software-development #coding-interviews