On teaching: Opinion page of a mildly disgruntled university student
Teaching materials
- Cite sources on slides. I do not want to spend my time figuring out whose's slides you ripped off or from which book you took that particular figure. Whatever you copied is likely incomplete or out of proper context, and I may want to take a look at the original thing. Then there's of course giving credit to the original source.
- If you do not like something on your slides, do not apologize for it, change it!
- Slides with white background and dark text / figures are more easily printed. Please do away with "gradient" backgrounds and the like.
- Organized slides make the material easier to follow. Number your lessons and headings, use different styles for headings and sub-headings etc. It is hard to piece this together when you do not yet understand the topic.
- Animations can be great on certain ocassions, just make sure something intelligible results when you export to PDF!
Technical language
- Especially for those for whom english is not their native tongue, please use the appropriate technical jargon for the subject you are teaching. A couple mistakes or mispronuntiations here and there do not matter as long as you get your point across, yet getting jargon right is a must on technical courses.
Examples:
- voltage fall drop
- charge porters carriers
- jump step response
- industry tendencies trends
- A pronuntiation pet peeve: Aliasing is pronounced ay-li-ah-sing not a-lay-a-sing.
Evaluation
- Feedback, and timely feedback that is, is invaluable. Students tend to want more that a number three weeks after the final exam. I want to know how I did on that last report so I don't make the same mistakes again.
Course organization
- Most courses I waded through suffered from an increasing workload as the semester progressed. While it is true that some practical material cannot be tackled before some theory classes, some homework and deliverables can be handed out earlier.
On coding practices
HDLs
- Please follow some naming convention with active low signals, e.g., ending in "_n", and stick to it.
- When your "design intent" is that something happens when this OR that signal is active, use an OR operator. That is, even if !(a_n & b_n) is equivalent to (!a_n | !b_n) they do not convey the same meaning to the reader.
Random tips
These are some reminders, mainly for my own use.
How to paste Inkscape SVGs into Microsoft Word preserving arrow formating:
1. Draw your figure on Inkscape
2. Export said figure to PDF
3. Import PDF back to Inkscape
4. Copy and paste from Inkscape to Word
5. Profit
This has something to do with svg standard and marker settings (arrows for example).
Note: It helps to export figures to PDF individually, because it may mix them together (as in joining text boxes for example) when you import them back.
Note 2: https://superuser.com/questions/1709965/pdf-export-from-word-changes-line-width-of-thin-lines-in-embedded-svg
From Microsoft PPT to Microsoft Word, so figures can be scaled without moving things around:
Copy from PPT, paste on Inkscape. Paste back to Word from Inkscape.
Stroke to path helps with getting rid of some fonts that may misbehave.
Kicad Libraries
On Kicad 7.0
Symbol editor > Create new libray > Project: Creates kicad_sym file
-Import/create symbols in symbol editor
Footprint editor > Create new library > Project: Creates .pretty folder
-Import/create footprints in footprint editor and save them to library
Comments
Post a Comment