A few tips to help developers improve their capabilities

When I was young, I used to see my father beat his boxing, professional boxers were often divided according to their weight, including many different grades such as feather, fly, middle, middle and heavy … Our developers can also Such rankings, but not by weight but by skill, consist of many different grades from intern, fresher, junior to senior, tech lead …

I myself am currently a feathered, fly-type developer, so my surroundings have a lot of my classmates, even though you have not been ranked yet. I realize that many of you have difficulties, don't know how to train yourself to improve your ability, increase your rank.

Training skills is a long way for each of our developers, which requires a lot of time and effort. Everything will be easier if we use our time and effort appropriately and effectively, otherwise, everything will be meaningless.

Learn how to improve debugging

Every line of code you write has the potential to cause errors, every software has errors. So, to become a great developer, you need to train your error-finding, bug-fixing skills, you need to be a bug-killer, no bug can get through your hand.

However, I find that the developer-class, fly-class developers often avoid debugging, making their debugging ability bad. Every time the code has a bug, they often immediately search for a higher-ranking guy to seek help. As a result, some high-class guys are getting better because they are exposed to many bugs, they learn how to judge errors, how to find errors, handle errors …, and those who ask to fix bugs are not learning anything. both.

In order to improve coding and debugging, I think we should learn to solve our own problems, independently fighting the bugs. Do not rush to ask for help and you sit and watch, just seek help when you have really tried your best but still have no results. You will probably finish the task slower, more tired, but you will learn more things, more advanced levels.

Learn how things work

Jobs for fresher and junior positions are usually quite simple, usually following something available. For example, making a web page based on an available web page, code a function based on the old functions … The reason is that because of the fresher level, junior is not enough to be able to do an independent job. This is not wrong, following what is available by senior seniors will help us learn many things. However, I find that many of you rely too much on what's available, just copy / paste the code from what's available, tweak it to suit your requirements and complete the task. That's not good.

I have seen a lot of you do not understand the basic theory of the web, do not understand how ASP.NET MVC works but still complete the assigned task, the reason is that they rely on the old code available to do something similar so. As a result, these students do not learn much from the work process, they only learn how to cope.

In my opinion, to be able to grow fast, best, we need to keep an open head, a curious head. Don't be easy on what you do, be curious, understand why it's done. Try to understand why the saints on stackoverflow give such instructions, not just copy their code. Understand why the old code is like that, not just imitating it. As above, you may be able to complete the task slower, more tired, sometimes criticized by the boss for slow work, however, think for yourself, learn how everything works well for you.

Don't just finish the task, look at the bigger picture

As I said above, jobs for low positions are often very simple, these jobs are usually only a very small part of an extremely large system. Therefore, hair-type and fly-type developers are more likely to fall into a situation like pawns on a chessboard, not understanding the whole world, not opening their minds, not learning more complicated knowledge.

So, take the time to find out where the things you are doing are located in the system, what their mission is, why people do that … So you will learn how they set system design, the way a larger system works, even the way their business operates … Don't just work hard like a mercenary, that's wrong, that's not good for the mind yours.

Of course sometimes hiring is the job the company hires you to do, they don't pay us to go there to find out what we're not responsible for. Assuming that your task is to edit a bit of css, of course they don't want you to spend an hour trying to understand how the whole website works. However, always trying to look at the bigger picture helps us learn more things, understand the system more, and gradually we can take on more complicated tasks, which is also beneficial company side. On your side, if you don't want to be a pawn, don't act like a pawn, always try to look up to see what they're doing above your head.

Always looking for holes in knowledge

Have you ever fallen into a sit-down situation but didn't know anything? If you've ever, the reason is because you've missed an important thing that is tracking the gaps in your knowledge.

There was a time when I always had difficulties in dealing with disagreements with C #, each time I did something asynchronous, I spent a lot of time. I know that I have a gaps in knowledge, but I do not have enough time to study, then I forget that I need to study that knowledge again. As a result, the next time I encountered some asynchronous things, I spent a lot of time, things kept repeating several times like that. Finally I decided to create a Trello list called "knowledge gap" and put "asynchronous in C #" on that list to remind myself to improve this knowledge, then I don't forget and the situation improved. I keep the habit of knowing what I don't know, what important knowledge I do not understand is that I have included a list of "knowledge gaps" to gradually improve. The results are quite satisfactory. Sometimes we don't have time to improve, but we simply don't know what we need to improve. So monitoring the end of the gap will help you fill the gap, improve your ability.

Train yourself every day

In addition to work, in addition to the code at the company or school work, take the time to train yourself every day. We have a lot of fields, knowledge that needs to be trained outside of technology, take time for them.

A soft skill book, a clean code book, a history book, an English lesson, an hour in the gym room will help you become a better person, a better person Also a better developer.

Conclusion

The things I mentioned above do not immediately turn you from a fly-class fighter to a heavy fighter, but I think it will help your promotion path to be shorter and more efficient.

If you are a medium and heavy developer, do you have any advice for the top-level, fly-based developers?

Source : TechTalk