Comments on: Why Choosing the Right Technology Matters http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/ The blog that helps you build great software Sun, 20 Jul 2008 01:51:50 +0000 http://wordpress.org/?v=MU By: Arjan`s World » LINKBLOG for June 28, 2008 http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/#comment-379 Arjan`s World » LINKBLOG for June 28, 2008 Sat, 28 Jun 2008 20:00:19 +0000 http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/#comment-379 [...] Why Choosing the Right Technology Matters - Hamid Shojaee Hamid makes some good points why the technology you choose for your project does indeed matter [...] [...] Why Choosing the Right Technology Matters - Hamid Shojaee Hamid makes some good points why the technology you choose for your project does indeed matter [...]

]]> By: Giancarlo Frison http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/#comment-373 Giancarlo Frison Fri, 27 Jun 2008 09:14:35 +0000 http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/#comment-373 I would add also the audience and the developing entourage of such a technology you choose. In past experiences I apply this rule for choosing frameworks with more chance to be carried forward in terms of developers number and users. I would add also the audience and the developing entourage of such a technology you choose.
In past experiences I apply this rule for choosing frameworks with more chance to be carried forward in terms of developers number and users.

]]> By: chin http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/#comment-283 chin Wed, 09 Apr 2008 03:49:52 +0000 http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/#comment-283 . If the product is good, the users don’t care if it’s written in Java, C# or Cobol. From the above excerpt in your blog, did you mean C++? . If the product is good, the users don’t care if it’s written in Java, C# or Cobol.

From the above excerpt in your blog, did you mean C++?

]]> By: Tom http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/#comment-197 Tom Wed, 30 Jan 2008 19:52:53 +0000 http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/#comment-197 Notice that, contrary to the first few paragraphs of the post, the selection of technology really can matter to product end-users. When engaged in product selection, there are some decision-makers who will limit their search to LAMP-based products. They don't even consider or evaluate MSFT platform products. To an extent when you're choosing the underlying technology you are most likely choosing the size of the market you can sell to. Choosing a technology for its ability to attract the right talent is also a bit of a thorny issue. For example, what do you do with the very talented people you have when the latest programming language shifts away from the one you're using? Do you send your C++ programmers to become greeters at WalMart because Java has taken over? Is this what it means to attract the "right talent that can get the job done"? If the technology shifts faster than the human beings (let's assume that they remain very talented people), what do you do with those human beings? And what do these choices tell you about your hiring practices in the first place? ("I'm not interested in a talented C++ person regardless of his track record for execution because he only has 1 year developing with Java...") These aren't always easy questions to answer well. Notice that, contrary to the first few paragraphs of the post, the selection of technology really can matter to product end-users.

When engaged in product selection, there are some decision-makers who will limit their search to LAMP-based products. They don’t even consider or evaluate MSFT platform products.

To an extent when you’re choosing the underlying technology you are most likely choosing the size of the market you can sell to.

Choosing a technology for its ability to attract the right talent is also a bit of a thorny issue.

For example, what do you do with the very talented people you have when the latest programming language shifts away from the one you’re using?

Do you send your C++ programmers to become greeters at WalMart because Java has taken over? Is this what it means to attract the “right talent
that can get the job done”?

If the technology shifts faster than the human beings (let’s assume that they remain very talented people), what do you do with those human beings?

And what do these choices tell you about your hiring practices in the first place? (”I’m not interested in a talented C++ person regardless of his track record for execution because he only has 1 year developing with Java…”)

These aren’t always easy questions to answer well.

]]> By: Krator http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/#comment-126 Krator Sun, 13 Jan 2008 00:59:37 +0000 http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/#comment-126 I totally agree with this article. Knowing your target audience by picking a set of technologies aligns you with a certain perspective. Some companies are 100% Microsoft shops while others are 100% the other way. Companies try to align technologies, even if the applications are bought, to try and minimize their support costs. Who would want to learn the intricacies of 10 different programming languages or even worse databases. Could you image trying to support SQL Server, Oracle, DB2, MySql, Progress, Reality, PostgreSQL, etc... The idea of creating something that is Standards based is a myth. An IT Standard is nothing more than a guideline. As new technologies come out the "Standard" shifts to reflect the changes in procedures. I totally agree with this article. Knowing your target audience by picking a set of technologies aligns you with a certain perspective. Some companies are 100% Microsoft shops while others are 100% the other way. Companies try to align technologies, even if the applications are bought, to try and minimize their support costs. Who would want to learn the intricacies of 10 different programming languages or even worse databases. Could you image trying to support SQL Server, Oracle, DB2, MySql, Progress, Reality, PostgreSQL, etc…

The idea of creating something that is Standards based is a myth. An IT Standard is nothing more than a guideline. As new technologies come out the “Standard” shifts to reflect the changes in procedures.

]]> By: pcdinh http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/#comment-118 pcdinh Fri, 11 Jan 2008 12:48:45 +0000 http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/#comment-118 Does it mean that your product is for Windows only and it is not standard-based? Does it mean that your product is for Windows only and it is not standard-based?

]]> By: ChrisVB http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/#comment-109 ChrisVB Thu, 10 Jan 2008 11:47:38 +0000 http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/#comment-109 I see one problem or contradiction here: what is attracting the right talent now, may make it leaving in the future. You say "developers often leave their jobs just to use newer, more exciting technologies", so how are you going to keep the devs from leaving when some other new technology comes along? If you also will use those new technologies, Future Support and even Code Maintenance is not as important anymore. If you don't, you will lose on number 1 Attracting the right talent. Remember, once devs where also hailing C as the newer, more exciting technology! That's why working in a startup is so exciting: for a short time you can have it all. But after a while you will have to join the legions and have to make sacrifices... I see one problem or contradiction here: what is attracting the right talent now, may make it leaving in the future.

You say “developers often leave their jobs just to use newer, more exciting technologies”, so how are you going to keep the devs from leaving when some other new technology comes along?
If you also will use those new technologies, Future Support and even Code Maintenance is not as important anymore.
If you don’t, you will lose on number 1 Attracting the right talent.

Remember, once devs where also hailing C as the newer, more exciting technology!

That’s why working in a startup is so exciting: for a short time you can have it all. But after a while you will have to join the legions and have to make sacrifices…

]]> By: Anonymous http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/#comment-55 Anonymous Mon, 31 Dec 2007 20:36:54 +0000 http://shipsoftwareontime.com/2007/12/31/why-choosing-the-right-technology-matters/#comment-55 So does that mean you guys will be soon upgrading to SQL 2008 and Visual Studio 2008? So does that mean you guys will be soon upgrading to SQL 2008 and Visual Studio 2008?

]]>