Introduction: In the steel jungle of industrial automation, PLC engineers and IT software engineers are like beings from two parallel universes.
One struggles with a screwdriver in the workshop, while the other types code in the office; one curses the cables in the control cabinet, while the other sighs at bug pop-ups. But if you catch a PLC engineer, reeking of machine oil, and ask, “What do you envy most about the IT world?” he will likely gaze longingly at the glass curtain wall of an office building and say, “They don’t have to go to the workshop at 3 AM to fix the frequency converter!”
Office Environment: From Steel Cages to Coffee Paradises
The daily commute of a PLC engineer can be described as a “Transformers” mode—while others carry laptop bags and squeeze onto the subway, they lug toolboxes to catch the bus, with their bags containing not just notebooks but also multimeters and screwdrivers. The moment they step into the workshop, they are greeted by the roar of machine tools and the mixed smell of hydraulic oil, and the operation console resembles an “industrial escape room”: with the noise of the frequency converter’s cooling fan in front and the death stare of 380V cables in the control cabinet behind. The most thrilling part is in summer, when IT coders enjoy watermelon in a 24°C air-conditioned room, while PLC engineers are crouched next to a 60°C motor adjusting parameters, their hair in hard hats could be wrung out from sweat.
In contrast, the office environment of IT software engineers is a “cyberpunk utopia”. Open workspaces with ergonomic chairs, endless freshly brewed coffee on the desk, and meeting rooms filled with terms like “Agile Development” and “Microservices” on the whiteboard. What frustrates PLC engineers the most is “remote work”—while they are making winter-proofing measures for PLCs in a workshop at -20°C in Northeast China, IT colleagues might be coding in flip-flops at an Airbnb in Sanya, with palm trees in the video conference background looking much more pleasant than the cables in the control cabinet.
Work Content: From “Cable Puzzles” to “Keyboard Magic”
PLC programming can be likened to “industrial Lego”—while others write code by typing on keyboards, they must first study the terminal block wiring diagrams. For example, when wiring a sensor, an IT coder might just need to call an interface in the API, but a PLC engineer has to use tweezers to insert 0.5mm² cables into terminal holes; if they accidentally bump a wire, it could cause the entire production line to “shut down” for two hours. During a debugging session on a filling line, I once witnessed an old engineer using a magnifying glass to inspect the wiring, his focus comparable to that of a bomb disposal expert.
On the other hand, the world of IT software engineers is filled with “magic attacks”. They can make server clusters obedient with just a few lines of Python code; writing a script can batch process data with the efficiency of an army. What’s even more frustrating is “version iteration”—updating PLC programs requires lugging a laptop to the site to insert and remove storage cards, while IT colleagues can sip milk tea in the office and click “release”, making the code fly to the user end as if it had grown wings. Once, while dining with a friend from an internet company, he said, “We just launched a new feature, and user feedback was instantaneous,” while I silently recalled spending three hours in the workshop last week just to complete a PLC firmware upgrade.
Overtime Philosophy: From “Life-and-Death Speed” to “Elegant Involution”
Overtime for PLC engineers can be described as “industrial-grade emergency rescue”. Receiving a call at 3 AM saying “the production line is down” is a common occurrence; they brave the cold wind to take a taxi to the factory, while checking program logs on their phones. Once, during the Spring Festival duty, the PLC of a stamping machine suddenly reported a fault, and I was in the workshop wearing a down jacket, disassembling modules, my fingers colder than the screwdriver, while my IT friends were posting pictures of the Spring Festival gift boxes from their companies—one even contained a hand warmer.
In contrast, IT software engineers’ overtime is marked by “cyber elegance”. They sit in bright offices, fixing bugs on their screens, taking breaks to play games in the pantry, and enjoying free snacks when hungry. What makes PLC engineers envious is “online fault handling”—although they also have to stay up late, at least they don’t have to troubleshoot sensor faults in a warehouse at -10°C. Once, while chatting with my cousin who works in the internet sector, he said, “I was handling an online fault until 2 AM last night,” and I looked at the Starbucks cold brew on his desk, recalling that the last time I handled a fault, I was drinking expired mineral water from the workshop vending machine.
Salary and Benefits: From “Steel Subsidies” to “Code Dividends”
The salary of a PLC engineer can be described as “industrial hardship subsidies”. The base salary looks decent, but it relies heavily on overtime and business trips—going to Xinjiang to debug equipment might cover the round-trip airfare, but living in a temporary house on the Gobi Desert for half a month means the subsidy is only enough to buy a few bags of spicy strips. The most disheartening part is job-hopping—switching from an automotive factory to an electronics factory means learning different brands of PLC programming from scratch, while IT coders can switch jobs like “changing skins”, with a Java engineer still writing Java at an internet company, only the framework changes from Spring to Spring Boot.
In contrast, the salary of IT software engineers is a prime example of “code monetization”. Fresh graduates can earn more than veteran PLC engineers, and during the “golden September and silver October” job-hopping season, salary increases can be astronomical. Once, at a class reunion, a friend working in AI algorithms said, “I just received stock options worth several hundred million in valuation,” while I silently calculated that it took me three years to save enough for a down payment on a house. Even more frustrating is “side income”—an IT colleague can buy a new computer by taking on a freelance project, while a PLC engineer’s “side job” might be fixing washing machines on weekends, as the logic for fixing frequency converters and washing machines… seems to have some similarities.
The Ultimate Blow: When PLC Meets IT’s “Dimensionality Reduction Attack”
What frustrates PLC engineers the most is the “dimensionality reduction attack” of IT technology on the industrial field. For example, digital twin technology—an IT engineer can build a virtual factory on a computer to simulate production line operations, while a PLC engineer has to adjust parameters on-site with physical equipment; and low-code platforms—IT colleagues can drag and drop to build an MES system, while PLC engineers have to write ladder diagrams line by line. During a visit to a smart factory, I saw a 3D visualization interface on the screen, and the factory manager said, “This was done by the IT team,” while an old electrician next to me secretly said, “Back in the day, we drew circuit diagrams with pencils and erasers.”
But that said, PLC engineers also have their own “industrial romance”—when they see the production line they debug running efficiently, or when they personally make a stalled machine roar back to life, that sense of accomplishment is something IT coders clicking “release” on a screen cannot compare to. As the workshop veterans often say, “We play with real things, while they tap away in a virtual world; each has its own struggles and sweetness.”
However, if you ask me to choose now—I would still choose to sit in an air-conditioned room typing code, after all, who wouldn’t want to debug in Sanya? At least I wouldn’t have to compete with a frequency converter for airflow.
Copyright belongs to the original author. If there is any infringement, please contact for deletion.Disclaimer: This article is an authorized reprint, and the copyright belongs to the original author. The content of this article reflects the original author’s views and does not represent the views of this public account or its responsibility for its authenticity.The new issue of “Digital Enterprise” is available for subscription, and there are also calendar notebooks to give away, while supplies last!