The Technical Specification should contain
-
Actual Code
-
Pseudo Code
-
General Code
-
No Code
Technical Specifications contain pseudo-code which describes the logic and algorithms to be implemented without actual syntax. This allows developers to understand the intended functionality while implementation details are left to the coding phase. Actual code belongs in development, not specifications.
A Technical Specification document should contain pseudo code — a structured, language-agnostic description of the logic/algorithm — so developers understand the intended design without the document being tied to (or duplicating) actual implementation code. "Actual Code" is wrong because tech specs precede coding and shouldn't hardcode a specific implementation. "General Code" is not a standard artifact type. "No Code" is too extreme — some structured logic description (pseudo code) is expected to convey design intent clearly.