When I decided I wanted a real PCB instead of a pile of development boards and jumper wires, I had to learn another tool from zero: EasyEDA.

I had worked around electrical drawings and control hardware for years, but PCB design was different enough that I had to slow down and learn the language of it.

The schematic was only the beginning.

Then came footprints, net names, component placement, routing, board clearances, design-rule checks, connector locations, copper pours, and all the little manufacturing details that matter once the board has to become a real object.

One of the first things I learned was that “this component should work” is not enough.

I also had to ask:

• Is the footprint right?
• Is the part actually available?
• Can the assembly house place it?
• Is the pin numbering what I think it is?
• Does the part fit where I put it?
• Am I creating a routing problem for myself later?

That was a big shift from the PLC world, where I am usually working with finished industrial components and established wiring conventions.

Here I was responsible for deciding how the whole thing physically went together.

AI helped a lot during this phase, especially when I was learning how EasyEDA represented things and when I ran into DRC problems I did not understand yet.

But again, I had to verify everything.

A footprint that looked good on screen still had to match the actual datasheet.

A pin assignment still had to match the part.

A board that passed one check could still have a completely different problem hiding somewhere else.

Eventually I got far enough along that I had something I was willing to send out for manufacturing.

That was probably the first point where the project felt expensive enough to make me nervous.

A mistake in software is annoying.

A mistake in a PCB can show up a week later in a box with five copies of the same mistake.

When the first manufactured boards arrived, it was a completely different feeling from seeing the design in EasyEDA.

Now I could hold it, power it up, probe it, and find out whether all that work actually meant anything.

That is where the project moved from learning PCB software to learning hardware the hard way.

And that turned out to be the interesting part.