Service Provider Cloud

SlideshowCal Poly 'Leapfrogs' Into the Future With Cloud

Page 1 / 2   >   >>
Michelle 7/8/2017 | 2:44:09 PM
Re: Sounds like a no-brainer... All this talk of legacy code and clinging to old ways makes me wonder how old is TOO OLD for this code? At what point is it no longer worth keeping? I wonder if there will soon be a market for very talented developers who can migrate old function to new languages. The projects would be massive, I imagine.
JohnMason 7/7/2017 | 3:25:35 AM
Re: Amazon's commodes Actually ran into the problem of water from toilets leading into a computer room. Meant a quick move (or as quick as we could make it).
kq4ym 7/6/2017 | 11:29:26 AM
Re: Sounds like a no-brainer... It looks like Cal Poly was in kind of between the rocka and a hard place, not to mention under the bathroom as well. To consider the choice that a "new data center would cost about $8 million," and head to the cloud probably make it a fairly easy choice to go with AWS in this case. Maybe not so easy for other situations though.
Joe Stanganelli 7/4/2017 | 5:50:14 PM
Re: Sounds like a no-brainer... @Michelle: In the old days (although, possibly, to a lesser extent, even today), dense legacy code was one's form of job security. Good luck figuring out your systems if you fire one of your key IT guys or devs.
Joe Stanganelli 7/4/2017 | 5:49:19 PM
Re: Sounds like a no-brainer... @mhh: Oh, yes, I was familiar with the 2038 issue...The problem is most likely to impact vehicles and IoT, it appears.

We probably should be hyping that one up more than we are. But, then, it's not like people were thinking much about the Y2K bug in 1979.
Michelle 7/3/2017 | 8:58:00 PM
Re: Sounds like a no-brainer... Yeah, I have to admit I can't quite identify with these folks. I have read some crazy stories about supporting legacy code so I can imagine they've got something they really like on those server (and they don't want to rewrite it).
mhhfive 7/3/2017 | 8:41:54 PM
Re: Sounds like a no-brainer... > "If you have a thick bureaucracy and a poor culture .."

Yup. However, sometimes taking a long time to decide isn't as bad as consultants might think. A long process sometimes surfaces issues that might not have come up with a quick "my way or the highway" decision.... But generally, yes, a company that takes an unduly long time to decide something that shouldn't be too difficult.. is doomed in the long run.
mhhfive 7/3/2017 | 8:29:08 PM
Re: Sounds like a no-brainer... > "Maybe after the Y10K problem is solved."

There's actually a Year 2038 problem that'll happen before that...


Or maybe we should go back to relying on purely mechanical clocks:

Joe Stanganelli 7/2/2017 | 12:28:55 AM
Re: Sounds like a no-brainer... @mhh: Sadly, these processes that take that long for decision-making are what is killing legacy businesses far more than their actual technology choices. If you have a thick bureaucracy and a poor culture and you need to get a dozen signatures on a piece of paper to get something done, you have problems that the cloud just can't solve -- and those problems will prevent you from realizing the full power of the agility that the cloud has to offer (let alone solve your complexity problems).

In other words, the hammer isn't going to do you any good if you keep insisting on hitting yourself on the thumb.
Joe Stanganelli 7/2/2017 | 12:26:10 AM
Re: Amazon's commodes @John: ...Talk about data wiping!


...I'll show myself out.
Page 1 / 2   >   >>
Sign In