Junior Developers – Know Your Tools!
Save Recoding Time and Do Not Skip Basics!
The desire to deliver new milestones quickly can often lead to turning in circles. Rushing forward without a plan can ultimately be more time consuming and lead to frustration. Developers often forget that not covering the basics may lead to poor performance in the future. Junior developers are enthusiastic about new technologies and tend to dive in to development without proper forethought. Unfortunately, we rarely see smart coding and full use of development tools’ functionality by juniors.
About a year ago, a misconception by a junior engineer almost led to a wasted day of coding. The guy deleted his all-day-efforts by mistake and said:
“I remember most of it! It will take me about three hours to code it again tomorrow.”
Three hours on a tight budget – impossible. That day he learned from his colleagues that Eclipse has a great history and rollback functionality – 10 seconds instead of three hours.
If only junior engineers paid more attention to the basics and “tedious” tutorials, thinking – “Yes, this will save me great hustle!” instead of – “I am not going to use this ever… Let’s skip and dig into the interesting part.”
It isn’t only juniors that let such thinking block their productivity. Even experienced developers make mistakes by not taking time to research the optimal solution, often on a code-refactoring day. Work is done, however two days later you remember – “I made some changes using the old method. The enhancement I just remembered will increase performance double fold; will require less coding and I can do it in less than 5 minutes. If only there was a way to go back…”
Always cover the basic functionality of the tools you use – make it a habit. Whether it is Eclipse, NetBeans or another favorite tool:
- Know where file history is kept and how to use it.
- Carefully review the basics of a technology and its new features. You never know when you are going to need them.
- Code smart even if you are at the start of your career and wish to spend 15 hours a day coding, just because you enjoy it. Enjoying your work does not mean you should code the same thing repeatedly.
ScaleFocus Team Leaders