Technology

The Wasteful Efficiency of the Large

by

(This column is posted at www.StevenSavage.com, Steve’s Tumblr, and Pillowfort.  Find out more at my newsletter, and all my social media at my linktr.ee)

I’ve been thinking of large, easy-to-deploy, fast-to-scale solutions can be an inefficient waste of time. Before I go into my inevitable rant-o-speculation, let me note the origin – Chinese history and Agile. Trust me, it’s worth it.

As to Chinese History, I’ve had a deep interest in the Taoists and because of that some of Chinese history and culture. The Taoists provide a body of philosophy, meditation, and sarcastic humor while focusing on simplicity, uncomplicated-ness, and a kind of mystical realism. Chinese History is replete with scholar-bureaucrats whom I deeply relate to because I’m me. This means I can read about a figure who is essentially “He was in the Department of Awesome Flowcharts and a famous Taoist scholar” and go “yeah, this dude rocks.”

Early on in philosophical Taoism there’s an emphasis on frugality, not-over reaching, and taking care of things while small. Arguably the “journey of a thousand miles begins with a single step” originated in the Tao Te Ching (Chapter 64). If you focus on small things before they’re large and not overdoing it, you get a lot done without, well, doing a lot.

Now does this sound like Agile? Well now you can see where this comes in . . . and learn even more about my personality. I love Agile’s focus on small, meaningful incremental change. The tenth Agile principle even states success is what you don’t have to do. Well done Agile Projects do what is needed, no more, and thus get a lot done – and even save time by not overdoing things.

By now if you know me, you can see where this is going in the world of IT solutions, so thanks for humoring my above explanation. Now let me rant about discussions I have with my friends in IT which is . . . most of them.

Back in my day (hey, I’ve been in IT 30 years) I saw a lot of custom IT systems. I built them. Whatever you needed for your specific needs might not have an off-the-shelf solution, and if it existed it was large and expensive. So when you had to make something custom you learned the issue, solved the solution, then watched your code decay for ten years after getting a promotion. Maintenance was an issue, but at least it was small.

(Software is an expense, talent is the investment.)

In time people of course made solutions that were scalable, that were customizable, that built on layers and layers of code over the decades. We took advantage of cloud computing, of distribution systems. Any large provider of services can instantly set up your small business because of years of investment.

You can implement the same solution as the big guys, or customize a solution . . .

. . . except everything is now all so large.

You just bought, say, an infrastructure tracking tool. Sure it’s on the cloud, but only runs in this one browser. Also you have to figure which modules to activate. You have to train your team. You also have a lot of features you may not need, but everyone wants them as they’re there and easy to use (for the people who want them). You may not have to maintain the system, but you have to get everyone on board something they never participated in making and isn’t based on your specific needs.

Oh, and as soon as a certain web security company who’s name sounds like “Clown Strife” goes under your inventory system is unreachable. Well, also half your other systems are too, but I digress because I still flash back to that outage.

Now you’re using all of this stuff to ease paperwork while creating more paperwork. You are probably entering data you don’t need but it was one of the features. You now have to reconcile the new system with the old system, which is months of work and means you need a consultant. You’re trying to get everyone aligned on something that you basically dropped on them and they make workarounds.

I have met people who were still solving problems with spreadsheets because the applications didn’t work. I have been those people.

You quickly and efficiency implemented a big solution that doesn’t quite work and thus you make more work and waste more time. You have small issues to solve and maybe if you solved them first you wouldn’t be here. Plus maybe you had no gain once all the overhead is taken account of.

All that new work you added may be worse than the janky old system – and you can’t tell.

Right now in technology we can implement huge, powerful solutions easily with no concept of the small picture that makes them work. We don’t even know if they serve the small picture as the “Big Thing” becomes paramount. You can buy a solution and not solve anything and may not know.

Maybe it was worth it slowly maintaining and upgrading the system you had. Or having done it right in the first place. B Or a piecemeal migration.

