Developers should do this, in this order:

• Research how LLMs work. This doesn't take long, there are many videos on youtube that describe how LLMs produce code. In 30 minutes you can have a pretty good understanding of how your prompt becomes code.
• Once you know how LLMs work, decide whether you want to produce code generated by the next most likely token (usually a word - a bit of language syntax), based on code that the LLM has seen before.
• If you decide to go ahead then check what the LLM tells you until you've established some knowledge around how often it can be trusted.
• Decide whether or not to continue based on how much of the generated code needs to be rejected, or fixed, or re-prompted

That's it. My trials revealed that LLMs (all of them) produce sufficiently high levels of garbage that I won't use them at all but depending on what kind of development you are doing your mileage may vary!

PYRAMID has been developed by the UK Ministry Of Defence to provide a consistent approach to modularising air system application software though the PYRAMID Reference Architecture (PRA).

The PRA encourages the well established software design principles of low coupling and high cohesion. Separation of concerns makes for reusable software components, and in an industry like aerospace being able to reuse software can have massive savings in time and money.