Tech-Blogs

Unnecessary Vs Necessary To Become A Great Software Engineer : 1. Writing code at a fast speed is unnecessary, but writing clean code covering all corner and edge cases is necessary. 2. Doing competitive programming is unnecessary but having the ability to solve problems efficiently is necessary. 3. Speaking fluent English is unnecessary, but having the ability to communicate your solution properly(even in broken English) is necessary. 4. Knowledge of everything in the tech field is unnecessary but having a learning attitude and will to work on new things is necessary. 5. Failing in new challenges is unnecessary but not running away from those challenges is necessary. Software engineers are doing amazing work. Keep in mind all of these things, and you will eventually become a great software engineer. #programming #motivation #coding #programmer # Software

 Most ideal Way To Learn Anything Is By 'DOING' it.  You don't learn until you commit errors, and ensure you don't rehash them. I need to add not many models :   1 . It's not possible for anyone to tackle programming issues in the first go. You make numerous blunders. Gain from them and at last beginning improving. In any case, you learn simply by 'DOING' it.  2 . It's not possible for anyone to assemble the best site in the first go. You distribute the site, get a few inputs/bugs from others eventually begin improving. In any case, you learn simply by 'DOING' it.  3 . It's not possible for anyone to assemble the best application in the first go. You will confront many bugs; you need to accomplish a lot of difficult work and at last, beginning moving towards making the best application. Be that as it may, you learn exclusively by 'DOING' it.  4 . It's not possible for anyone to give their best meeting in the first go. They may ne

  5 Biggest Mistakes We Do As Programmers :  1 . We burn through much time in choosing our first programming language:  Pick any language - C++, Java, or python and begin learning information structures and calculations. Meetings will be founded on critical thinking, not on the number of dialects you know.  2 . We stick to learning one information structure till we dominate in that :  Information designs and calculations are adapted dynamically. Do 20-30 issues on one information construction and continue on. As you move, you will begin getting trust in past information structures and calculations. For Ex-You will begin getting trust in recursion as you begin learning trees.  3 . We don't update our ideas consistently :  Doing new inquiries is alright. Be that as it may, the most significant is the correction of the ideas, which you couldn't do prior.  For every one of the inquiries you were unable to do, bookmark them and continue to update the idea you had utilized in those i

 ' NOTHING COMES EASY ' in this world.   Everything requires exertion and devotion. We should be basically in the top 10% in whatever we are doing.  I need to add not many focuses:  1. Learning information designs and calculations aren't EASY. 90% of individuals flop in that. Like yourself, if you did that.  2. Learning web advancement and sending projects isn't EASY. 90% of individuals flop in that. Like yourself, if you did that.  3. Breaking any work/temporary position meet isn't EASY. 90% of individuals neglect to dominate in interviews. Like yourself, if you did that.  4. Breaking any aggressive test isn't EASY. 90% of individuals fall flat in many tests. Like yourself, if you did that.  Clearly, we can say that it is nearly less troublesome, however, 'NOTHING COMES EASY.'  #learning #datastructures #interview#coding#codingninjas#Competitive programming

 Optimal Roadmap For Any Beginner To Become A Great Software Engineer Step By Step :  1. Initial 4-5 months -  Start with the nuts and bolts of programming and learn information designs and calculations. Practice 250-300 coding questions covering 20-30 inquiries of every point.  2. Next 1-2 months -  Give a beginning to cutthroat programming. Do some essential inquiries on code powers and CodeChef.  Attempt to accomplish a propensity for giving challenges consistently or addressing 2-3 medium and hard inquiries every day.  3. Next 4-5 months -  Become familiar with an expertise in which you can do astonishing tasks. It tends to be application advancement or web improvement, or AI.  Ensure you are rehearsing 2-3 information structures questions every day and ready to make a decent level task eventually.  You can rehearse routinely on any stage or keep in contact with cutthroat coding.  4. Begin searching for temporary jobs. Presently you have each ability, yet you need to get the hang o

  Tragedy Of Life : 1. Learned such hard subjects as SST in class X. - Never used in XI and XII 2. Solved so many hard problems of physics and maths in XI and XII. - Never used it in college. 3. Solved so many hard problems of data structures and algorithms in college. - Never used after college. They all helped to build great aptitude and problem-solving. But I didn't get a chance to use them directly. #learning   #life

  People worry a lot about being 'Slow In Learning' . I also faced similar things during my school and college life and was able to solve this problem.      Let me give you few examples : 1 . During JEE preparation, some people can crack it by studying for 6-7 hours daily. Honestly, I studied 10-12 hours daily and was able to get decent college, not IIT. But it was all worth it. Accept that you are slow and keep working hard. You will get results. 2 . During my college life, I was too slow in learning programming. Rest people were exceptional in that even in the first year itself. But I spent a lot of my time in the second year managing college and programming together and cracked internship in Amazon in the third year. Accept that you are slow and keep working hard. You will get results. 3 . During my Amazon internship, I was slow in understanding the team requirements and the work I needed to do. I spend some late-night hours in the office itself to understand with more clari

  One of the big mistakes people make while seeking out help is being disrespectful of people's time "I want to be respectful of your time so I will keep it short. I am confused about my career and don't know what to do. Please help." "I am looking for help to connect me to investors. Attached is my business plan. Let me know of your feedback" Both these examples lack empathy. They make it hard for people to help them. Because in order to help them, they will have to spend time understanding the context, synthesizing it, and then figuring how they can be of help. Not something most people will do. The best way to get help is to make it easy for people to help you by being specific. #Mistakes #Coding #Tips #Improveyourself

  Whenever you get rejected in an interview, remember these points.  I know it's easy to say, but honestly, these things helped me : 👈 1. There are much worse rejections than interview rejections. You may get the interview again in the same company after some time. So don't take it by heart. 2. Rejection will make you stronger than before. It will push you hard to prepare yourself better, and eventually, you will grow in life. 3. Everybody faces rejections in life. It's not only about you. It's just that God is testing your tough times. 4. A much better opportunity for you may be waiting for which this rejection was necessary. Stay positive. 5. Be honest and ask yourself that you didn't lack skills? If you lack in them, work on them, and if you don't, it is just not your day. Good luck and keep learning :) #learning   #interview   #rejections

  Importance Of Different Skills We Should Learn As Software Engineers: 1. Data Structures And Algorithms : It will build your base of problem-solving and let you enter the world of programming. It will be the most critical skill for your interviews. 2. Development : It will give you a feel of the real power of programming. Building software, websites, apps or applying unique machine learning algorithms are the applications you do as software engineers. 3. Attitude : It is very underrated, but companies do HR Rounds for this only. It will help if you have a proper learning attitude and good reasons to become a software engineer. Some Other Good To Have Skills : - Aptitude : Some companies do ask in the first round, so be ready for that. In general, it's always great to have good logical skills. - Competitive Programming : You don't need to be a star. But giving timed tests online will help you crack the first round of companies. So doing competitive programming enables you to s