I’m Emmanuel, and I design systems, some you can walk through, and others that run on a board.
My work spans architectural floor plans, PCB design, and Excel VBA automation, but...Read moreI’m Emmanuel, and I design systems, some you can walk through, and others that run on a board.
My work spans architectural floor plans, PCB design, and Excel VBA automation, but the way I approach them is the same. I focus on structure first. Whether it’s a building layout or a circuit, I’m looking at how everything connects, where problems will show up, and how to make the system work cleanly under real conditions.
In architecture, I’ve worked on projects like garage conversions, floor plan redesigns, and CAD redraws from rough sketches or outdated drawings. These aren’t just drawing tasks. Most of the time, there are hidden constraints, tight spaces, poor flow, or layouts that don’t translate well into actual use. My role is to restructure those plans so they make sense both on paper and in reality.
That same thinking carries directly into my PCB work.
When I design or redraw schematics, I’m not just placing components. I’m restructuring systems. I’ve handled schematic redraws, reverse-engineered circuits, and cleaned up designs where the logic or layout was inefficient. Just like in architecture, a small structural mistake in a PCB can affect the entire system. I focus on signal flow, component relationships, and making sure the board performs reliably, not just looks complete.
There’s a clear parallel between both fields.
A floor plan organizes physical space.
A schematic organizes electrical flow.
In both cases, I’m solving for structure, clarity, and performance.
Excel VBA is where I apply that same mindset to workflows. I build automation systems that take scattered or repetitive processes and turn them into structured, reliable tools. Whether it’s reporting, data handling, or task automation, the goal is always to remove friction and make the system run smoothly without constant manual input.
I also work with websites when needed, focusing on simple, functional builds that support the purpose they’re meant to serve.
What matters most in my work is how I think through problems. I don’t jump straight into execution. I break systems down, identify weak points, and rebuild them in a way that holds up over time.
If you’re dealing with something that feels messy, unclear, or inefficient, whether it’s a plan, a circuit, or a workflow, I’m the kind of person who can step in, restructure it, and make it work properly.