Nah, don’t blame it on the sunshine, don’t blame it on the moonlight. Blame it on the boogie.

Several models of helicopters have ejectable blades, this article mentions a few, and has a diagram of the blade severing system.

Dude, what are you actually trying to make right now? Like, this isn’t flight sim stuff anymore.

It’ll only be done when you can get out of your plane, walk around, find a computer and start playing Flight Simulator 2024.

H.A.R.M - High-speed Anti Radiation Missile.

Basically, rather than having it’s own radar to track a target, or using IR sensors, it locks on to a target emitting lots of radio noise such as an enemy radar or jammer.

I like it, this is clearly very enterprisey and solution focused, but I would like to suggest a couple of amendments if I may?

• Namespaces We should make full use of namespaces. Make the structural tags be in a language specific namespace (to be referenced in every function spec, obviously) but change the in an out params to use the parameter name as the tag, namespaced to the function they’re for, with a type attribute.

• In memory message queues Have all function invocations be marshaled as xml documents posted to an in memory message queue. Said documents should use a schema that validates the structure and a function specific schema to validate the types of arguments being passed. Namespace everything.

I reckon we could power a medium sided country if we could generate energy from the programmers despair.