Other Software Engineering Useful Topics

UI Design

Credits for the videos and slides go to Eric Paulos' Fall 2020 CS 160

Access CS 160 Lectures 2 and 7 here: https://drive.google.com/drive/folders/1F7Hp89Kc48oAi7vOcr8JPZPJ-GMJ2wkm

The Design Cycle

• Lecture 2: Start to 46:16, skip “Announcements” at the beginning
• Slides link: http://teaching.paulos.net/cs160_FL2020/lectures/cs160-fl20-02.pdf

Heuristic (Design Severity) Evaluation

• Lecture 7: 22:30 to end, but ignore User Testing
• Slides link: http://teaching.paulos.net/cs160_FL2020/lectures/cs160-fl20-07.pdf

Good SWE Practices

Rubber Ducky Debugging

• Wikipedia Article Link: https://en.wikipedia.org/wiki/Rubber_duck_debugging
• Purpose: Force yourself to explain your code and why it works
• You don’t need a Rubber Duck
  • Any inanimate object

Planning out your code

• Remember: Code is just a formalized language of Logic!

• Move away from code, make sure the Logic is right first!

• Use Paper Brainstorming (inspiration from writers)

  

Memory is Volatile

• short-term memory - process that involves remembering bits of data for just a few seconds
• More here: https://bebrainfit.com/short-term-memory-loss/

Documenting your Code

• Inspiration from History:
  • We only remember the history written on paper
• Oral history is a game of telephone (e.g. lost languages)
• Helps with future officer cores iterations to know what has been done
• Helps you to know what needs to be done in English first before formal (Django) code

Consult with Others

• You are not alone!!!!!!

• There are other people to help you and talk to

• Do not be shy to reach out!