top of page
image.png

Written by: Muthyam Geeta Sai Charan Reddy​


Reading Time: 7 min

Word Count: 989 

image-removebg-preview (2).png

published in:

Click here to go to the article page :

How a Messy Workshop Led Me to Think Like an Engineer. 

Say the words "Design and Technology project" to most people and they'll picture a student knocking something together for marks. That's honestly how I saw it too, at first  design something that works, build it, write it up, hand it in.

That's not how it went.

It started with something so ordinary I almost didn't notice it was a problem at all. Every single D&T lesson began the same way. Someone hunting for a screwdriver. Someone else convinced a chisel had vanished into thin air. Our teacher usually ended up rifling through three or four different cupboards trying to find whatever had gone missing, half convinced it was hiding in the wrong drawer the whole time.

I didn't think much of it for the first few weeks  you get used to that kind of background noise pretty fast in any classroom. After the third or fourth time watching the same scramble, I stopped shrugging it off and started asking why nobody had just fixed it.

So instead of churning out another stool or shelf nobody would remember, I went after the thing that actually annoyed me.

 I wanted the workshop itself to be less of a mess. Looking back now, that was probably the first time I approached anything the way an engineer would  not jumping straight to a solution, but sitting with the problem long enough to actually understand it.

 

The first thing I had to admit was that I didn't really know why the workshop was such chaos I just assumed I did. So I watched. I paid attention to how people actually used the storage that already existed, asked the teachers what bothered them most, noticed which tools got grabbed constantly and which ones sat untouched. It wasn't a shortage of drawers, as I'd first guessed. The organiser that was already there simply hadn't been designed with any of us in mind.

Tools were shoved into spots you could barely reach. Completely different sized items were crammed into the same space. Small parts got swallowed by oversized compartments, and some of the heavier power tools made certain drawers nearly impossible to pull open. There was no real logic to any of it, so naturally everyone put things back differently  assuming they put them back at all.

At that point the project stopped being about a storage box and turned into something closer to a system.

Before I sketched a single line, I measured almost every tool that would eventually live inside it. Length, width, height, over and over, tool after tool  not exactly thrilling work, but it turned out to matter more than almost anything else I did. Those numbers decided how big every drawer and compartment needed to be. Get them wrong and the whole thing falls apart later, no matter how good the design looks.

That was the point where it hit me: a huge amount of engineering happens before you've built anything at all.

Once I had enough measurements, I moved on to sketching, and my first ideas were, predictably, not great. One version looked sleek but would have cost far more than made sense. Another had plenty of storage but ate up half the workshop. A third crammed in so many drawers it ended up heavier and clunkier than it needed to be. Each one seemed fine on paper until I actually sat with it for a while and the cracks started showing.

Rather than stubbornly forcing one of those designs to work, I just kept revising. I used to assume good designers nailed it on the first attempt  this project talked me out of that pretty quickly. Every version I threw out taught me something the last one hadn't, and the improvement came less from a flash of insight and more from being willing to admit the current version wasn't good enough yet.

Eventually I moved from paper to SketchUp, and that's when the whole thing started to feel real for the first time  I could finally spin it around and look at it from angles I hadn't even considered while sketching.

The CAD model was brutal about exposing flaws my sketches had quietly hidden. A couple of drawers would have collided with each other when opened. Some compartments turned out too small for what they were meant to hold. The whole unit was noticeably bigger than I'd pictured it. Seeing it in three dimensions forced a shift in how I thought about the whole project. Something can look perfectly reasonable on paper and still be unbuildable in practice.

Oddly, finding these problems didn't frustrate me the way I expected. Every flaw I caught on a screen was one I wouldn't have to discover halfway through building the real thing.

As the design matured, I started noticing details I'd never have thought twice about before. Material choice turned into its own small research project plywood against MDF against hardwood, weighing up strength, weight, cost, how easy each one actually was to work with. Since this thing was going to get dragged around the workshop daily and loaded with heavy tools, it needed to be sturdy without turning into something nobody wanted to move.

I also went down a bit of a rabbit hole on joints and shelving methods. I'd assumed, going in, that joining wood together was more or less straightforward. It isn't. Every joint I looked at came with some trade-off baked in stronger ones that took forever to make, faster ones gave something up in rigidity.And whatever I picked there ended up messing with something else down the line, every single time.

I didn't see this coming, but by the end of it I just didn't trust the word "perfect" anymore, not really. What I trusted instead was knowing which compromise I could actually live with, and being able to say why, if someone asked me.

Muthyam Geeta

            Sai Charan Reddy 

123-456-7890

500 Terry Francine St. San Francisco, CA 94158

  • Instagram
  • Facebook
  • LinkedIn

Connect with Me

© 2035 by C. Lee. Powered and secured by Wix 

bottom of page