This is a reminder of Agile, of the Taoists, all having a point. Solutions are often about the small things, about working on something before it’s large, of doing what’s needed – and not letting things grow into a problem. I think in the world of IT we’ve accumulated so much tech, so many solutions it’s easy to just throw a Big Thing at a problem. That may not solve the problem, it may make more of them.

There are situations that need bottom-up implementation and that’s a lot of them. Yes, you might be able to use a Big Solution, but only after you get what you need, and probably do it incrementally. You have to address the small to fix the big, not throw the Big at whatever else is Big and hope.

Also let’s face it, sometimes we get Big Solutions because we let something get out of hand and hope it’ll fix it. We forgot the lesson of starting small then repeat it.

Think small. It’s the way to do big things right as opposed to just doing a Big Thing and hoping.

Steven Savage

Alternate Steves: Conference Call

by

(This column is posted at www.StevenSavage.com, Steve’s Tumblr, and Pillowfort.  Find out more at my newsletter, and all my social media at my linktr.ee)

More on Alternate Histories through the eyes of Alternate Me’s. This comes from some past speculations on the internet, useful technologies, and vital functionality. In this case I wonder how conference calls/party lines could have been more widespread, giving us casual group chat long before Zoom, Teams, and so on.

Let’s meet an Alternate Steve who remembers the Conference Call Boom of the 80s and 90s . . . even if he missed the start.

I’m going to confess – I missed out on the Party Line/Conference Line craze when I was younger. Yes, I know, this is me, I’m the guy that has set up conferences. But Back In The Day it just didn’t register for me until I graduated college.

So anyway, let’s talk me in the 1990s. I’ve graduated from college and pending getting into graduate school, ended up working as an admin in an anthropology department. Pretty good gig and I figured I’d eventually go back to school to get into that PHD program. As you know I didn’t (even if I did get two more degrees).

One of the things people were talking about is Conference Calls, though everyone kept calling them Party Lines, an older name for shared phone lines. I think it honestly stuck because the term also got used by sex lines and so on. Boy did I work to call it “Conference Call,” and boy did people embarrass themselves throughout the early 90s.

Anyway at the time, I vaguely knew about Conference Calls and we all know the drill – people call one number or someone calls them and you all chat at once. It’s very standard now, but it exploded in the 80s and 90s – in ways that made perfect sense when you look back.

And in 1990 boy did I have to look back. I’m there in the office, suddenly having to catch up on all of this stuff that passed me by as I was A) in the dorms, and B) a computer guy.. I still remember sitting out a weekend with some of my co-workers to understand what was going on. And how I missed it.

You have to remember the 80s saw a lot of changes in communication. The Bell system got broken up. Compuserve and AOL were becoming noticeable. People met on internet forums in academic areas. And what happens when you’re a suddenly-regional phone company after a big breakup and you have a vision or just want money?

People are using computers to talk. But you are used to phones. So by pushing conference lines you sell phones, sell services, and get a leap on these growing services. Also some bigwigs use conference calls and you see them in movies. It was kind of a slam dunk, moreso in the business-obsessed 80s.

A lot of people claim to be the brains behind the Conference Call revolution, but I think it was more a thing of the time – everything came together. Certainly it did for us there in the office as we had PHDs and scientists who were MORE and more interested in figuring how to chat with each other without having to travel. I mean trust me, they wanted to travel (I had to do some of the billing), but you can’t rush back to the lab or something then.

Anyway all that happened while I was busy getting my degree and I only paid attention when I had to. I mean it moved slower than people make it sound because there was a lot of technical stuff, but to me it seemed fast. It had changed over four years.

So I kept learning.

Of course the Conference Call thing began creeping into many aspects of life and nerds like me were there on top of it. Sure they got pitched to business, then families, but I remember when TTRPG (Table Top RPG) was jokingly called Telephone Time RPG. Then there were writer’s roundtables, etc. Or the time I attended the Atlanta Fantasy Fair and someone did a panel by conference line, and that’s when things were definitely in full swing.

