This one got a giggle out of me!
I meant to post this in the Funny thread. I blame it on being old. I made mistakes like this when I was younger, but now I have something to blame it on.
Good to know you’re working on your positive post.
And like magic, it appears where it belongs.
Good luck maintaining that one.
Three engineers are riding in a car: a mechanical engineer, an electrical engineer, and a software engineer.
Suddenly, the car breaks down on the side of the road.
The mechanical engineer says,
“It must be a problem with the engine or the transmission. Let’s pop the hood and take a look.”
The electrical engineer says,
“I think it’s the battery or maybe the alternator. We should check the wiring.”
The software engineer says,
“Let’s all get out of the car, close the doors, wait ten seconds… and then get back in and see if it works.”
Why did the engineer break up with SolidWorks?
Because every time they tried to move on, it said “Fully Defined Relationship!”
Wait, wouldn’t that be “Under Defined”?
A mechanical engineer walks into a bar, looking absolutely exhausted.
The bartender asks, “Rough day at work?”
The engineer sighs, “You ever try dating SolidWorks?”
The bartender laughs, “Nope, can’t say I have.”
“Well, I thought we were getting along great,” the engineer says, slumping into a stool. “Things were smooth at first—sketches lined up, mates were clicking, assemblies coming together…”
“So what went wrong?”
The engineer gulps their drink. “I tried to make a small change. Just one. Suddenly, everything exploded. Parts were flying off the screen, constraints were screaming, and the entire assembly went into therapy.”
The bartender chuckles. “Sounds dramatic.”
“Oh, it gets better,” the engineer says. “SolidWorks sent me a message: ‘Overdefined relationship.’”
“Dang.”
“And when I tried to fix it, it ghosted me—crashed without warning and didn’t even save our last conversation.”
The bartender shakes his head. “Sounds toxic.”
“Tell me about it,” says the engineer. “I miss AutoCAD. At least with them, we knew it was just casual.”
An engineer proudly shows his friend his latest SolidWorks model.
Friend: “Wow, that looks complicated! How long did it take?”
Engineer: “About 3 hours.”
Friend: “That’s impressive!”
Engineer: “Yeah… but then I spent the next 5 hours trying to fix the mates because the model was having an identity crisis.”
Friend: “Identity crisis?”
Engineer: “Every time I change one part, the whole thing decides to rebel. It’s like trying to convince a toddler to wear matching socks.”
An engineer calls tech support.
Engineer: “My SolidWorks assembly won’t rebuild.”
Tech Support: “Did you try turning it off and on?”
Engineer: “Yes.”
Tech Support: “Okay… is your computer plugged in?”
Engineer: “Yes…”
Tech Support: “And you saved your work before this happened?”
Engineer: “…No.”
Tech Support: “That’s the problem. SolidWorks isn’t a mind reader. Yet.”
A military veteran walks into his new engineering job, sits down, and opens SolidWorks for the first time.
After about five minutes, he yells across the office:
“Hey—why does this program keep telling me to start an assembly? I’ve been to enough of those to last a lifetime!”
His coworker laughs and says, “Don’t worry, in SolidWorks you don’t have to stand at attention.”
The vet nods. “Good, because last time someone said ‘mate the parts,’ it wasn’t HR-approved either.”
I overheard this at lunch today.
Did you see the odds on the horse that won the Kentucky Derby? 23:1. I wish i had put $1000 on him last week. I would have, like, $100 grand now.
The Mission Brief
A veteran sits down to use SOLIDWORKS for the first time.
Before touching the mouse, they read the entire feature tree, check every constraint, and make sure the planes are aligned.
Someone asks, “You gonna start modeling?”
The veteran replies, “Not yet. I’m reviewing the mission, identifying dependencies, and confirming there’s a clean exit strategy.”
Thirty minutes later, they build the part perfectly—no errors, no rebuild warnings.
Turns out SOLIDWORKS isn’t that different from the military:
Plan first, execute once, and don’t ignore your constraints unless you want trouble later.
TLDR: SNFAU