I grinched my own Christmas

[Hawkmoon]

I've been chugging along way past the contract expiration with my trusty Samsung Galaxy S III cell phone from Verizon. I don't even remember when I got it -- at least six years ago, possibly closer to eight. Battery life seems to be deteriorating, so I decided to treat myself to an "upgrade" for Christmas. I've been happy with Samsung, and I don't need a lot of extras, so I went with a Galaxy J3 Eclipse model. It arrived on Saturday (ordered on-line because none in stock at local Verizon stores), wouldn't activate, so on Sunday I took it to a Verizon storefront in a mall and had it activated.

I think I set a new record. Less than four hours after activating it I was on-line with Verizon, having them switch me back to my old phone. Trying to use the new one was like landing on another planet. It's difficult to believe that it's the same phone manufacturer, and a newer version of the same operating system. I hated it. And that was before I realized that my contacts transferred over, but my messages didn't!

So the new phone is now the old phone, and it goes back as soon as Verizon sends me a return shipping label. It's already boxed up and ready to go.

Bah, humbug.

[Northwoods]

Luddite.

It's what you get for trying to skip something like 5 generations of technology in one go.

[Hawkmoon]

Luddite.

It's what you get for trying to skip something like 5 generations of technology in one go.

True.

Since I'm sending the former new phone back, with any luck I'll skip several more generations before I venture into the next "upgrade." What an oxymoron. The term "upgrade" suggests that the new product should be better. How is it an "upgrade" if I can't see the screen well enough to read it, it doesn't have some standard apps that I actually use, and the menu screens are all reorganized so I can't find anything? It's the same argument I have with Microsoft and the new, ribbon menu structure on Office (starting with Office 2007). It's not an improvement -- it's impossible to find how to do anything. Since my work switched from Office 2003 to Office 2010 my productivity has tanked. It wouldn't have been difficult for Microsoft to have included a toggle to allow the use of the old menu structure but, Noooo ... they want to force us all to use the new menus. Yet, despite the fact that it creates massive losses of productivity and required hours and hours of retraining, they characterized it as an "upgrade."

Bah, humbug!

[bedlamite]

[230RN]

"It's the same argument I have with Microsoft and the new, ribbon menu structure on Office (starting with Office 2007). It's not an improvement -- it's impossible to find how to do anything."

Well, see, you expected "improved."  All it improves is their bottom line.

Actually I think there is a toggle somewhere to revert to the classic style, but I lost where I found it.  That ribbon thing has rendered Win7 Paint almost inoperable.  Fortunately, there's a good old copy on my Dell with XP.  I have no idea what the guy who invented the ribbon system was smoking.

The irony is that even though the "ribbon" Win7 Paint has more functions, I can accomplish more with the old XP Paint.

It's like something I saw the other day:  "Spellchecker is my worst enema."

Terry, 230RN

[Hawkmoon]

The irony is that even though the "ribbon" Win7 Paint has more functions, I can accomplish more with the old XP Paint.

The old (XP) Paint runs under Windows 7. I have both on my computer, and I use the old one for almost everything. I did once find something that was easy in the new paint that I couldn't do in the old one, but that was so long ago that I can't remember what it was.

[Jocassee]

I'm scared to ask what yall are using Paint for.

[Hawkmoon]

Painting, of course.

:duh:

[charby]

I'm scared to ask what yall are using Paint for.

No kidding with all the free better stuff out there.

[mtnbkr]

No kidding with all the free better stuff out there.

But it's different...

Chris

[Jamisjockey]

I'm betting this is your "old phone"
https://youtu.be/5MCrfXDiQWs

[charby]

But it's different...

Chris

and scary

[230RN]

Not scary, just a time sink.  Someone remarked about skipping five generations of advances (Eeek) but let's look at it this way.

You buy some software a couple of years ago, it does what you want, you get fluent with it, you can get your stuff done without looking up help every time a function is needed, and you go ahead and "accomplish" for those couple of years.  In the meantime, the "latest and greatest" "new product = new profit" "cutting edge of technology" juggernaut proceeds in its unstoppable way.

You finally get to the point where you're seduced into a "five generations" ahead of  you package, and the "seduction" is due to the fact that the mfr no longer supports the old stuff and you have to buy the new stuff.  Yay, profit !

And instead of producing what you used to produce faciley and fluently, you have to stop to find out how to do what you used to do faciley and fluently.

Time.

Time sink.

See...  It's not a game I play.  It's a tool I use.

Terry  

[mtnbkr]

It's not a game I play.  It's a tool I use.

I like how you insinuated those of us not all torn up by software changes are just playing games or not using it for serious work.

See...I've worked in the IT field in one form or another for over 20 years.  Software changes are a part of life, so I don't get bitched up over them.  More importantly to me is the security issues around those apps or the ability to share data with users of older or newer versions. 

When MS introduced the Ribbon in Office, I was annoyed at it for about a week, but since it wasn't likely to go away, I adjusted and found out it was a net benefit to my workflow once I stopped clinging to the old menu system.  I actually started noticing and using features in Word, Excel, etc, due to the Ribbon.

If cosmetic changes in user applications are enough to have you clutching your pearls, you should see what changes come to the professionals in enterprise systems and the like. 

