Shiiieeettt.......

A gun that shoots eagles, obviously

Step clap step step clap

The Intuitive Machines lander issue was that no one disarmed the safety switch on the laser guidance system. (No, really!) Luckily NASA had a backup system installed that ended up working better anyway.

Pound-seconds wouldn't be a force, but i looked and it seems there is pound of force or pound-force, lbf, wich is a unit of force, i guess that's it.

Technically the US measurement system is metric since the Mendenhall Order of 1893 reestablished all customary units as conversion factors of metric units. In 1933 the ASA redefined the inch to be exactly 25.4mm, following the lead of the British Standards Institution in 1930 (precision was increasingly important for manufacturing, and the previous value of 25.40005mm had become impractical). The international yard and pound were officially adopted by the US National Bereau of Standards (now NIST) in 1959, the Metric Conversion Act was passed in 1975, and finally EO 12770 (1991) required all agencies of the executive branch to transition to metric units.

So, from one point of view we've been transitioning to metric since 1893 and it's still not done. From another, the inch is just a metric unit as its length is officially defined in millimeters (all customary units are now based on SI units), therefore the conversion is complete.

It was intended to be an orbiter.

A free for all, late Friday deployment is baffling… We’ve got a strict window of Tuesday-Thursday for releases (unless it’s a critical issue), and a 2-3 day merge freeze to help mitigate unexpected changes.

We’ve got a relatively small team with LOTS of moving parts, so minimizing deployment issues is always top of mind.

I literally know multi billion dollar B2C startups doing the same. It's got so toxic that the management regularly fires people and to fill their spots, they offer obscene amounts of money just for starter positions.

That's no longer a technical process issue but more of a teamcoach/HR kind of issue then. You should be able to assume good intentions from colleagues, imho.

We use a CI pipeline check which prevents merges to master if the code contains a TODO. A precommit hook only works if the developer has the hooks configured.

Golang won't even compile with dead code. Unfortunately that's too strict, you just end up commenting out the whole block instead. At least the commented out code is obvious in review, and some automated checks catch it if you have them.

implying that any developer actually reads warnings

Woah woah WOAH WOAH.

So you're saying software for the Artemis landers aren't being built with the latest TypeScript compiler and running on a canary version of v8?!

The test release shouldn't have anything marked with @nocommit though... The idea is that you use it to mark code that is only temporary local debugging code that should never be committed.

Final flight checks:

"It's off, so I turn it on and .... WALK AWAY!"

That requires someone to look at that section in the IDE. If it doesn't block the merge, it doesn't do shit.

Yeah, gVim is pretty great, isn't it? :-P

On the one hand: kind of sad since this isn't too far removed from some workplaces. The hardware and furniture could be sourced from any number of places.

On the other: hot damn. We can get the same kit NASA uses at home. Welcome to the future.

That's what i meant, all software and plugable devices now. Those desks were prohibitively expensive.