“There is No Climate Emergency”

[Rotadom]

Al still sweating that too?

Y2K was a conservative conspiracy because they don't understand how computers work.

 

[BabyBoomer50s]

Y2K was a conservative conspiracy because they don't understand how computers work.

IT managers at large corporations and government agencies spent boatloads of money on software and services. The big systems integrators like Deloitte and PWC made a fortune. The computer industry press was saturated with doom and gloom stories and marketing people at tech companies worked overtime coming up with ways to frame their products as the only hope for survival. Crazy days.

 

[ll74]

IT managers at large corporations and government agencies spent boatloads of money on software and services. The big systems integrators like Deloitte and PWC made a fortune. The computer industry press was saturated with doom and gloom stories and marketing people at tech companies worked overtime coming up with ways to frame their products as the only hope for survival. Crazy days.

They made a lot of money because early programmers didn't know what the fuck they were doing. Companies that didn't fix their shit, had their shit break.

 

[BabyBoomer50s]

They made a lot of money because early programmers didn't know what the fuck they were doing. Companies that didn't fix their shit, had their shit break.

Part of the issue, especially for big banks and large government agencies, was that many of their mission critical apps were written in COBOL decades earlier. Source code management tools and processes were primitive, institutional knowledge about patches built upon patches over the years had faded, and very few COBOL programmers were left in the US workforce by the 90s. Lots of ongoing system maintenance was done by programmers from Russia and other Eastern European countries.

 

[ll74]

Part of the issue, especially for big banks and large government agencies, was that many of their mission critical apps were written in COBOL decades earlier. Source code management tools and processes were primitive, institutional knowledge about patches built upon patches over the years had faded, and very few COBOL programmers were left in the US workforce by the 90s. Lots of ongoing system maintenance was done by programmers from Russia and other Eastern European countries.

Yes, early programmers didn't know what they were doing. Companies that didn't fix their.shit had their shit break.

Thanks for confirming.

 

[BabyBoomer50s]

Yes, early programmers didn't know what they were doing. Companies that didn't fix their.shit had their shit break.

Thanks for confirming.

They probably knew what they were doing but didn’t know where they were going. They earliest programs were built upon hierarchical databases to perform simple tabulations of what they thought were large numbers of records. Over time, new capabilities were required which meant more row and columns, more sophisticated calculations, time series formulas, and on and on. Stuff the original app designers and programmers never imagined. Just how computer generations rise and fall. From the mainframe age to mini computers to client server computing to the web to virtualization to the cloud, etc. Discovery of new possibilities makes things break and become obsolete.

 

[ll74]

They probably knew what they were doing but didn’t know where they were going. They earliest programs were built upon hierarchical databases to perform simple tabulations of what they thought were large numbers of records. Over time, new capabilities were required which meant more row and columns, more sophisticated calculations, time series formulas, and on and on. Stuff the original app designers and programmers never imagined. Just how computer generations rise and fall. From the mainframe age to mini computers to client server computing to the web to virtualization to the cloud, etc. Discovery of new possibilities makes things break and become obsolete.

They didn't plan for the future. I e. They didn't know what they were doing because they failed to plan their languages properly. Make excuses al you want ...they were the problem...not the companies hired to fix their fuckup

 

[BabyBoomer50s]

They didn't plan for the future. I e. They didn't know what they were doing because they failed to plan their languages properly. Make excuses al you want ...they were the problem...not the companies hired to fix their fuckup

Not making excuses or blaming anyone. It’s just how computer languages and architectures evolve. Spent 35 + years in the industry and have seen these cycles unfold.

 

[ll74]

Not making excuses or blaming anyone. It’s just how computer languages and architectures evolve. Spent 35 + years in the industry and have seen these cycles unfold.

Awesome. I'm still in the industry and saw first-hand companies bottom out trying to recover from their lack of investment to fix the issue.

Your insinuation was that companies took advantage of something that was over hyped. Since you know it wasn't, I'll assume it wasn't intended then.

 

[schism666]

babbydoodoo is another one who if you let them type long enough, they blowup their own point.

 

[BabyBoomer50s]

Awesome. I'm still in the industry and saw first-hand companies bottom out trying to recover from their lack of investment to fix the issue.

Your insinuation was that companies took advantage of something that was over hyped. Since you know it wasn't, I'll assume it wasn't intended then.

The software and services companies that profited from Y2K delivered valuable products that addressed real needs. I worked for one in the late 90s. And yes, the issue was hyped by the IT press and by marketing departments across the industry. Hype waves come and go in the tech industry. New innovations and new business problems come along and everyone wants to catch the wave. If you want a really good example of IT people creating train wrecks by not knowing wtf they were doing, look at SAP implementations done in the 90s and early 2000s.

 

[ll74]

The software and services companies that profited from Y2K delivered valuable products that addressed real needs. I worked for one in the late 90s. And yes, the issue was hyped by the IT press and by marketing departments across the industry. Hype waves come and go in the tech industry. New innovations and new business problems come along and everyone wants to catch the wave. If you want a really good example of IT people creating train wrecks by not knowing wtf they were doing, look at SAP implementations done in the 90s and early 2000s.

It was hyped because it was needing to be hyped.

Y2K is nothing like over hyped software, such as SAP.

 

[Rightguide]

Right-wingers (unlike Rightguide) believe in small government and low taxes. That doesn't mean they are stupid or uncritical of people who post right-wing conspiracy theories.

Being right-wing is a political choice, a valid one.

You can be right-wing and intelligent. Or you can be right-wing as Rightguide claims to be, and completely fooled by propaganda that shows right-wingers to be stupid.

People like Rightguide do more damage to the Republican party than even the Jan 6 rioters. But Rightguide can't see that. His version of 'facts' makes right-wingers appear to be complete nutcases. They're not but Rightguide is.

Here's a fact for you, the crazed moon-barking zealots who appointed themselves as saviors of the World all flew into Davos on over 1000 private jets to demand the rest of us consume less.

 

[Caseygrl24]

Oops bit the wrong button. Sorry.

 

[HisArpy]

Oops bit the wrong button. Sorry.

That's ok, some people like it when you bite their button.

 

[Caseygrl24]

That's ok, some people like it when you bite their button.

 

[phrodeau]

Here's a fact for you, the crazed moon-barking zealots who appointed themselves as saviors of the World all flew into Davos on over 1000 private jets to demand the rest of us consume less.

I’m searching your post for a fact, but I don’t see one. What makes you think that consuming less is anybody’s demand?