Resources that you may find useful

Ethics Resources

• ACS Code Professiona Ethics
• ACS Code of Professional Conduct
• Alex Reid's Ethics of Computing Resources page and in particular his extensive ethics of computing bibliography
  Alex has added a summary of data from the class surveys, 2004-2021.

• Link to the 2024 Ethics Class Survey

• Eophea 2001 paper by Fialho (Including cover piece by the then Vice Chancellor)
• UWA Code of Ethics and Code of Conduct

• Guidelines on Conduct in the Workplace
• Sexual Harassment
• Charter of Student Rights and Responsibilities
• Equity and Diversity, including UWA Ally Network
• A flowchart on what is, and what is not "mansplaining", by Kim Goodwin @kimgoodwin"
  Mansplaining is where someone, often male, "explains" something in a manner that is demeaning to the recpient.

CITS3200 Specific Computing Resources

• An introduction to GitHub and Git
• Lecture by David Glance introducing Git (49MB file)
• These are the slides accompanying David Glance's introduction to Git
• Markdown is a simple type-setting system that is widely use for documentation and on the Web. For example, Markdown can also be used to produce nicer looking postings on hel3200. Markdown Basic Syntax guide is a nice cheat-sheet. Implementations include the web implementation Dillinger and the Pandoc document format converter.

• Some thoughts by John Wiese on different project management tools
• Thoughts on VLC and being a developer
  Jean-Baptiste Kempf is the president of VideoLAN and a lead developer of the open-source media player VLC. In this YouTube interview he talks about VLC, why they have kept it open source and free of charge. He talks about the importance of programming for maintainability as developers come and go. he also talks about what he looks for in a developer: that they have the interested to understand the context in which they are working.

• 10 Signs you suck at programming
  While the title is deliberately provocative - 10 signs you will suck as a programmer - the piece also says what you can do about it, and is ultimately very positive; if you do these things you will likely succeed, and be a productive software-engineering team member.

• A nice discussion of collaboration tools
  The article is about collaboration tools for teams of scientists, it applies equally to software engineering teams. Indeed, given the multiple things we all juggle, some of these tool are potentially useful for your own projects.

• Project tracking/task allocation with Trello.
  Over the past couple of years, different CITS3200 Project Teams have found Trello to be very useful, helping the team to keep track of the different threads in the projecct, who is doing what, etc.

Writing Resources

• The UWA service StudySmarter has nice (and short) guide to writing reflections.