Psychology

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

The Result Isn’t The Thing

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)

In a recent discussion with Serdar – which seems to drive no small amount of my posts apparently – we were discussing writing and results. Both of us being writers, we’ve both put out a lot of, well, product in the form of books, blog posts, zines, and so on. We’ve also encountered many people who somehow can’t get product out, endlessly not finishing things.

(Also I hate calling my writing product. I also hate calling it content. But I digress, possibly enough to have a followup blog post.)

My terminology hangups assigned,I kept thinking about how people wanted to finish product (ugh) but never got to it. Never got a book done, couldn’t get a blog post out, and so on. They would talk about finishing but never get it done. Yet product was on their mind.

This got me thinking about how the focus on product is a problem, because product isn’t writing. Product is the result of writing. It’s the result of a process.

To write you have to write. Put pen to paper, finger to keyboard, and do it.

Except you also have to plot. You have to write things down, make plans, possibly throw them all away. You have to come up with what to say be it a mystery or the narrative you tell in a business advice book on textiles.

(Trust me, any good nonfiction book has narratives, it’s how humans think).

But to get to all that plotting you also need ideas. Brainstorming. Thinking things up. Trying things out. Breaking down in frustration and eating pastries when they don’t work (apple fritter is my preference here).

Then once you do all of the above and get something written you have to get beta readers, edit, run it through legal. If you’re self-published there’s formatting, covers, setting up, marketing.

Then, only then, do you have a product (again, ugh), because of a process. The actual book, the actual blog post, or wherever, is a small part of writing and publishing. Also by the time you’re done you’re probably on to something else, possibly to avoid thinking about the book you just put out.

But the product is just what a process produces, and unless you’re into the process you won’t get out the product. Endless speculation on the final product keeps you from getting it done. I say this having written any number of things, some stunningly mediocre, but at least they were done and real. And yes, I moved on because I love the process of writing.

I think the endless enchantment of the end result deceives us. We feel it can’t be reached, we feel it must be a certain thing, or we can see it but not get there. But it misses that you just keep going keep trying, keep putting one metaphorical foot in front of the other, and write. Yes it may not be what you expected – it probably never is – but it’s done and out.

I also think this is why the fascination with AI is so powerful for some people. They imagine product dropped in their lap or made for them, ready for a bit of editing and then delivery. But the thing is that’s not the process, the real lives experience, the building of skill, the you saying something. It’s not about being a writer.

And if you want to be a writer, you embrace the process (sometimes gingerly) and write until you’re done. Or done enough. Or just disgusted so you toss it out into the world. But it’s done.

Steven Savage

See the Door Before You Open 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)

Serdar and I were recently discussing how certain opportunities open doors for people. I noted that sometimes its not opening the door, it’s seeing it in the first place. We can’t open the door until we see it.

(We also want to see the door before opening it in case it’s a bad idea. But anyway, I don’t want to over-follow this metaphor).

This idea of “seeing the door” led me to think about a few examples from my own creative and professional life I wanted to share to illustrate the point.

Creatively, as some of my regular readers know, I do surrealist collage art under a pen name (art name?). I got into this via small press zines, originally just to add some decoration, but quickly got very into the collagist style. Now I’m using museum images, researching art history, and creating some truly strange and wild stuff – and learning about graphics and imaging tools and making new friends.

I’d never have thought of doing this except for, well, a series of events. Now I can see how I enjoy unusual art and such. I have done graphics before, but did I expect to pick up playing Max Ersnt in my 50s? No. However it all makes sense, filling my sense of curiosity, of creativity, and a desire to connect via creativity.

I didn’t see the door until I tried something different.

Career-wise, let’s talk laboratories. As folks know I work in medical research and education as a Project Manager. I got assigned to work on a project to set up some environmental monitoring for a lab, and after some research, found there was other work to be done as well. Suddenly I’m down the rabbit hole on environmental sensors, chemical testing, and equipment so heavy it needs special tables to use – and I’m having an incredible time.

Plus sometimes I wear a Geiger counter at work or get my shoes checked for hazmat.

I’d have never thought that, say, things like liquid nitrogen or worrying about sensor condensation were a thing for me. Yet, I found the world of lab setups exciting and stimulating, a whole new world that called on my organization skills, social skills, and science skills. What started as a chance assignment and my own hard-headed dedication to researching project needs has started to define my career.

I didn’t see the door until I tried something different.

The ability to see the door is just as important as being able to open it. Maybe moreso since we can’t open it until we see it (and if we can’t open it we can learn how to or break it down). To see the door to something more you have to try new things, experience new things, and get educated.

This is why education matters, why new experience matters, why knowing there are unseen doors matters.

I’m in or approaching middle age, depending on who you ask – but I keep going, the above things make me feel alive. I have friends who are the same, always finding new doors, always alive. I have older friends and family who keep finding new things and they have that spark.

Keep finding doors. Keep setting up situations so you can find new doors.

Steven Savage