No problem @AgedLace I've gone through my old text book "Problem Solving Using C++: Structured and Object-Oriented Programming Techniques" by Yuksel Uckan, and learned about Pseudocoding from there, within Chapter 2 Problem Solving Computers. I even wrote about it via Amazon just on that one chapter alone. Chapter 2 initially talks about about:
(5 step Method of Solution, 6 with Software Development)
- Requirement Specifications
- Design and Representation of Algorithms (where I first knew about Pseudocoding & Flowcharting)
- Testing and Verification
- Program Documentation
(anywhere in the Tier above that goes through this let me know. Otherwise I'll find out as I continue this journey.)
Even after I graduated, BMCC (a CUNY school) at the time, I remember one of my Professor's kept lecturing about how we need to go over this stuff if we are to become real programmers. He came out passionately one day when he got fed up with some knuckleheads in the class. Imagine a character from Revenge of the Nerds (pocket protector and glasses), who definitely earned my respect for that day.
This was YEARS ago and although I have not been a programmer within the field (away from working as a Litigation Support Specialist temporarily and freelancing '04-'14 (with further informal training then and now)), I've seen how technology has changed and wish to contribute. Just another reason for being here, focused on Computer Science side of it, and almost literally starting from scratch (but at an accelerated rate with hours to pinch).
Although this book is ancient (published in '99), I'm more than familiar with it's code at the time and I will implement it when time to use C++ of today (not much to change within the syntax, I think). For as I make it this go round, C++ will be kept in my tool-belt.
Back to coding.