Skip to main content

The problem with being passionate about technologies

imageThe title is a little bit misleading. There is nothing wrong with being passionate about technologies you love/like. In fact, I believe in being a passionate developer, and I appreciate having passionate people in my team and around me.

The real problem is – being subjective about something just because you are passionate about the same.  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 us 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 boy friend Winking smile

Subjectivity is bad because it’ll hurt others and yourself, and won’t let you focus on the real problems. Hence, especially with in a tech team, I think it is 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. lol.

Popular posts from this blog

Creating a quick Todo listing app on Windows using IIS7, Node.js and Mongodb

As I mentioned in my last post, more and more organizations are leaning towards Web Oriented Architecture (WOA) which are highly scalable. If you were exploring cool, scalable options to build highly performing web applications, you know what Node.js is for.After following the recent post from Scott Hanselman, I was up and running quickly with Node.js. In this post, I’ll explain step by step how I’ve setup Node.js and Mongodb to create a simple Todo listing application.Setting up Node.jsThis is what I’ve done.1 – Goto http://nodejs.org/, scroll down and download node.exe for Windows, and place it in your c:\node folder2 – Goto IIS Node project in Git at https://github.com/tjanczuk/iisnode, download the correct ‘retail’ link of IIS Node zip file (I downloaded the already built retail package, otherwise you can download and build from the source).3 – Extract the zip file some where, and run the install.bat or install_iisexpress.bat depending on your IIS Version. If you don’t have IIS in…

MVVM - Binding Multiple Radio Buttons To a single Enum Property in WPF

I had a property in my View Model, of an Enum type, and wanted to bind multiple radio buttons to this.

Firstly, I wrote a simple Enum to Bool converter, like this.

public class EnumToBoolConverter : IValueConverter { #region IValueConverter Members public object Convert(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture) { if (parameter.Equals(value)) return true; else return false; } public object ConvertBack(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture) { return parameter; } #endregion }

And my enumeration is like

public enum CompanyTypes { Type1Comp, Type2Comp, Type3Comp } Now, in my XAML, I provided the enumeration as the ConverterParameter, of the Converter we wrote earlier, like
<Wi…

Top 7 Coding Standards & Guideline Documents For C#/.NET Developers

Some time back, I collated a list of 7 Must Read, Free EBooks for .NET Developers, and a lot of people found it useful. So, I thought about putting together a list of Coding Standard guidelines/checklists for .NET /C# developers as well.As you may already know, it is easy to come up with a document - the key is in implementing these standards in your organization, through methods like internal trainings, Peer Reviews, Check in policies, Automated code review tools etc. You can have a look at FxCop and/or StyleCop for automating the review process to some extent, and can customize the rules based on your requirements.Anyway, here is a list of some good Coding Standard Documents. They are useful not just from a review perspective - going through these documents can definitely help you and me to iron out few hidden glitches we might have in the programming portion of our brain. So, here we go, the listing is not in any specific order.1 – IDesign C# Coding StandardsIDesign C# coding stand…