717
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 10 Mar 2026
717 points (100.0% liked)
Technology
85543 readers
2958 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
I read it as "now a senior developer will be at fault for all AI code." Do you think they will have time to review all that code properly and do their jobs.
One of my first big jobs at NASA was as a lead engineer on a multi-experiment platform to fly on the space shuttle. I checked all the work and compiled all the data and trotted my 27 year old self down to Johnson to present my case to the Safety Board. When I stood up to present, the head of the panel asked if I knew why I was there. I confidently told him that I was there to walk them through my evaluation of each of the payload components and show that the payload was safe to fly. He smiled. He then said "You're here because if something goes wrong on this mission, there had to be one ass to kick. Proceed."
Everyone needs an ass to kick, and AI doesn't offer that function.
That sounds like an almost refreshing "you're one of us now / welcome to the real thing" type of brutal honesty.
Did it have a friendly tone and/or serve as an ice breaker before your presentation?
Sorry for the necro reply, been away for a but. It was a great icebreaker, actually. Still a little nerve-wracking given it was my first presentation outside of my directorate, but it was clear that this was a no-bullshit zone.
If you've seen NASA-related movies like The Martian, Apollo 13, or Hidden Figures the portrayal of the enthusiast/no-bs engineers and managers is actually true. There's no tiptoeing around or "whistling through the graveyard" - you see a problem, you talk it out. And it can get animated. But I can only think of a handful of cases where things ended in an impasse because we had the (math/science) resources to make sure things were right. Obviously that doesn't mean failures don't happen, but it really fine tuned the way I approach engineering problems to eliminate as many failure modes as was practical.
thanks!
They will save time by making them go pee in bottles
The preview for the reply notification for this comment started getting my brain so excited when my eyes scanned over the beginning. Screen grab: