Do Server Administrators Not Write Code? — The True Nature of the “Invisible Language” Revealed in a 200-Person Project

The Shock of “Engineers Who Don’t Code”

What!? There are people who control systems without writing code—

In my 7th year as a professional, I joined a large-scale development project with over 200 members as a configuration management leader. With five companies involved, I was responsible for creating various standards and guiding the entire team through structured rules.

Among all roles, the one I worked most closely with was the server administrator. Configuration management and server management were the two wheels supporting the project. Naturally, our conversations increased.

One day, I casually asked:
“How much Java do you usually write?”

The answer I got was unexpected.
“Actually, I’ve never written it.”

The “Language of Scripts” That Runs the Field

Surprised, I asked further:
“So… you don’t program at all?”

He smiled slightly and replied:
“Well, I do simple stuff.”

What he referred to were shell scripts like Bash and Windows VB scripts.

At that moment, the hidden structure of the system became clear to me.

Servers are managed in units called “JOBs.” All processes are scheduled and automated. And the system that controls this is JP1.

However, JP1 does not operate alone. When calling OS functions, it always goes through scripts. In other words, shell scripts and VB scripts act as “translators,” conveying JOB instructions to the servers.

A System Runs on “Three Layers”

If we structure it, it looks like this:

• Overall control: JP1 (JOB management)
• Execution layer: Individual servers
• Connector: Scripts (Shell / VB)

And on top of this, our applications like Java are running.

In other words, behind every visible application, there are countless scripts supporting the entire system.

“Small Code” Governs the System

Weekly processes, batch jobs, log collection, monitoring integration—
All of these are built on the accumulation of small scripts.

They are not large programs. But their number is enormous, and if even one fails, the entire system can stop.

Their work is not flashy. Yet, they undeniably keep the whole system running.

Where Does the Value of an Engineer Lie?

Here is a question worth discussing:

Which is more valuable?

“Someone who writes large-scale code in advanced languages”
or
“Someone who can operate the entire system”

In the DX era, the answer is clearly shifting.

What truly matters is the ability to “connect” and “drive” systems.

Scripts are the very symbol of that capability.

Can You See the Invisible Value?

That sense of discomfort I felt back then has now turned into conviction.

The value of an engineer is not determined by “which language you can write.”
It is determined by “how far you can make systems run.”

With this perspective, the way you see your career changes dramatically.

And only those who recognize invisible value can move to the next stage.

I can do it! I’ll take the first step starting tomorrow