Insights and Advice for Software Engineers Working in the Manufacturing Industry
After a month and a week as a software engineer in a remote high‑tech manufacturing zone, the author shares candid observations on the prevalent use of Java, .NET, legacy frameworks like SSH/SSM, limited documentation, occasional front‑end tasks, and practical tips for thriving in such environments.
The author reflects on a month‑plus experience as a software engineer in a second‑tier city’s remote high‑tech development zone, noting the salary of about 7K, benefits such as dormitory, cafeteria, five‑insurances, and a relatively short commute.
He advises prospective developers to verify the department’s main business and programming language, observing that most teams use .NET while only a few use Java, and some engineers are dual‑skilled in both.
Assigned to a seemingly new project described as using an SSH architecture, he discovered it actually used SSM and faced a complete lack of documentation, forcing him to spend roughly ten days configuring the environment and writing his own configuration and development documents.
After getting the system operational, he was asked to create a Java Swing interface, and later handled a simple front‑end task by delivering a pure HTML page within a morning.
A subsequent requirement led him to build a small feature using Vue, Axios, a backend controller, service layer, and database, but the client later demanded a plain JavaScript page, highlighting the inconsistency between modern front‑end practices and legacy expectations.
He notes that most projects are JSP‑based with little front‑end/back‑end separation, requiring developers to maintain older technologies for compatibility.
The company’s database lacks even basic indexing, and senior staff have long tenures, making it difficult to switch to internet‑focused roles.
He summarizes practical advice for manufacturing‑sector programmers:
Confirm the department’s language requirements; .NET is more common than Java.
Be prepared to handle both front‑end and back‑end tasks; front‑end work is often ad‑hoc.
Learn legacy technologies such as JSP, SSH/SSM, and Swing, as they remain essential.
Focus on database knowledge; understanding indexing and design can be more valuable than modern cloud frameworks.
Maintain thorough documentation, as many older projects lack it.
Familiarize yourself with manufacturing systems like ERP, CPC, MES, and reporting tools.
Recognize that compensation may be modest and promotion opportunities limited compared to internet companies.
Java Captain
Focused on Java technologies: SSM, the Spring ecosystem, microservices, MySQL, MyCat, clustering, distributed systems, middleware, Linux, networking, multithreading; occasionally covers DevOps tools like Jenkins, Nexus, Docker, ELK; shares practical tech insights and is dedicated to full‑stack Java development.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.