95

So, I'm programming a control system for a prototype aerospace vehicle. You know, the stuff that needs to work to prevent falling out of the sky.

Anyway, test day was today (was -- not anymore). Wiring all the electronics, everything is actuating and works well. Except for one part, a little thruster for stability.

I spent hours - literally, fucking hours - trying to fix the problem. Wrong address? Wrong syntax? I had absolutely no clue what was wrong. Queue the hardware guy, $stupid:

$stupid: "How have you not got it working yet?!"

$me: "I don't know, everything I'm trying isn't working. I've spent hours digging through this code and nothing is fucking working."

$stupid: "Well have you set it up for the new thruster?"

$me: "What...What new thruster?"

$stupid: "Oh, the one we installed this morning, did noone tell you?"

WHY WOULDN'T YOU TELL ME THIS?! COMMUNICATION 101!

Comments
  • 6
    how do you keep cool in the face of such shit.
  • 8
    Hope the rest of the test flight went well, though!

    Oh and welcome to devRant :)
  • 1
    @nitaj96a what specifically do you want to know?

    I work on a prototype lunar lander, so it's a lot of PID, Kalman filters and sensor fusion. It's written mostly in C, with numerical simulations done in MATLAB and FORTRAN. It's very mathematics and optimisation-heavy -- lots of nonlinear control and differential equations.
  • 0
    Working at spacex sounds pretty shit
  • 0
    @tylerjackoliver where do you work? Sounds like you have a kickass job.
  • 0
    You should ask Elon Musk to fire the fucker!
Add Comment