I’m realizing I’ve learned quite a bit over the last year and a half. I had very little Objective-C experience (not to mention Cocoa) when I started and just yesterday I realized I could have made a much better architecture choice in my code. Going back to some of the original code is kinda painful sometimes, but it all works just fine.
One major feature I added is a visual one:
Cel-style outlines on the basic stage geometry.
My last post is a bit painful to read. Soon after that elated optimism I had to do some deep digging into my code.
This is me in July(!):
The technical stuff is almost completely over with: one gameplay glitch to tidy up — not a show stopper — and a few more sound effects to shoehorn in.
So that glitch wasn’t the only one, and that glitch did stop the show for a while. Ah, innocence.
Pseudocode is meant to be a way to quickly sketch or communicate how a coding problem could be solved. It’s not a real programming language, but usually resembles the language one is targeting.
Well, I’ve been teaching a class based on a book that takes the approach of learning the fundamentals of programming by focusing on pseudocode. It’s a mixed bag. Yes, a lot of complexity is avoided so students can focus on the logic rather than syntax, but there is no way to test it. It all feels abstract and theoretical.