Add real value, don't be workaholic!
Adding more value or becoming a workaholic? | Image by Jonny Lindner

Add real value, don't be workaholic!

Friday night, 10 pm and keyboard typing sound can be heard on the floor. The one who is creating that noise in the silence is thinking,

it's only 10 PM, I can do much more!

Often freshers in the software industry think that they can add more value by working extra hours which in certain cases can be true if you are just reading and understanding the code or the product.

It's very important to understand what adding more value means. Some people think workaholic people add more value because they spend most of their time in office. As most of the studies have shown, productive work can be done in less than 4 hours a day and past that is the time you should start adding more value.

Following are some points which I think can really help you to add more value,

Upgrade your skills and knowledge

By Skills I do not mean only the programming languages but certain ways of doing things, libraries, methodologies etc.

E.g. You might be knowing how to do one thing but there can be other approaches to do it and some of them can be way better than what you were doing. Explore them and upgrade yourself.

Read books e.g. Clean Code, Clean Coder, Test Driven Development are some.

Help and educate others

Collaborating, discussing, reviewing can improve the knowledge of the team and upgrade the entire team to a new level. Generally, single point of view misses out some corner cases which can get revealed when you discuss the approach or the problem statement with your colleagues.

E.g. Conduct training sessions of the technology or methodology you know.

Take ownership

Taking ownership of your work is a very important quality. Be proud of what you do and take the ownership of it. Your managers (or the one who is above you in the hierarchy) will rely on you and will be confident about your work due to this.

If someone is facing issues in the module owned by you help them, if there is any issue raised by product verification team, peek it proactively.

Take initiatives

This is one of the important point to note. Not everyone has valour to act on this point. Most of the team members always think about doing something but they need someone to act upon it. You can be that person, who will be recognized by others.

Header image by Jonny Lindner from Pixabay.

要查看或添加评论,请登录

Sachin Gorade的更多文章

  • Common misunderstandings of Software Developers

    Common misunderstandings of Software Developers

    Software development is a complicated subject. There are many things we have to learn almost every day and it is…

    1 条评论
  • Integration tests vs Unit tests

    Integration tests vs Unit tests

    There are various types of testing which happens in the software development process. Unit testing, Integration…

    3 条评论
  • Why Interfaces are recommend by Spring?

    Why Interfaces are recommend by Spring?

    Spring framework has become the central part of every Java based micro-service application. Spring beans work with…

    4 条评论
  • What makes REST API really usable?

    What makes REST API really usable?

    REST APIs are the most critical part of every application today, be it a blog or an application which is running on…

    8 条评论
  • Micro-services and DRY (Don't repeat yourself)

    Micro-services and DRY (Don't repeat yourself)

    DRY is one of the basic principles of software which not only programmers but the DBA, technical writers and everyone…

  • Why features fail?

    Why features fail?

    Unclear requirements Each product company follows a different path for adding new features. Some follow…

    6 条评论

社区洞察

其他会员也浏览了