.NET Zone is brought to you in partnership with:

Presently working as a Solution Architect building offerings, enabling delivery and providing solutions and strategies across multiple customers and domains. Speciality in Microsoft Technologies, Cloud technologies and WOA. Focused on DDD practices, with a sharp interest in highly scalable architectures like CQRS. Anoop is a DZone MVB and is not an employee of DZone and has posted 14 posts at DZone. You can read more from them at their website. View Full User Profile

The Problem with Being Passionate about Technologies

10.13.2012
| 6980 views |
  • submit to reddit
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

Published at DZone with permission of Anoop Madhusudanan, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)