Chris

[Hawkmoon]

I'm betting this is your "old phone"
https://youtu.be/5MCrfXDiQWs

Not quite. It's a Samsung Galaxy S III.

But my first "portable" phone was a Radio Shack "bag phone" ...

[mtnbkr]

Not quite. It's a Samsung Galaxy S III.

But my first "portable" phone was a Radio Shack "bag phone" ...

So was my wife's.  She managed to adapt to and learn how to use an iPhone 5 though.

Chris

[charby]

I like how you insinuated those of us not all torn up by software changes are just playing games or not using it for serious work.

See...I've worked in the IT field in one form or another for over 20 years.  Software changes are a part of life, so I don't get bitched up over them.  More importantly to me is the security issues around those apps or the ability to share data with users of older or newer versions.  

When MS introduced the Ribbon in Office, I was annoyed at it for about a week, but since it wasn't likely to go away, I adjusted and found out it was a net benefit to my workflow once I stopped clinging to the old menu system.  I actually started noticing and using features in Word, Excel, etc, due to the Ribbon.

If cosmetic changes in user applications are enough to have you clutching your pearls, you should see what changes come to the professionals in enterprise systems and the like.  

Chris

I also worked IT for close to 20 years before switching careers to something totally different.

Towards the end of my IT career I was doing autonomous enterprise silent installs for both Windows and Mac. You learned to not like anything for very long because as soon as you did a new version came out, it was usually a steep learning curve but the new functionality kicked ass.

[HeroHog]

Not quite. It's a Samsung Galaxy S III.

But my first "portable" phone was a Radio Shack "bag phone" ...

Us too! Good phone, lots of power.

[bedlamite]

[230RN]

I like how you insinuated those of us not all torn up by software changes are just playing games or not using it for serious work.

See...I've worked in the IT field in one form or another for over 20 years.  Software changes are a part of life, so I don't get bitched up over them.  More importantly to me is the security issues around those apps or the ability to share data with users of older or newer versions. 

When MS introduced the Ribbon in Office, I was annoyed at it for about a week, but since it wasn't likely to go away, I adjusted and found out it was a net benefit to my workflow once I stopped clinging to the old menu system.  I actually started noticing and using features in Word, Excel, etc, due to the Ribbon.

If cosmetic changes in user applications are enough to have you clutching your pearls, you should see what changes come to the professionals in enterprise systems and the like. 

Chris

If I may make a smart-assed remark, may I gently suggest that folks who work in IT are not qualified to comment on this issue...

"I was annoyed at it for about a week... "

Yup.  Time.  Like I said.  Time.

Terry

[mtnbkr]

If I may make a smart-assed remark, may I gently suggest that folks who work in IT are not qualified to comment on this issue...

Because IT practitioners are mages and have otherworldly grasp of technology.

Or...

We realized long ago not to get attached to a specific version or feature and just get on with out lives because change happens.  It's more productive to accept it and move on.  Time, remember?

"I was annoyed at it for about a week... "

Yup.  Time.  Like I said.  Time.

Terry

Nope.  That was the emotional response.  In your quote cherry-picking, you left out where I ultimately found it more productive than the previous menuing system.

Look, software is still evolving.  Change happens and will keep happening.  If you don't want change, don't upgrade.  Stick with what is comfortable for you.  It's not advisable from a security or interoperability perspective, but it'll reduce your stress levels.  If you're unhappy with commercial software, give open source a try.  Don't get too hung up on a feature or version there either because open source changes as well.

Typewriters are fundamentally unchanged for a few decades now.  You might consider that as an alternative (they are experiencing a bit of a renaissance). 

Chris

[K Frame]

"Because IT practitioners are mages and have otherworldly grasp of technology."

Nah, you're just geeky bastards who can't communicate well with anything other than a motherboard and soldering iron.

[mtnbkr]

I also worked IT for close to 20 years before switching careers to something totally different.

Towards the end of my IT career I was doing autonomous enterprise silent installs for both Windows and Mac. You learned to like anything for very long because as soon as you did a new version came out, it was usually a steep learning curve but the new functionality kicked ass.

All my work these days is with the people side of IT services.  I build stuff with human beings and processes.  :)

Prior to last summer, I managed a security service.  One of the teams reporting to me was a systems development team.  The wailing and gnashing of teeth over systemd  was amusing and annoying (there were a few who did not handle change well), but since it was unavoidable, they eventually got on with it.  Having since moved onto service design*, they don't report to me any longer, but I understand they're all sorted out and comfortable with the new system.

*Getting out of Operations was the best thing I've done in a long time.

Chris

[mtnbkr]

"Because IT practitioners are mages and have otherworldly grasp of technology."

Nah, you're just geeky bastards who can't communicate well with anything other than a motherboard and soldering iron.

I have transcended physical IT and now cast spells using people and processes.  Begone before I redefine your role and move it to a lower cost economy!

Chris

[K Frame]

I have transcended physical IT and now cast spells using people and processes.  Begone before I redefine your role and move it to a lower cost economy!

Chris

I'm betting that the only thing you've transcended is another notch in your belt given Michelle's normal Christmas food output...