SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


The Five Year Plan


The Five Year Plan

Author
Message
Gary Varga
Gary Varga
SSCoach
SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)

Group: General Forum Members
Points: 16130 Visits: 6531
David.Poole (6/13/2013)
In short, IT will still exist in 5 years time, 25% will have gone, 50% will stay the same, 25% will be brand new and unimagined today.


I know that I am being pedantic but surely one 25% is replacing the other so that totals to 75%.

I get your point though and totally agree.

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Michael Valentine Jones
Michael Valentine Jones
SSCertifiable
SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)

Group: General Forum Members
Points: 5686 Visits: 11771
New technology does not mean the old technology is going away. Technology has a purpose, and only goes away when its utility goes away.

I read somewhere that there are more horses in the US now than there were a hundred years ago, so the automobile never quite eliminated horses.

Even punched cards are still in use in some applications, and many file formats standards are still in use that were based on punched cards, with the 80 column format still alive in terminals and the default column width for the Windows command shell.

Nine track reel to reel tapes did finally go away, but production did not end until 2001 and the last drive was shipped in 2003. However, newer forms of tapes and drives are still widely used for backups.

I have a friend with a small non-technology business, and he has two employees out of twenty who are dedicated to IT. He didn’t plan to have an IT department that was 10% of his workforce, but it happened and he feels he needs them.

So the death of IT departments may not be as imminent at the predictions. They will disappear only when they no longer have any value.
Gary Varga
Gary Varga
SSCoach
SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)

Group: General Forum Members
Points: 16130 Visits: 6531
I would have to agree with many of the comments here, particularly Michael Valentine Jones', as decades on and I still get involved in creating enterprise systems from department cobbled ones e.g. their use of Excel, Access or even far more professional attempts.

In the end, if a system is mission critical to a company or nearly that important then the nonfunctional aspects that the IT department brings (redundancy, disaster recovery, etc.) are essential and something that departments rarely implement to that satisfaction of the board.

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
GeorgeCopeland
GeorgeCopeland
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1097 Visits: 849
The IT helpdesk will go away about the time that the sun goes nova.
ccd3000
ccd3000
SSC Veteran
SSC Veteran (210 reputation)SSC Veteran (210 reputation)SSC Veteran (210 reputation)SSC Veteran (210 reputation)SSC Veteran (210 reputation)SSC Veteran (210 reputation)SSC Veteran (210 reputation)SSC Veteran (210 reputation)

Group: General Forum Members
Points: 210 Visits: 768
I think the author is a better salesperson and self-promoter than a prognosticator. For one, IT departments are organizational constructs no matter the current technology they employ and process is central to an efficient IT operation, especially the bigger ones. This is simple puffery.
Jim P.
Jim P.
SSC Eights!
SSC Eights! (897 reputation)SSC Eights! (897 reputation)SSC Eights! (897 reputation)SSC Eights! (897 reputation)SSC Eights! (897 reputation)SSC Eights! (897 reputation)SSC Eights! (897 reputation)SSC Eights! (897 reputation)

Group: General Forum Members
Points: 897 Visits: 2215
David.Poole (6/13/2013)
Anyone starting today would be shocked by what their predecessors had to to to fight with the early versions of MFC. The sheer amount of code that was necessary to produce a simple Windows form was shocking. Today its drag and drop, set a few properties and fill in the bit that actually delivers value to the business. Back then it was work out how to get windows to resize and redraw correctly, controls to respond to events.


And I have lost count how many times I've had to essentially rebuild an Access DB for some department that went ahead and used the form wizards and macros to build their database. They only came to IT when it started so acting up and slowing down.

Then you find there is no normalization and the auto-generated code is just a huge waste of time.



----------------
Jim P.

A little bit of this and a little byte of that can cause bloatware.
scott mcnitt
scott mcnitt
SSC-Enthusiastic
SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)

Group: General Forum Members
Points: 100 Visits: 436
Jim P. (6/13/2013)
David.Poole (6/13/2013)
Anyone starting today would be shocked by what their predecessors had to to to fight with the early versions of MFC. The sheer amount of code that was necessary to produce a simple Windows form was shocking. Today its drag and drop, set a few properties and fill in the bit that actually delivers value to the business. Back then it was work out how to get windows to resize and redraw correctly, controls to respond to events.


