Organizational tweak to guide
This commit is contained in:
parent
4df8521c58
commit
23e712fda3
1 changed files with 3 additions and 3 deletions
|
@ -1,11 +1,11 @@
|
||||||
# NASA-style Programming for C#
|
# NASA-style Programming for C#
|
||||||
|
|
||||||
I asked the AI to write their [NASA-style](https://en.wikipedia.org/wiki/The_Power_of_10:_Rules_for_Developing_Safety-Critical_Code) [coding instructions](Powerof10PPrompt.txt) in the form of guidelines. I figured I'd use C# since it's both my preferred language and the syntax should be fairly easy to grasp once you understand the basics.
|
I asked the AI to write their [NASA-style](https://en.wikipedia.org/wiki/The_Power_of_10:_Rules_for_Developing_Safety-Critical_Code) [coding instructions](Powerof10PPrompt.txt) in the form of guidelines. I figured I'd use C# since it's both my preferred language and the syntax should be fairly easy to grasp once you understand the basics.
|
||||||
|
|
||||||
Why NASA? Their coding standards have loads of redundancies, and if AI is going to behave like advanced code generation tools, they need to be as fault-tolerant as possible. While my instructions were modified to account for modern languages, the principles are still the same.
|
|
||||||
|
|
||||||
My only request was to apply .NET 6's [top-level statements](https://learn.microsoft.com/en-us/dotnet/csharp/tutorials/top-level-statements) for brevity. Aside from a few organizational tweaks with the guidelines and fixing the scope example to be wrapped in a class, it all works flawlessly.
|
My only request was to apply .NET 6's [top-level statements](https://learn.microsoft.com/en-us/dotnet/csharp/tutorials/top-level-statements) for brevity. Aside from a few organizational tweaks with the guidelines and fixing the scope example to be wrapped in a class, it all works flawlessly.
|
||||||
|
|
||||||
|
Why NASA? Their coding standards have loads of redundancies, and if AI is going to behave like advanced code generation tools, they need to be as fault-tolerant as possible. While my instructions were modified to account for modern languages, the principles are still the same.
|
||||||
|
|
||||||
## 1. Write Clear, Well-Structured, and Maintainable Code
|
## 1. Write Clear, Well-Structured, and Maintainable Code
|
||||||
|
|
||||||
- Keep the code simple and coherent. Use meaningful identifiers and limit the complexity of expressions.
|
- Keep the code simple and coherent. Use meaningful identifiers and limit the complexity of expressions.
|
||||||
|
|
Loading…
Add table
Reference in a new issue