What makes good pseudocode before you write real code?

Good pseudocode

• Name inputs/outputs and edge cases upfront.
• Use plain English loops—no syntax errors needed.
• Mark invariant: "window always valid", "left sorted".
• Translate to code section by section.

// Pseudocode → Java sketch
// for each right index r:
//   expand window; while invalid shrink left
// return best