And I have lost count how many times I've had to essentially rebuild an Access DB for some department that went ahead and used the form wizards and macros to build their database. They only came to IT when it started so acting up and slowing down.

Then you find there is no normalization and the auto-generated code is just a huge waste of time.


But the answer should not be to take away the ability of the Business to create its own technical solutions (prevent them from creating MS Access databases) but rather to prevent them from creating mission critical solutions under the radar with no long-term plan to move them "into the fold".

I think the point of this Editorial and the article from Infoworld is that the Business needs to get things done and sometimes their need for a solution does not fit into the traditional IT solution process. It realizes that each need fits on a continuum from "Slow but Sure" for IT to "Seat of the Pants" for non-IT.

Sometimes it needs to be done NOW (create this report for the customer by tomorrow or lose the contract) and the scope and risk are such that a quick solution in MS Access is a good fit...for now.

I don't think traditional IT will completely go away but the companies that do not embrace the issue of Shadow IT may find themselves out of business.
batgirl
batgirl
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1705 Visits: 1820
djackson 22568 (6/13/2013)
We need to remember that these people get paid to make predictions, not to be right. Maybe one day the C-Suites of the world will recognize that these predictions are being made by idiots.

Other predictions made in my life that were just as bad, if not worse:

We will run out of oil by 1980 1990 2000 2010 2020
Code generation tools will replace programmers by 1990 2000 2010 2020
Amnesty will end illegal immigration
Teaching (abstinence/sex ed) will put an end to teenage pregnancy
Hope and change
I will be rich by age 25

OK, the last one is true, I did meet and marry my better half, and she makes me feel rich!


Don't forget the ever popular Social Security will run out of cash by 1975 1976 1977 1978and every year since
David.Poole
David.Poole
SSCertifiable
SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)

Group: General Forum Members
Points: 7449 Visits: 3279
Gary Varga (6/13/2013)
David.Poole (6/13/2013)
In short, IT will still exist in 5 years time, 25% will have gone, 50% will stay the same, 25% will be brand new and unimagined today.


I know that I am being pedantic but surely one 25% is replacing the other so that totals to 75%.

I get your point though and totally agree.


Some of us will be retired/downsized or pursuing other opportunitiesw00t

LinkedIn Profile

Newbie on www.simple-talk.com
Gary Varga
Gary Varga
SSCoach
SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)

Group: General Forum Members
Points: 16130 Visits: 6531
scott mcnitt (6/13/2013)
Jim P. (6/13/2013)
David.Poole (6/13/2013)
Anyone starting today would be shocked by what their predecessors had to to to fight with the early versions of MFC. The sheer amount of code that was necessary to produce a simple Windows form was shocking. Today its drag and drop, set a few properties and fill in the bit that actually delivers value to the business. Back then it was work out how to get windows to resize and redraw correctly, controls to respond to events.


And I have lost count how many times I've had to essentially rebuild an Access DB for some department that went ahead and used the form wizards and macros to build their database. They only came to IT when it started so acting up and slowing down.

Then you find there is no normalization and the auto-generated code is just a huge waste of time.


But the answer should not be to take away the ability of the Business to create its own technical solutions (prevent them from creating MS Access databases) but rather to prevent them from creating mission critical solutions under the radar with no long-term plan to move them "into the fold".

I think the point of this Editorial and the article from Infoworld is that the Business needs to get things done and sometimes their need for a solution does not fit into the traditional IT solution process. It realizes that each need fits on a continuum from "Slow but Sure" for IT to "Seat of the Pants" for non-IT.

Sometimes it needs to be done NOW (create this report for the customer by tomorrow or lose the contract) and the scope and risk are such that a quick solution in MS Access is a good fit...for now.

I don't think traditional IT will completely go away but the companies that do not embrace the issue of Shadow IT may find themselves out of business.


Departments developing their own poor (technically) but useful (business-wise) solutions is the ultimate in agility and prototyping. I just wish that they would recognise to call in their IT departments when it starts to become a problem as opposed to waiting until it no longer is viable and need the replacement from the IT department immediately.

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search