Am I saying that Conference Calls exploded even more because of enormous nerdery? Honestly, I kind of am.

I ended up staying on top of it way more than most because I worked in admin and I was a nerd. Despite missing all of it at the start, it became a pretty integral part of my life. When I moved to Berkley in the mid-90s, it was even more prominent there. People forget how cable companies and other infrastructure companies got in on the deal and how vital it was to academia.

Which, come to think of it, was also a huge bunch of nerds. Seriously, by the late 90’s I knew professors who “had to suddenly” give a class by Conference Call.

I think in a weird way the Conference Call revolution both drove and delayed the adoption of the Internet. You could do a whole lot with a line, and the fancy specialized phones that companies sold (at a big markup) that maybe you didn’t need the internet. At the same time the growing infrastructure changes led to interests in other changes. I wonder if videoconferencing like Ringer would have come about as quickly – or were they accelerated?

It’s funny now how we still use these lines. But they afford security, they’re easy to use, and they’re familiar. I get it, even if I didn’t at first.

The 80s and 90s was a time of weird technical and cultural ferment, and I could see Conference Calls getting a big boost. Certainly I knew the various zine groups and geeks I went to, cons I went to, were filled with people who’d have taken advantage of it. Considering how phone companies broke up and consolidated, I see it as a potential business opportunity.

Steven Savage

But What If It Wasn’t Worth It?

by

(This column is posted at www.StevenSavage.com, Steve’s Tumblr, and Pillowfort.  Find out more at my newsletter, and all my social media at my linktr.ee)

As I’ve mentioned a few times here, a friend once said she didn’t think any tech “innovation” in the last 15 years was worth it overall. Admittedly considering some of the innovations are supermassive web frameworks and electric vehicles that inadvertently catch fire, I sorta get that. But this brings up a larger question.

What is it we’re used to today that actually isn’t worth it?

This makes me think of my interest in Chinese history and philosophy. Watching Taoists and Confucians discuss good government, it was in context of feudalism, so it was “what if we feudalismed right?” Like maybe feudalism was part of the problem, even if some Taoists had a kind of “Anarcho-feudalism” in mind.

So how much of what we have today we think of is perfectly fine and normal is a bad idea we’ll need to get over? And I’m not talking the usual critiques of things like AI (which is easy), but other technologies and policies and the like.

Focusing America on the automobile is one that I think is a big mistake, even if I like having one. It’s led to racist zoning, sprawling suburbs, loss of public transportation, pollution, and the like. I’m not saying automobiles are bad, but man did we overdo it for various reasons.

Try to imagine if that hadn’t happened.

I’ve also wondered about the impact of parts of pop culture. Things I loved in my youth have become sprawling, money-sucking mega-franchises. Was it large company consolidation that we needed to avoid? Something else? Why is it now when I hear of anything Star Wars, Star Trek, or Marvel I just assume I won’t like it?

What was missed because we made another Star Trek?

In another case I definitely felt that too much of our world got driven by graphics. Systems get bigger, cards get larger, all so we can watch web pages that look like movies and play games that don’t look like games. A few years ago I found Team Fortress 2 (a fave of mine for ages) still runs off of CPUs and looks fine in its stylized way.

How many resources got poured into pretty? Maybe we just didn’t need as much photorealism?

I’ve also questioned office software. I mean I self-publish out of LibreOffice, which is basically Microsoft Word ten years ago. I’ve worked with tools that store enormous amounts of data no one cares about. Look I’m fine with graphics software getting more powerful (albeit again, needing the hardware) but otherwise? Not sure.

I’d like something that does its job with options, not has something that does so much more than anyone needs. Or maybe some software can be more modular.

Try asking what we’re used to now that kind of has flaws is something we didn’t need or needed less of?

Steven Savage