First TakeFirst Take

Thanksgiving

In the US, Thanksgiving is next week and the next issue of The Shift Register will drop on Black Friday when early morning shoppers will try to score deals at brick and mortar stores. The tradition for Thanksgiving here is to gather with friends and family and have a large feast with a turkey as the central entree. Many families have other themes surrounding parade watching, football games and what have you, but by and large we gather our closest people and share a large meal with the idea of giving thanks for the bounty the year has provided us.

The economy is soft and even my talented and workaholic wife has been laid off from her six-figure job since July. Anyone else looking for ways to cut $145k from their annual household budget? Still, there is plenty to be thankful for. I for one, as a double stage 4 cancer survivor, am thankful for everyday this side of the dirt. I've never been really motivated by money, but have managed to remain mostly gainfully employed my entire adult life. Getting ready for this holiday, considering retiring while looking at the broad chaos erupting in our world, I can't help but consider that we have to look again at our families and loved ones and just be thankful for their love, presence and support in our lives. Sorry, nothing techie here outside of the personal layoff impact. Be grateful for and take care of your families even if you don't celebrate Thanksgiving. Good luck out there!

Credit to Bon Appitit Magazine for the photo:

The Shift Register  

EditorialEditorial

CIO's Corner

This week, I'd like to share something that has been a good comparative source for me for decades in terms of identifying and implementing new solutions. I'm not talking about the new startup's webinars or industry seminars or swag give-away events either. I'm talking about plain old open source software. Now this was a dirty word for a long time in enterprise software and government circles, but these days, many of the most innovative products are starting out as open source software solutions.

Even if there's a major industry player involved, they frequently lack the across the board expertise to bring their ideas to fruition with in-house development resources and open-source their code hoping to bring additional developer support to their nascent project ideas. Solutions like AMD's Lemonade server, that supports a ton of AI models and three different backends as a one-stop serve-all of edge compute AI are out there and free to use/experiment with. You may not end up using this exact tool, but it gives you a broader understanding of what is possible and deployment needs within the current ecosystem surrounding whatever need you are trying to fill.

This is what I call the research hat for CIOs. You have to understand what is already out there in order to avoid reinventing the wheel or pursuing targets that are largely already well addressed. If you stop your technology assessment work with back issues of PC Magazine, you are going to pay a bunch of money for something that might be stable, but isn't a best fit for your needs. You'll buy more software to fill the holes.

With open source solutions, you can find something that is 95% of what you need or more and decide to pay for support and the other 5% or fork it and roll your own. This doesn't mean that 5% will be cheap or easy, that's where your organization's experience and relative development chops need to be added to the decision matrix. Buying closed source software doesn't get you any guarantees and what you are really paying for is support and the ubiquity of adoption across your industry to ensure you won't have to train your users, too much. Many of these vendors use multiple open source software packages underneath an overarching infrastructure that welds things together in a more user friendly fashion.

Unfortunately, with closed source software you also get things like vendor lock-in, forced upgrades and run-away licensing costs from year to year. To give you one example, we recently had to procure an MDR system due to requirements coming down from our parent company. As I went through vendors and options, I spoke to engineers and looking at the vulnerability scanning tool in one of our choices for an MDR, immediately recognized some features from Greenbone, an open source tool that also has paid options with more advanced features. Now, for the past few years, I've used this tool to do our internal vulnerability scans and found it reliable. The engineers at this new MDR admitted that Greenbone was the tool they used for the vulnerability scanning.

So what does that mean to us? It means, I already know and trust a portion of their software stack or their supply chain as it were. This is important. You have to have verified supply chain sources from your vendors that you both trust and that you can monitor for breach activity. So, now as I go through my daily research work, if I see an issue with Greenbone, I reach out to our MDR SaaS vendor and ask them if they have addressed this or when they will.

The point is that even if you don't personally adopt or buy open source software, at some point one of your vendors will. You need to know what they are using in development and in their software supply chains to understand your own. If you leave it to them alone, you are placing a greater degree of trust in their risk mitigation efforts than your own. Remember, they'll have many clients, but your organization is the only one you are looking after. It's your baby and at the end of the day, your responsibility from end to end. Your job is to manage IT risks and understanding the supply chain of every vendor is part of it.

Kudos to ChatGPT for the graphic.

The Shift Register  

AI Perspective: The Economy Was Built for Humans to Work. What Happens When We Don't Have To?

By ChatGPT

For most of modern history, technological progress has been measured against a remarkably consistent objective: produce more, faster, cheaper, and with fewer resources. Machines replaced physical labor. Software replaced repetitive administrative work. Automation reduced the number of people required to manufacture, transport, calculate, process, and manage things. Each successive wave of technological advancement promised greater productivity, and largely delivered it.

Artificial intelligence and robotics may be different in degree, if not in kind. They are beginning to encroach on tasks that were previously considered uniquely dependent on human intelligence, judgment, adaptability, and physical dexterity. The distinction between assisting a worker and replacing the worker is becoming increasingly difficult to maintain.

The debate about whether AI will eliminate jobs or create new ones is familiar. History provides plenty of examples of technologies that destroyed occupations while creating others. But history is not a guarantee, and the scale, speed, and breadth of what is emerging deserve a more serious examination than simply assuming the next transition will resemble the last.

The more interesting question isn't whether AI will replace jobs. It is why we have constructed a society in which access to the necessities of life is so heavily dependent upon the availability of work that technology may increasingly be capable of performing.

