Re: Blueprint?
"is there a course I can go on to learn how to "pore over software blueprints"?"
I once went for a job interview at a mechanical engineering company that was dipping a toe in computer controlled instrumentation.
The programs were documented on flowcharts drawn by draughtsmen on A0 sheets because that was what fitted the document archive. A single code point change could take weeks to implement. That's what I call firmware.
Did not get job, should not have laughed when shown flowcharts.
Biting the hand that feeds IT
