Are Electronics, IT, and Electrical Really Different Fields? — What an Electronics Engineer Who Went Through IT Found When Looking at Electrical Installations

The first time I actually sat down with an electrical drawing was a Friday afternoon a few years ago. One distribution panel schematic on the table, an electrician walking me through the circuits one by one. I listened, and the whole time my mind kept drifting. I've seen this picture before.

Electronics, IT, electrical. We usually file them as three separate industries.

Electronics means semiconductors, circuits, sensors, MCUs. IT means servers, networks, databases, applications. Electrical means power, transformers, switchboards, distribution panels, breakers.

Different technology, different codes and standards. Electrical work especially sits right up against human safety, so if you line it up next to an IT system and say "same thing," someone on site will set you straight. Let me nail that down before anything else.

But climb one level up, strip everything except how does this system work, and the overlaps start showing.

I ended up putting it crudely:

Electronics handles signals. IT handles information. Electrical handles energy.

Different subject matter. But the structure for moving it, splitting it, controlling it, protecting it, and watching it — that part rhymes.

Start with the circuit

Lay out one circuit, as simple as it gets.

A sensor measures something outside. The circuit takes that signal, an MCU or processor works on it. The result turns on an LED, spins a motor, drives some other device.

Strip it to structure:

Input → transport → processing → control → output

Then you start building something you actually intend to sell, and the story gets longer.

What if the voltage runs too high. What if current flows somewhere it shouldn't. What if the sensor readings spike. What if the link drops.

So protection circuits go in. Fuses get added. Sensors and measurement functions get bolted on so you can see what state things are in. Bit by bit the system turns into this:

Input → transport → processing → control → protection → observation → output

Anyone who studied electronics has seen this diagram until they're sick of it.

The problem is that IT systems don't look all that different.

In IT, the signal gets abstracted into data

Take a web service.

A user sends a request. It travels the network and arrives. An API receives it, the application processes it. If it needs to, it hits the database and returns a result.

Client → Network → API → Application → Database

Complicated cloud systems are, at the level of shape, this same structure stretched out.

More users, so you put in a load balancer. More services, so you put in an API gateway. You assume failure, so you attach timeouts, retries, circuit breakers. You need to know the state, so you collect metrics and logs. Something like Prometheus scrapes them, something like Grafana draws the pictures.

IT asks the same questions. Where does it go. How does it get split. Who controls it. When something breaks, where do you cut. How do you know it's healthy right now.

The worries I had in front of a circuit come back with nothing changed but the scale.

The point where the electrical drawing stopped me

Compress a building's power system, roughly.

Power comes in from outside. It gets converted into the form you need and distributed. At the panel it splits into multiple circuits. It gets consumed at real loads — lighting, outlets, HVAC, motors, production equipment.

Source → substation/switchgear → distribution panel → branch circuits → loads

Same problems show up here too.

What if current piles onto one circuit. What if there's a short. How do you keep a fault on one circuit from spreading to the one next to it. How do you know how much is being drawn right now.

So there are breakers, protective devices, meters. That day, with the electrician tracing the drawing for me, I went a little blank right at this part. It was the same sentence structure as the meeting I'd been in the day before.

Putting all three on one page

I'm not saying a fuse, the circuit breaker pattern, and a distribution breaker are the same technology. Different operating principles, different purposes, and the weight of the safety requirements isn't even close.

But abstract it to system architecture and the overlap looks like this:

System view	Electronics	IT	Electrical
Primary subject	Signal	Information·data	Energy
Input	Sensor·electrical signal	Request·data	Electric power
Transport	Circuit·bus	Network·API	Wiring·busbar
Processing/control	MCU·controller	Application	Control·protection systems
Distribution	Circuit topology	LB·routing	Distribution·branch panels
Protection	Fuse·protection circuit	Isolation·circuit breaker	Breakers·protective devices
Observation	Sensor·instrumentation	Metric·log·trace	Voltage·current·power metering
Final target	Actuator	Service·user	Load

