Over a million developers have joined DZone.

The Problem with Being Passionate about Technologies

· Java Zone

Discover how powerful static code analysis and ergonomic design make development not only productive but also an enjoyable experience, brought to you in partnership with JetBrains

I believe in being a passionate developer, and I appreciate having passionate people on my team and around me. The real problem is being subjective about something just because you are passionate about the same. A few quotes:

Subjective

Subjective information is one person's opinion. In a newspaper, the editorial section is the place for subjectivity. It can be based on fact, but it is one person's interpretation of that fact. In this way, subjective information is also analytical.

Objective

Objective information reviews many points of view. It is intended to be unbiased. News reporters are supposed to be objective and report the facts of an event. Encyclopedias and other reference materials provide objective information.

Now, let's relate this to the developer’s life. Think about how you selected a specific framework or platform for your last assignment.

  • Whether your decisions were made using objective parameters? Like
    • POCs that confirms the merit of the framework/platform/approach
    • Team goals like cost, scope, quality
    • Valid references with in proper context
  • Or, you were driven by something subjective?
    • Your comfort level
    • Your own ego to prove what you suggested
    • The person who suggested a different approach was your wife’s ex-boyfriend.

Subjectivity is bad because it’ll hurt others and yourself, and won’t let you focus on the real problems. Hence, especially with a tech team, I think it's important to have a mutually-agreed protocol to take architecture and design decisions objectively – and not subjectively.

I’ve observed that practicing two critical points should always help

  • Be open to explore suggestions from others - It is possible to have multiple ‘rights’ as two ways can lead to the same destination in the end.
  • If you have difference of opinions, be open, take that offline and have an in depth discussion focusing on the problem + solution.

So, I believe you can enjoy your coding better if you have an objective view point as I’ve myself fallen for my subjectivity multiple times. And a line of disclaimer:

I wrote this post as an objective fact but is clearly a subjective opinion

Learn more about Kotlin, a new programming language designed to solve problems that software developers face every day brought to you in partnership with JetBrains.

Topics:

Published at DZone with permission of Anoop Madhusudanan, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}