Whether to Use Open Source or Windows Development Platform

The following questions was on LinkedIn today:

How to decide whether to use Open Source or Windows development platform.  we are working on creating a SAAS model for a payroll and HR software. The debate we currently having is to on what software to develop Open Source or Windows. Need some help to decide the parameters on which to compare so as to come up with a logical decision rather than the decision based on gut.

Here is my response:

I started typing a couple of different responses, and then stopped as it occurred to me that the world of the operating system has turned upside in the last ten years, because your choice for OS is literally Mircrosoft or Open Source. All of the other vendors have either gone open source or are too small to consider as real choices anymore.

So from the OS point of view, it is a choice of who your support vendor is now.

Once you choose your operating system, then you need to choose your software packages. This is where in-house skill is a big part of the equation, because if you don’t have people that will take complete ownership of both the framework and custom code, your open source options narrow. You have to look at which projects have the most solid team that will still be updating the product n years from now. Currently, those are products that either have vendor sponsorship (and you expect the vendor to be around n years from now) or are so wildly popular for so long that even if the current group gets rich and bored someone else will step in.

And, back to the Windows or something else question: For a web-based application, if software doesn’t run on both (at least a version that runs on both), I wouldn’t consider it.

But (as Dennis Miller used to say every week), that’s just  my opinion. I could be wrong.

If you found this interesting, please share.

© Scott S. Nelson

Scott Adams Nails it Again

This will be considered a classic. It is relevant at least every three years… (Click the post title to see properly until I get around to customizing this blog more)
Dilbert.com

If you found this interesting, please share.

© Scott S. Nelson

Some Comments on Offshore and Outsourcing.

This question came up on Linked In today, and I thought I would post my response to it here for those that don’t belong (and if you don’t and you are reading this blog, you probably should):

I read the question as one about outsourcing, and I see many responses about off-shoring. I’ll give my 2 cents on both, and you can owe me a nickle including tip.

Outsourcing is a way to mitigate risk for mission critical goals. The mitigation is in two forms. The first is, outsourcing to experts provides the perceived safety that the job will get done correctly. The perception is right about half the time (in my experience).

The other form of risk mitigation is the ability to place the blame for any failure on the vendor. As a vendor, I know that the likelihood of this being the reason for outsourcing increases with the number of people involved in the decision.

Off-shoring is a mixed bag. There are some companies that are really good, and some that are not. There are individuals within companies that are really good, and many that are not. In other words, on one level there is no difference between offshore and outsourcing.

On another level, there is the communication gap that is unavoidable due to both cultural and temporal differences. There are some companies that try to offset the temporal differences by having teams that work hours that coincide with US business hours. Anyone who has ever used 24 hour services knows that the best and brightest rarely work in the wee hours, and those that do are still not at the top of their game.

Off shoring works great for both parties far more often if the requirements are crystal clear and fairly static. Otherwise, your mileage will vary. Since the successes are a huge boost to ROI, they are well publicized and very motivating. The much more frequent failures are kept low key to protect careers.

And, as Dennis Miller often said: “But that’s just my opinion…I could be wrong”

If you found this interesting, please share.

© Scott S. Nelson

What is Web 2.0?

I saw this question posted on Linked-In today and thought I would blog my input, especially as I have been tied up with some paid work and haven’t been blogging as much lately…

Q: What are the differences between Web 1.0 and Web 2.0?

A: In addition to answers already provided, Web 2.0 is often a battle cry for selling new IT products and services rather than an actual technology. It encompasses AJAX, blogs, wikis, RSS, mash ups, and just about everything else that is currently popular.

What is the same between the web before and Web 2.0 (no one ever referred to Web 1.anything until the Web 2.0 marketing banner was raised) is that these technologies can be a huge benefit when implemented well against a solid design and massive headache if done wrong.

Not all of the technologies are mature yet, which is where the big push to use them can be beneficial. Why? Because as development teams run into the issues and limitations vendors will be pushed to fix them, which will accelerate their maturity.

IMHO 🙂

If you found this interesting, please share.

© Scott S. Nelson