How I Make Sense of Software Development as a Layman - An Material Engineer's Perspective

An article by Xiaoxiang Yun

As someone trained in material engineering, my world has always revolved around tangible things: metals, ceramics, polymers, and composites. The beauty of material science lies in its layers - atomic structures, microstructures, and macroscale applications - all seamlessly interwoven to create functional products. It wasn’t until I ventured into software development, however, that I realized the parallels between these two seemingly disparate fields.

Software development, much like material engineering, has its own layered structure, intricate processes, and relentless pursuit of perfection. Here's how I make sense of software development through the lens of a material engineer.

Front-End: The Visible Surface

In material engineering, the outer layer of a product is its interface with the world. It’s what customers see, touch, or interact with. Think of a smartphone’s screen, the sleek surface of a car, or the ergonomics of a tool handle.

In software, this is the front end - the user interface (UI) and experience (UX). It’s the dashboard of a car or the display of a coffee machine, designed to be intuitive, visually appealing, and functional.

My Layman Analogy:

The front end is the polished ceramic coating of software. It’s what catches the user’s attention and makes them want to use the product. Just like a material must be durable and aesthetically pleasing, software must be responsive, user-friendly, and adaptable across devices.

Back-End: The Core Material

If the front end is the visible layer, the back end is the bulk material. It’s the engine under the hood, the wiring in the walls, or the atomic structure in a metal alloy.

The back end powers the software - managing databases, servers, and the logic that makes the front end work. It’s not flashy, but it’s fundamental.

My Layman Analogy:

The back end is like steel in construction. Users rarely think about it, but it’s what holds the entire structure together. Just as a material engineer selects alloys for strength and reliability, software developers build robust back-end systems for seamless functionality.

Middleware: The Adhesive

In material engineering, we often need layers to bond - whether it’s laminates in a composite or the coupling agents that hold together different phases of a material. This is where middleware comes in. It connects the front end with the back end, ensuring they work in harmony.

My Layman Analogy:

Middleware is the adhesive or matrix resin in a composite material. It’s not visible, but without it, the system would fall apart. APIs (Application Programming Interfaces) act as connectors, enabling different parts of a software ecosystem to communicate, much like a binder holding fibres in place.

Iteration: The Refinement Process

In material engineering, no product emerges perfect on the first attempt. We prototype, test, analyze failures, and iterate until we achieve the desired properties. Software development mirrors this process.

My Layman Analogy:

Iteration in software is like heat treatment in metals or curing in polymers. Each cycle makes the product stronger, more reliable, and better suited to its purpose. Whether it’s debugging code or improving a user interface, the process is one of constant refinement.

API: The Joining Mechanism

An API is a set of rules that allows different software programs to communicate. For a material engineer, this is like a mechanical joint or a soldered connection in a circuit board. APIs enable modularity and scalability, just as joints and connectors enable structures to grow or adapt without rebuilding from scratch.

Quiet Efficiency: The Unsung Hero

In engineering, some materials perform best when they are "quiet" - absorbing energy, reducing friction, or resisting wear without calling attention to themselves. Similarly, the best software works quietly in the background. Users don’t notice it; they simply enjoy the seamless experience.

My Layman Analogy:

This quiet efficiency is like a polymer coating reducing wear on a bearing. It’s invisible to the user but essential to the system’s longevity and performance.

What I’ve Learned About Software Development

1. Layered Complexity:
   Software, like materials, is built in layers. Each layer has a purpose and must work seamlessly with others.

2. Interdisciplinary Thinking:
   Just as material engineers collaborate with mechanical or electrical engineers, software developers work across disciplines, blending design, logic, and infrastructure.

3. The Power of Iteration:
   Whether it’s a turbine blade or a mobile app, perfection is a result of testing, learning, and improving.

4. Integration and Modularity:
   Both fields thrive on systems that integrate well and can scale or adapt to new challenges.

Closing Thoughts

As a material engineer navigating the world of software development, I’ve found comfort in the parallels between these fields. Both require precision, creativity, and a deep understanding of how individual components contribute to the whole.

For businesses, understanding these parallels can be a game-changer. Whether you’re refining a physical product or developing an app for your café, the principles of iteration, integration, and layered design remain the same.

So, the next time you marvel at a perfectly brewed cup of coffee or a beautifully designed app, take a moment to appreciate the engineering - whether it’s material or digital - that made it possible.