• 6 Posts
  • 39 Comments
Joined 1 year ago
cake
Cake day: April 4th, 2025

help-circle

  • Yes, the blog and its sources explain in depth that this is not caused by individual faulty engineering decisions but by the security culture of the organization and the culture and incentives driving it.

    For example, the decision to not test the heat shield in full tests under real conditions, and to not make full physics models of the processes in it are mayor decisions. And the decision to make a crewed flight without these tells a lot about values and priorities.










  • I would agree with that.

    Especially, “being 70%” finished does not mean you will get a working product at all. If the fundamentale understanding is not there, you will not getting a working product without fundamental rewrites.

    I have seen code from such bullshit developers myself. Vibe-coded device drivers where people do not understand the fundamentals of multi-threading. Why and when you need locks in C++. No clear API descriptions. Messaging architectures that look like a rats nest. Wild mix of synchronous and async code. Insistence that their code is self-documenting and needs neither comments nor doc. And: Agressivity when confronted with all that. Because the bullshit taints any working relationship.