About 'Pseudocode Programming'!

  • More on Pseudocode Programming Practice (PPP)
  • Reviewing our code and architecture
  • Using // TODO as a comment prefix
  • Introducing Visual Studio’s Task List
  • Planning our next wave of coding.

(Unique Video Reference: 21_BC_URC)

We would love to know…

  • What you found good about this lecture?
  • What we could do better?

Remember that you can reply to this topic, or create a new topic. The easiest way to create a new topic is to follow the link in Resources. That way the topic will…

  • Be in the correct forum (for the course).
  • Be in the right sub-forum (for the section)
  • Have the correct lecture tag.

Enjoy your stay in our thriving community!

1 Like

Hello @sampattuzzi and dear Community,

everything until now is fully clear and understandable to me. The hint will the “// TODO”-comment and the linked task-list is very helpful. I like to get more of those handy tips.

Kind regards
Kevin

1 Like

IMO I found sections 30 - 37 a bit loose in terms of explanations about why you would need classes and how they should be implemented. I think seeing the project a bit further along would better illustrate how these items are being used.

Maybe @ben wants to take this into account in the remaster.

Thanks for the heads-up, also looping-in @GavinMilroy

Privacy & Terms