Forcing a one-to-one match between individual pieces of equipment isn't worth much. What I saw is that the basic principles of building a system keep repeating.

Why protection always shows up

One thing in common comes into focus here.

A good system isn't one that doesn't fail. It's one where a failure doesn't take everything down with it.

Electronic circuits defend the circuit against overcurrent and overvoltage. Power systems cut off the faulted circuit so the incident doesn't grow. IT isolates one service's failure so it doesn't spread everywhere.

The circuit breaker pattern you see all over microservice architecture took its name straight from the electrical breaker. Just as a breaker opens the circuit under a fault condition, software stops shoving requests at something that keeps failing and holds the door shut for a while.

Different fields, same attitude. Stopping the propagation of a failure comes before the failure itself.

True in a small consumer device, true in a building's power network, true in a cloud running thousands of servers.

Get big enough and observation follows

Small circuit? Poke it with a meter. One server? SSH in and look. Small electrical installation? Check it on site with an instrument.

Once the system gets big, none of that works.

This is where observability steps forward — the ability to tell from outside what's happening inside.

IT has talked this to death already. You watch CPU. You watch memory. You watch network traffic. You watch latency and error rate. You collect logs and fire an alert when something looks wrong.

What about power systems? You watch voltage. You watch current. You watch energy consumption. You watch power factor. Temperature too. And you keep storing how all of it changes over time.

From that moment the electrical installation isn't an electrical device anymore. It's a system that produces data. This is exactly where electrical, electronics, and IT start meeting.

Three worlds in a single distribution panel

Take an ordinary distribution panel.

Power comes in. Breakers split it into circuits. Each circuit feeds a load — lighting, machinery. Up to here it's electrical territory.

Now attach sensors that measure current, voltage, temperature.

Electronics walks in. An MCU or edge controller reads the sensor values. Modbus or some other industrial protocol carries them out. A gateway passes them to a server.

Now IT walks in. The server accumulates the data. Builds dashboards. Sends alerts when something abnormal shows up.

Pile up enough data and you go as far as statistics or machine learning hunting for patterns that don't look like the usual. That's where AI connects.

Out of one distribution panel:

Electrical → electronics → communications → IT → data → AI

That's the stack you end up with.

The edge ahead may be in the connections, not any one technology

Industry grew for a long time by carving up specialties.

Electrical engineers know electricity. Electronics engineers know circuits and control. Software engineers know programs. Infrastructure engineers know servers and networks. It had to be split that way.

Deep expertise in each field is still going to be necessary. Anywhere human safety is on the line, like electrical installations, you don't get to poke at it with software instincts alone. However hard I look at it through IT eyes, I have no intention of pushing on that one.

But as IoT, smart factories, edge computing, cloud, and AI move onto the industrial floor, the boundaries keep blurring.

My guess is that one of the valuable skills going forward is knowing where different technologies attach to each other, alongside digging deep into one of them. Not a conviction. It's just where I'm placing my bet.

The world starts looking like one big system

Electronics looks at small circuits. IT looks at servers and networks. Electrical looks at the power network keeping buildings and factories running.

Different scales, different technology.

But one step up, the same questions keep coming back. What comes in. Where does it go. How does it get split. Who controls it. When something breaks, where do you isolate. How do you observe the current state. And at the end, do you use that data to make a better call.

I find it more interesting to lay electronics, IT, and electrical out like this than to keep them as three separate worlds.

Electronics handles signals, IT handles information, electrical handles energy. And all three are systems that transport, control, protect, and observe a resource.

One of the places these three actually meet on the industrial floor is the distribution panel.

Next post I want to go one level deeper. How does an ordinary distribution panel become a "smart" one? Is it a matter of bolting on a few sensors, or does it need a whole different architecture behind it? I haven't fully worked out the answer myself yet.