Anyone else surprised by how improvised engineering actually is?

Nov 21, 2026 Last reply: 13 hours ago 7 Replies

First reply

PineWorks640

What you're describing matches what I saw at my first job out of school. I walked in expecting clean documentation, tight change control, and managers who understood the technical work. Instead I found spreadsheets only one retiring guy knew how to read and decisions made in…

Read the full reply

On my second internship now, this time at a way bigger company than my first one, and it's alot more office work too. What's cracked me up is seeing how much of it runs on patchwork fixes that were never meant to be permanent, with people steering the ship who honestly seem to be winging it. And still, everything somehow functions. Well, sort of.



I sort of suspected this before, but watching it up close has been funny. As a kid I figured engineering was this polished world for geniuses with rigid processes and everything locked down. Turns out it feels more like everyone's just coasting toward Friday afternoon and calling it a system.



So I'm curious where others land on this. Is the improvisation actually a feature, like temporary fixes are just how big orgs stay flexible? Or is it a slow rot that only hasn't bitten yet becuase things take years to fail? Would love to hear from people who've been inside real companies longer than I have.


What you're describing matches what I saw at my first job out of school. I walked in expecting clean documentation, tight change control, and managers who understood the technical work. Instead I found spreadsheets only one retiring guy knew how to read and decisions made in hallway conversations. It rattled me for about six months, then I started seeing it as the normal operating condition of any large organization rather than a scandal. The thing I'd push back on gently is the word 'winging it.' A lot of what looks like improvisation from an intern's seat is actually the residue of decisions that made sense at the time, plus a few layers of reorganization on top. The Friday-afternoon feeling is real, but underneath it there's usually more structure than it appears, just not the kind they taught us in school.

Here's the part that took me longest to accept: you can't tell from the outside which companies are competent and which aren't. The polished website and the fancy lobby tell you nothing. I've assumed a place had it together and been wrong, and the reverse too. Nobody's quarterly report admits the load-bearing spreadsheet. As for whether the patchwork is a feature or slow rot, I honestly don't know, and I've stopped losing sleep over it. I'd say watch which fixes come back around twice. That tells you more than any org chart.

I read that reply about making peace with the chaos after a few months, and honestly my reaction is the opposite of making peace. I still think the improvisation is a real feature of big organizations, but sitting back and calling it normal always felt like a cop-out to me. Somewhere in that mess is usually one person quietly holding a critical piece together, and I decided early on I wanted to be that person rather than shrug at it. What worked for me was writing things down as I found them. Whenever I inherited a spreadsheet or a process only one person understood, I kept my own notes on how it fit together. Nobody asked me to. It slowed me down at first, and it was boring, but it meant that when someone walked out the door or retired, the knowledge did not leave with them. I would say to you that as an intern you are in a strange sweet spot. You have fresh eyes and nobody expects you to know the history, so asking why a fix from years ago is still in place costs you nothing. Some of those answers will be genuinely good reasons. Some will be silence and a shrug, which tells you something too. So my answer to your question is that it is both flexible and rotting at the same time, and the difference usually comes down to whether anyone bothered to write the patchwork down. Did your current company have any onboarding documents at all, or were you handed a login and left to it?

To be pedantic about one phrase you used, I'd argue the duct tape metaphor undersells it slightly, because actual duct tape has a known failure mode and a rough service life, whereas the corporate equivalent tends to get load-bearing the moment nobody writes down what it was patching. I'm a hobbyist who reads engineering history for fun, and the pattern shows up there too, where a wartime stopgap or a quick revision ends up in production for decades because it worked well enough and nobody wanted to touch it. Which makes me lean toward your second option, the slow rot one, except rot implies decay and these patches often get stronger with tenure. Curious whether your bigger company has anyone whose actual job is to go back and replace the temporary fixes, or whether that person exists only in job postings.

The kid-version expectation bit hit home for me. I figured the same thing growing up, that engineering offices were these gleaming labs where geniuses followed the manual to the letter. Reality check came fast for me too. What cracks me up now is that the patchwork jobs I'd be embarrassed to show anyone somehow outlast the 'proper' solutions that get replaced a year later. Maybe that's the actual answer to your question, the fixes that stick around aren't failing, so were they ever really temporary?

For me the biggest eye-opener was the leadership part, honestly. My first internship I kept waiting for some senior engineer to step in and run the show, and instead the person everyone answered to mostly handled meetings and charm while the actual numbers came from people two rungs down. Once I accepted that, the duct tape everywhere stopped bothering me so much. Curious if you've noticed that at the bigger company too, whether the schmoozers outnumber the technical folks.

That bit in the longer reply about not being able to spot a competent company from the outside is dead on for me too. I picked a job once mostly because the place looked sharp and established, and it was just as much patchwork inside as anywhere else. Had the reverse happen as well, so I stopped trusting appearances. Do you think you'd have guessed your two internship companies were that different from the outside?

Update: still chewing on the reply that called out my duct tape comparison, the bit about a patch going load-bearing the second nobody writes down what it was holding. That stuck with me. So new question: if undocumented fixes are the real danger, how do you even start untangling something like that when you're just an intern? Do you ask, or stay quiet and take notes?

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required