After completing our college life, when we enter the corporate world as an IT fresher we face lots of challenges and hurdles in our early days, if we are aware of things that we should avoid, then we can prepare ourselves in advance to face them head on. I am writing this blog to highlight few such key points that I think we should avoid as a fresher.
1. Never try to master all at once:
"Be a jack of all, master of one", we learn a variety of things during our academics days in college, but usually we don't focus on a specific interest that we want to pursue as our career, In IT there are variety of different fields or areas of expertise that you can pursue, sometimes you might be interested in more than one at a time, but remember if you try to become an expert in all of them together and if it exceeds your capacity you might stumble upon and end up troubling yourself. In this case undestanding your limits can help you decide what is your capacity and how much can you focus at a time.
Conclusion - "Focus on single area of expertise at a time and don't bite more than you can chew"
2. Half baked plans can cause serious damage:
Whether it's a hobby project, or a full fledged commercial app idea, planning is extremely important, when we are freshers we are very enthusiastic about our new job that we have achieved, we are eager and want to try to implement all those things that we learnt during our academics in college, it is good thing if the task in hand is a minor or simple, but for complicated or major tasks its better we follow the development plan, we should analyse the task and plan it out first how to implement the task in hand, its better we have 2 - 3 approaches/alternatives in mind, after analysing and planning we should discuss it with one of our seniors.
Taking a third person view always helps us to make our plan more perfect and we get to learn new things in early stage, if you don't have any seniors available try to search online and read the related articles and discussions on the topic before you take any decisions yourself and get started. This helps us keep the quality of the output in control as well as avoids those multiple rework attempts and multiple rejections from seniors at the later stage.
Taking quick decision is a good thing helps develop and deliver faster, but if that is hampering the quality of the product then you need to slow down a bit since because of that company can loose potential clients, Freshers should be aware of the actions they take on there own to avoid any mishap they should
Conclusion - "Always plan, discuss and then implement"
3. Do not allow inconsistencies to enter your code
Inconsistencies may seem trivial to you now, but they will come back and haunt you later. We always like things to be done our own way, whenever any existing project is assigned to us as a freshers, we usually develop the new feature in a new pattern that adds inconsistency to the project this lead to difficulties in maintenance in future.
Do's for fresher :
1. If you are assigned to an existing project then in the project you can find a way in which the things are done. In such case we should first study the existing code and try to understand the pattern used and continue to follow the same pattern to maintain consistency to make future maintenance easy, it is best if you get a quick introduction from one of your senior on the project.
2. Any new ideas or changes in pattern that we have should be noted down and should be proposed to the team first before implementing it,
3. If any new pattern changes are to be implemented its best to implement it through out the project if possible, else should plan the changes in parts.
Conclusion - "Always keep your code consistent"
4. Keep it simple stupid (KISS Approach)"
There are varieties of challenges that a fresher can get in the beginning days, sometimes this challenges might have a simple approach to complete it but you may end up complicating it or taking another approach that makes the challenge even more difficult.
This might happen due to various reasons depends on the environment too, it might be due to overthinking, or might be because you have not given it enough thought or the time limit might have forced you to take those decisions, to keep it simple we should first clear our mind think straight, use materials around you to write down all the alternatives, compare them to find which helps you better to achieve the challenge in simple and better way and go for it.
Adding complexities to the task will create difficulties for you in future to maintain it.
Conclusion - "Always try to keep it as simple as possible, without adding unnecessary complications"
5. Understand the domain in which you are working
If you don't understand the domain, the science, the industry, the exact outcome of the software project, you will not be able to deliver quality results. Ensure you make every attempt to undestand not just how to code/program but also the domain.
This was all for this blog article. Hope you found this useful and informative.
Stay stuned for more, later!