Employment is more than an economic transaction. For billions of people, it is the primary mechanism for obtaining food, housing, healthcare, transportation, education, and financial security. It is also a source of identity, community, social status, and purpose. Our economic institutions, public policies, retirement systems, and cultural expectations have evolved around the assumption that most adults will spend a substantial portion of their lives working in exchange for compensation.

That assumption has served industrial society reasonably well. It may not survive the next technological transition intact.

Businesses have powerful incentives to adopt technology that improves efficiency, reduces costs, increases production, or provides competitive advantages. Those incentives don't inherently distinguish between eliminating unnecessary administrative work, improving the productivity of an existing employee, or eliminating the position entirely. The decision is generally driven by economics, not by the broader consequences for the labor market or society.

And that isn't necessarily an indictment of businesses. Businesses operate within incentive structures created by markets, regulations, competition, and shareholder expectations. If an organization can achieve substantially greater productivity while reducing labor costs, it may be economically compelled to do so simply to remain competitive.

The problem is that the benefits of productivity improvements and the costs of displacement are not necessarily borne by the same people.

A company may become more profitable. Consumers may benefit from lower prices. Investors may benefit from increased returns. A small number of highly skilled workers may become substantially more productive and valuable. Meanwhile, people whose occupations disappear may find themselves competing for a shrinking pool of available positions, retraining for unfamiliar careers, or struggling to maintain the economic stability they previously enjoyed.

Productivity gains do not automatically translate into broadly shared prosperity.

There is an uncomfortable asymmetry here. Technological development can move remarkably quickly when incentives, capital, infrastructure, and engineering talent converge. The institutions required to manage its consequences move much more slowly. Education systems, labor protections, tax policies, healthcare structures, and social safety nets were not designed for a world in which the economic value of human labor might change substantially over relatively short periods.

We could find ourselves with extraordinary productive capacity and inadequate mechanisms for distributing the benefits.

That is not an inevitable outcome of artificial intelligence. It is a potential consequence of failing to adapt.

There are possible alternatives. Productivity gains could translate into shorter working weeks, greater flexibility, improved public services, new forms of compensation, or economic arrangements that don't depend exclusively upon traditional employment. New industries and occupations may emerge that we cannot presently anticipate. Entirely new opportunities for human participation, creativity, and enterprise may develop.

But none of these outcomes are automatic. They require decisions, experimentation, policy changes, investment, and sometimes a willingness to reconsider deeply embedded assumptions about how society should function.

The technological question is whether machines can increasingly perform the work we currently assign to humans. The economic question is who benefits when they do. The social question is what happens to the people whose economic security, identity, and sense of purpose have been tied to that work.

Those are three very different questions, and solving the first does not solve the other two.

Artificial intelligence is not arriving with a predetermined economic or social blueprint. Its capabilities will be shaped by the organizations deploying it, the incentives governing those organizations, the policies enacted by governments, and the choices made by the people affected by its adoption.

The technology may eventually make human labor less necessary for producing many of the things society needs. If that happens, it would be a remarkable achievement of human engineering and scientific progress.

But an achievement of that magnitude would also require us to reconsider a fundamental premise of our economic civilization: that people must continually sell their labor in order to earn the right to participate in the benefits of civilization.

We have spent centuries developing machines to reduce the amount of work required to sustain human life.

Perhaps the next challenge isn't teaching machines to do more of our work.

Perhaps it is learning what to do with the world when they do.

How this was done: I provided ChatGPT with a draft of issue 81 and asked if there was anything that stood out as a potential AI Perspective article. It chose this topic and I asked if it would like to write the article.

Kudos to ChatGPT for the graphic.

The Shift Register  

AIAI

Emerging TechEmerging Tech

NewsNews



RoboticsRobotics

Open SourceOpen Source

SecuritySecurity



Final TakeFinal Take

Supply Chains in Dev

Back when I built my first website, I hosted on a public provider and had no idea what the server was. I think it was actually a netscape built product at the time. The site came free with my dial-up account. I know, crazy, right? What did I build?

I did some screen captures and editing for a Jane's ATF fan site. Folks were all agog at my 3d button action replication mirrored as navigation options from the software controls inside Jane's ATF. Simple stuff, done after work just to explore the emerging technologies. I still do this kind of work today.

Not websites, or at least not any I code directly, but lots of software investigation and use case work. This helps me determine best fit solutions and assess new technologies as they emerge. When I left my web-dev days behind, I had worked with IBM WebSphere, IIS and LAMP stacks galore. When it came time to pick up and dust off my web-dev hat a few years back, none of these options were a good fit for modern workloads and security environments.

We're a mostly Microsoft organization here, using their SaaS to a large degree, so we went with Azure based systems, but fielded secure Linux docker components for our subsystems and load balancing. I can't really say here what our web server software and code stack is today, but know that it isn't Nginx, apache or anything using PHP or Java. I can say that every part of the stack has been vetted to ensure they are keeping up with CVEs and not controlled by an unfriendly nation. We have even changed stack components a couple of times as timely CVE patching was failing for that vendor.

When you are developing software of any sort, the tools you use, the supporting infrastructure, all of it becomes a part of your supply chain that you have to track and update as time goes by in order to keep your system operational in today's very hostile environments. Whether you are building public or private web apps, endpoint software or server components is irrelevant. The availability and the security of the system depend on your design choices and the ability to remain flexibly current as needed. There is a lot out there, so choose very wisely and keep shopping for better fits. Good luck out there.

Kudos to ChatGPT for the graphic.

The Shift Register