mirror of
https://github.com/jackyzha0/quartz.git
synced 2025-12-24 05:14:06 -06:00
update
This commit is contained in:
Jet Hughes
parent
d5ef674f8c
commit
0324a7cb71
@ -20,6 +20,9 @@ title: "Jet Hughes"
|
||||
|
||||
# 5 Independent Learning
|
||||
- [networks](notes/networks.md)
|
||||
- [philosophy](notes/philosophy.md)
|
||||
- media
|
||||
- [philosophize-this](notes/philosophize-this.md)
|
||||
- random
|
||||
- [propogation-of-ideas](notes/propogation-of-ideas.md)
|
||||
- [model-view-controller-pattern](notes/model-view-controller-pattern.md)
|
||||
@ -27,3 +30,4 @@ title: "Jet Hughes"
|
||||
|
||||
# 6 Books
|
||||
- The book of illusions
|
||||
- the story of man
|
||||
|
||||
@ -10,9 +10,9 @@ SP500 : 4057.84
|
||||
TSLA : 707.73
|
||||
|
||||
## Today
|
||||
- [ ] 09:00 Cosc202 Lab
|
||||
- [x] 09:00 Cosc202 Lab
|
||||
- [ ] 11:00 Cosc201 Lecture
|
||||
- [ ] 12:00 Info201 Lab
|
||||
- [x] 12:00 Info201 Lab
|
||||
|
||||
# Review
|
||||
```dataview
|
||||
@ -21,19 +21,11 @@ list from #lecture where sr-due = date(today)
|
||||
|
||||
## Backlog
|
||||
- [ ] 11:00 Cosc202 Lecture
|
||||
- [ ] 12:00 Cosc201 Lab
|
||||
- [ ] 12:00 Info203 Tutorial
|
||||
- [ ] 16:00 Info201 Lecture
|
||||
- [ ] 16:00 Cosc201 Tutorial
|
||||
- [ ] 11:00 Cosc201 Lecture
|
||||
- [ ] 13:00 Info201 Lecture
|
||||
- [ ] 14:00 Cosc202 Lab
|
||||
- [ ] 11:00 Cosc202 Lecture
|
||||
- [ ] 12:00 Cosc201 lab
|
||||
- [ ] Cosc201 Lab 12
|
||||
- [ ] Cosc201 follow up email about labs
|
||||
- [ ] Info201 Lecture 22 performance and security
|
||||
- [ ] Info201 Lab 7
|
||||
- [ ] Info201 Lecture 14 activity and state diagrams
|
||||
- [ ] Cosc202 Lecture 21 optimisation
|
||||
- [ ] Cosc202 Lab 19
|
||||
|
||||
40
content/daily_notes/2022-05-29.md
Normal file
40
content/daily_notes/2022-05-29.md
Normal file
@ -0,0 +1,40 @@
|
||||
[2022-05-28](daily_notes/2022-05-28) << [daily-notes](notes/daily-notes.md) >> [2022-05-30](daily_notes/2022-05-30)
|
||||
|
||||
---
|
||||
# 29-05-22
|
||||
[Mermaid Avenue - Billy Bragg](spotify:album:0yTmT1i6yHb5EVyJOmIwGw)
|
||||
|
||||
|
||||
|
||||
AAPL : 149.61
|
||||
SP500 : 4158.24
|
||||
TSLA : 759.63
|
||||
|
||||
## Today
|
||||
|
||||
|
||||
# Review
|
||||
```dataview
|
||||
list from #lecture where sr-due = date(today)
|
||||
```
|
||||
|
||||
## Backlog
|
||||
- [ ] 11:00 Cosc201 Lecture
|
||||
- [ ] 11:00 Cosc202 Lecture
|
||||
- [ ] 16:00 Info201 Lecture
|
||||
- [ ] 11:00 Cosc201 Lecture
|
||||
- [ ] 13:00 Info201 Lecture
|
||||
- [ ] 11:00 Cosc202 Lecture
|
||||
- [ ] Info201 Lecture 22 performance and security
|
||||
- [ ] Info201 Lecture 14 activity and state diagrams
|
||||
- [ ] Cosc202 Lecture 21 optimisation
|
||||
- [ ] Cosc202 Lab 19
|
||||
|
||||
## Projects
|
||||
- python ai weekly review
|
||||
- spotify clone
|
||||
|
||||
## Links
|
||||
- [202 lab book](C:\Users\Jet%20Hughes\Documents\Personal\COSC202LabBook-2.pdf)
|
||||
- [i201 cousework](https://isgb.otago.ac.nz/infosci/INFO201/labs_release/raw/master/output/info201_labs.html#)
|
||||
- [i201 Assignments](https://isgb.otago.ac.nz/info201/shared/assignments_release/raw/master/output/info201_assignments.html)
|
||||
41
content/daily_notes/2022-05-30.md
Normal file
41
content/daily_notes/2022-05-30.md
Normal file
@ -0,0 +1,41 @@
|
||||
[2022-05-29](daily_notes/2022-05-29) << [daily-notes](notes/daily-notes.md) >> [2022-05-31](daily_notes/2022-05-31)
|
||||
|
||||
---
|
||||
# 30-05-22
|
||||
[Selling England By The Pound - Genesis](spotify:album:2tSRe2rkdJvZWMOIZpu6lk)
|
||||
|
||||
|
||||
|
||||
AAPL : 149.61
|
||||
SP500 : 4158.24
|
||||
TSLA : 759.63
|
||||
|
||||
## Today
|
||||
- [ ] 11:00 Cosc202 Lecture
|
||||
- [ ] 12:00 Cosc201 lab
|
||||
|
||||
# Review
|
||||
```dataview
|
||||
list from #lecture where sr-due = date(today)
|
||||
```
|
||||
|
||||
## Backlog
|
||||
- [ ] 11:00 Cosc201 Lecture
|
||||
- [ ] 11:00 Cosc202 Lecture
|
||||
- [ ] 16:00 Info201 Lecture
|
||||
- [ ] 11:00 Cosc201 Lecture
|
||||
- [ ] 13:00 Info201 Lecture
|
||||
- [ ] 11:00 Cosc202 Lecture
|
||||
- [ ] Info201 Lecture 22 performance and security
|
||||
- [ ] Info201 Lecture 14 activity and state diagrams
|
||||
- [ ] Cosc202 Lecture 21 optimisation
|
||||
- [ ] Cosc202 Lab 19
|
||||
|
||||
## Projects
|
||||
- python ai weekly review
|
||||
- spotify clone
|
||||
|
||||
## Links
|
||||
- [202 lab book](C:\Users\Jet%20Hughes\Documents\Personal\COSC202LabBook-2.pdf)
|
||||
- [i201 cousework](https://isgb.otago.ac.nz/infosci/INFO201/labs_release/raw/master/output/info201_labs.html#)
|
||||
- [i201 Assignments](https://isgb.otago.ac.nz/info201/shared/assignments_release/raw/master/output/info201_assignments.html)
|
||||
33
content/daily_notes/2022-05-31.md
Normal file
33
content/daily_notes/2022-05-31.md
Normal file
@ -0,0 +1,33 @@
|
||||
[2022-05-30](daily_notes/2022-05-30) << [daily-notes](notes/daily-notes.md) >> [2022-06-01](daily_notes/2022-06-01)
|
||||
|
||||
---
|
||||
# 31-05-22
|
||||
[Eagles - Eagles](spotify:album:51B7LbLWgYLKBVSpkan8Z7)
|
||||
|
||||
|
||||
|
||||
AAPL : 149.61
|
||||
SP500 : 4158.24
|
||||
TSLA : 759.63
|
||||
|
||||
## Today
|
||||
- [ ] 10:00 Info203 Lecture
|
||||
- [ ] 11:00 Cosc201 Lecture
|
||||
- [ ] 13:00 Info201 Lecture
|
||||
- [ ] 14:00 Cosc202 Lab
|
||||
|
||||
# Review
|
||||
```dataview
|
||||
list from #lecture where sr-due = date(today)
|
||||
```
|
||||
|
||||
## Backlog
|
||||
|
||||
## Projects
|
||||
- python ai weekly review
|
||||
- spotify clone
|
||||
|
||||
## Links
|
||||
- [202 lab book](C:\Users\Jet%20Hughes\Documents\Personal\COSC202LabBook-2.pdf)
|
||||
- [i201 cousework](https://isgb.otago.ac.nz/infosci/INFO201/labs_release/raw/master/output/info201_labs.html#)
|
||||
- [i201 Assignments](https://isgb.otago.ac.nz/info201/shared/assignments_release/raw/master/output/info201_assignments.html)
|
||||
35
content/daily_notes/2022-06-01.md
Normal file
35
content/daily_notes/2022-06-01.md
Normal file
@ -0,0 +1,35 @@
|
||||
[2022-05-31](daily_notes/2022-05-31) << [daily-notes](notes/daily-notes.md) >> [2022-06-02](daily_notes/2022-06-02)
|
||||
|
||||
---
|
||||
# 01-06-22
|
||||
[New Wave - The Auteurs](spotify:album:7dJLDJkGND4ovSCRL4r4bk)
|
||||
|
||||
|
||||
|
||||
AAPL : 149.61
|
||||
SP500 : 4132.15
|
||||
TSLA : 758.26
|
||||
|
||||
## Today
|
||||
- [ ] 10:00 Info203 Lecture
|
||||
- [ ] 16:00 Cosc201 Tutorial
|
||||
|
||||
# Review
|
||||
```dataview
|
||||
list from #lecture where sr-due = date(today)
|
||||
```
|
||||
|
||||
## Backlog
|
||||
- [ ] 10:00 Info203 Lecture
|
||||
- [ ] 11:00 Cosc201 Lecture
|
||||
- [ ] 13:00 Info201 Lecture
|
||||
- [ ] 14:00 Cosc202 Lab
|
||||
|
||||
## Projects
|
||||
- python ai weekly review
|
||||
- spotify clone
|
||||
|
||||
## Links
|
||||
- [202 lab book](C:\Users\Jet%20Hughes\Documents\Personal\COSC202LabBook-2.pdf)
|
||||
- [i201 cousework](https://isgb.otago.ac.nz/infosci/INFO201/labs_release/raw/master/output/info201_labs.html#)
|
||||
- [i201 Assignments](https://isgb.otago.ac.nz/info201/shared/assignments_release/raw/master/output/info201_assignments.html)
|
||||
39
content/daily_notes/2022-06-02.md
Normal file
39
content/daily_notes/2022-06-02.md
Normal file
@ -0,0 +1,39 @@
|
||||
[2022-06-01](daily_notes/2022-06-01) << [daily-notes](notes/daily-notes.md) >> [2022-06-03](daily_notes/2022-06-03)
|
||||
|
||||
---
|
||||
# 02-06-22
|
||||
[Pink Moon - Nick Drake](spotify:album:6LoD5uGEynY4eqstWDFKhg)
|
||||
|
||||
|
||||
|
||||
AAPL : 149.61
|
||||
SP500 : 4101.23
|
||||
TSLA : 740.37
|
||||
|
||||
## Today
|
||||
- [ ] 11:00 Cosc202 Lecture
|
||||
- [ ] 12:00 Cosc201 Lab
|
||||
- [ ] 12:00 Info203 Tutorial
|
||||
- [ ] 16:00 Info201 Lecture
|
||||
|
||||
# Review
|
||||
```dataview
|
||||
list from #lecture where sr-due = date(today)
|
||||
```
|
||||
|
||||
## Backlog
|
||||
- [ ] 10:00 Info203 Lecture
|
||||
- [ ] 16:00 Cosc201 Tutorial
|
||||
- [ ] 10:00 Info203 Lecture
|
||||
- [ ] 11:00 Cosc201 Lecture
|
||||
- [ ] 13:00 Info201 Lecture
|
||||
- [ ] 14:00 Cosc202 Lab
|
||||
|
||||
## Projects
|
||||
- python ai weekly review
|
||||
- spotify clone
|
||||
|
||||
## Links
|
||||
- [202 lab book](C:\Users\Jet%20Hughes\Documents\Personal\COSC202LabBook-2.pdf)
|
||||
- [i201 cousework](https://isgb.otago.ac.nz/infosci/INFO201/labs_release/raw/master/output/info201_labs.html#)
|
||||
- [i201 Assignments](https://isgb.otago.ac.nz/info201/shared/assignments_release/raw/master/output/info201_assignments.html)
|
||||
42
content/daily_notes/2022-06-03.md
Normal file
42
content/daily_notes/2022-06-03.md
Normal file
@ -0,0 +1,42 @@
|
||||
[2022-06-02](daily_notes/2022-06-02) << [daily-notes](notes/daily-notes.md) >> [2022-06-04](daily_notes/2022-06-04)
|
||||
|
||||
---
|
||||
# 03-06-22
|
||||
[Here Are the Sonics - The Sonics](spotify:album:4vqaqoTEbNyeeSHJA6KpdM)
|
||||
|
||||
|
||||
|
||||
AAPL : 149.61
|
||||
SP500 : 4176.82
|
||||
TSLA : 775
|
||||
|
||||
## Today
|
||||
- [ ] 09:00 Cosc202 Lab
|
||||
- [ ] 11:00 Cosc201 Lecture
|
||||
- [ ] 12:00 Info201 Lab
|
||||
|
||||
# Review
|
||||
```dataview
|
||||
list from #lecture where sr-due = date(today)
|
||||
```
|
||||
|
||||
## Backlog
|
||||
- [ ] 11:00 Cosc202 Lecture
|
||||
- [ ] 12:00 Cosc201 Lab
|
||||
- [ ] 12:00 Info203 Tutorial
|
||||
- [ ] 16:00 Info201 Lecture
|
||||
- [ ] 10:00 Info203 Lecture
|
||||
- [ ] 16:00 Cosc201 Tutorial
|
||||
- [ ] 10:00 Info203 Lecture
|
||||
- [ ] 11:00 Cosc201 Lecture
|
||||
- [ ] 13:00 Info201 Lecture
|
||||
- [ ] 14:00 Cosc202 Lab
|
||||
|
||||
## Projects
|
||||
- python ai weekly review
|
||||
- spotify clone
|
||||
|
||||
## Links
|
||||
- [202 lab book](C:\Users\Jet%20Hughes\Documents\Personal\COSC202LabBook-2.pdf)
|
||||
- [i201 cousework](https://isgb.otago.ac.nz/infosci/INFO201/labs_release/raw/master/output/info201_labs.html#)
|
||||
- [i201 Assignments](https://isgb.otago.ac.nz/info201/shared/assignments_release/raw/master/output/info201_assignments.html)
|
||||
42
content/daily_notes/2022-06-05.md
Normal file
42
content/daily_notes/2022-06-05.md
Normal file
@ -0,0 +1,42 @@
|
||||
[2022-06-04](daily_notes/2022-06-04) << [daily-notes](notes/daily-notes.md) >> [2022-06-06](daily_notes/2022-06-06)
|
||||
|
||||
---
|
||||
# 05-06-22
|
||||
[All That You Can't Leave Behind - U2](spotify:album:7a5U0GPoAvT3gvEY66FRuN)
|
||||
|
||||
|
||||
|
||||
AAPL : 149.61
|
||||
SP500 : 4108.54
|
||||
TSLA : 703.55
|
||||
|
||||
## Today
|
||||
|
||||
|
||||
# Review
|
||||
```dataview
|
||||
list from #lecture where sr-due = date(today)
|
||||
```
|
||||
|
||||
## Backlog
|
||||
- [ ] 10:00 Info203 Lecture
|
||||
- [ ] 10:00 Info203 Lecture
|
||||
|
||||
- [ ] 12:00 Info201 Lab
|
||||
- [ ] 16:00 Info201 Lecture
|
||||
- [ ] 13:00 Info201 Lecture
|
||||
|
||||
- [ ] 12:00 Cosc201 Lab
|
||||
- [ ] 11:00 Cosc201 Lecture
|
||||
- [ ] 11:00 Cosc201 Lecture
|
||||
|
||||
- [ ] 11:00 Cosc202 Lecture
|
||||
|
||||
## Projects
|
||||
- python ai weekly review
|
||||
- spotify clone
|
||||
|
||||
## Links
|
||||
- [202 lab book](C:\Users\Jet%20Hughes\Documents\Personal\COSC202LabBook-2.pdf)
|
||||
- [i201 cousework](https://isgb.otago.ac.nz/infosci/INFO201/labs_release/raw/master/output/info201_labs.html#)
|
||||
- [i201 Assignments](https://isgb.otago.ac.nz/info201/shared/assignments_release/raw/master/output/info201_assignments.html)
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- info201
|
||||
- lecture
|
||||
sr-due: 2022-05-29
|
||||
sr-interval: 9
|
||||
sr-due: 2022-06-29
|
||||
sr-interval: 26
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- info201
|
||||
- lecture
|
||||
sr-due: 2022-05-17
|
||||
sr-interval: 24
|
||||
sr-due: 2022-09-05
|
||||
sr-interval: 94
|
||||
sr-ease: 290
|
||||
---
|
||||
|
||||
|
||||
@ -3,8 +3,8 @@ title: "04-requirements"
|
||||
tags:
|
||||
- info201
|
||||
- lecture
|
||||
sr-due: 2022-05-29
|
||||
sr-interval: 32
|
||||
sr-due: 2022-08-29
|
||||
sr-interval: 87
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
103
content/notes/040-superstition.md
Normal file
103
content/notes/040-superstition.md
Normal file
@ -0,0 +1,103 @@
|
||||
---
|
||||
title: "040-superstition"
|
||||
aliases:
|
||||
tags:
|
||||
- podcast/philosophizethis
|
||||
---
|
||||
|
||||
"falsely attributing somet cause to some affect"
|
||||
|
||||
e.g., apple is preventing me from going to doctor
|
||||
|
||||
more common than commonly thought
|
||||
|
||||
most people are mistaken about the true causes of things
|
||||
|
||||
e.g., sports fan thinkgs type of beer they drink affects outcome of game
|
||||
|
||||
## on happiness
|
||||
most people want to be happy
|
||||
|
||||
so emulate people who are happy. they see rich people who are happy and think the cause of their happiness is their material things. eventualty realise than not all rich people are happy
|
||||
|
||||
socrates - "happy is he who is content with the least"
|
||||
|
||||
happiness lies in low expectations
|
||||
|
||||
if basic needs aren't met would you be necessarlly be unhappy? -> no you can still be accepting of that
|
||||
|
||||
∴ happiness lies in acceptance
|
||||
|
||||
what is acceptance: accepting what you have and what is in your future. so is happiness being fully present in this moment. when have money you are able to do this more easily
|
||||
|
||||
## back to supersition
|
||||
|
||||
These ^ are all superstitious conclusions. we are all gulity of things like these.
|
||||
|
||||
It is good to periodically examine our own superstitions. However, if we know they're superstitions, why do we have them?
|
||||
|
||||
huge "enemy" during the enlightenment
|
||||
|
||||
### The enlightenment
|
||||
relatively short (relative to history), made up of three key generation of people who had ideas on the backs of each other.
|
||||
|
||||
ways to describe:
|
||||
- the ultimate awakening of mankind - start the snowball of reason
|
||||
- others say the snowball had been rolling since the middle ages (aristotle). enlightenment is just the culmination
|
||||
- fueled by religion - the counter reforation of the curch
|
||||
- propaganda - thinker propped up by people to give legitamacy to new way of thinking
|
||||
|
||||
regardless it was transformative - attempt to abolish superstition is all aread of thought
|
||||
|
||||
### bishop berkley
|
||||
aboish superstitions with senses.
|
||||
|
||||
what we percieve with our senses is not reality "veil of perception"
|
||||
|
||||
we have an idea of reality in our mind far from actual reality
|
||||
|
||||
underneath is some "true" reality.
|
||||
|
||||
berkely questioned this assumption
|
||||
|
||||
the only thing we need to interact with is our "idea" of reality
|
||||
|
||||
"immaterialist idealist" also a monist (the one substance is mind) and impericist (all knowledge is derived from sense experience)
|
||||
|
||||
we never experience the supposed "real" world, so how do we know it exists
|
||||
|
||||
"if a tree falls and noone sees it does it fall" - if there was nobody or notging aroud to percieve it is wouldn't exists. but there is one entity that is perpetually aware of everything in the universe - God
|
||||
|
||||
He is the first in this line of thinking
|
||||
|
||||
tyring to preserve the idea of god.
|
||||
|
||||
gave rise to idealism - emanual kant
|
||||
|
||||
|
||||
how did he get to this line of reasoning? why ask these questions? maybe because he was trying to preserve god. once matter is a substance that explained itself, what is stopping god from being removed. therefore. why does this physical stuff even need to exists at all
|
||||
|
||||
|
||||
### Voltaire
|
||||
not a big fan of the religion of his day
|
||||
|
||||
evolved throughout his life - deist -> theist -> ? Belived in the cosmological god.
|
||||
|
||||
common to be anti-semetic. most peopole because mad at "people who killed jesus". valtaire was mad because jews made christianity able to exist.
|
||||
|
||||
easy for us to project our time period onto voltaire. chistianity - islam - judaism, were different than they are now. they represented something bad to volatire (enemies of supersitions and tolerance). volatire wanted toleration, he thought that god was more that what these religions had laid out so far.
|
||||
|
||||
#### letters concerning the english nation
|
||||
anallysing system of govern in england after reformation following the (3) civil wars, knowing there would be a revolution in france soon
|
||||
|
||||
liked some elements. they were producing good thinkers (newston, bacon, hobbs, and more)
|
||||
|
||||
trying to understand elements of english cuture and how they differed from france. in order to help the french revolution
|
||||
|
||||
appreciates their system of religous tolerance. why do people of differenet religions get along so well. maybe because there are many different forms of religions.
|
||||
|
||||
if there was only one religion - there would be no need for government
|
||||
if there were two religions - they would be fighting (e.g., democrat vs rebuplican)
|
||||
|
||||
so more that two is best. no religion feels threatened by another religion.
|
||||
|
||||
34
content/notes/054-hume-on-art.md
Normal file
34
content/notes/054-hume-on-art.md
Normal file
@ -0,0 +1,34 @@
|
||||
---
|
||||
title: "054-hume-on-art"
|
||||
aliases:
|
||||
tags:
|
||||
- podcast/philosophizethis
|
||||
---
|
||||
|
||||
Tastemaker:
|
||||
- strong sense
|
||||
- able to see and experience the art (i.e., not blind, deaf etc)
|
||||
- delicate taste (perceptive of delicate sentiment)
|
||||
- should be able to see what makes a piece of art good
|
||||
- practice
|
||||
- free of prejudice
|
||||
- Nostalgia
|
||||
- Novelty
|
||||
- Complexity
|
||||
- And more
|
||||
- comparison
|
||||
|
||||
There is something consistent about art. The greatest scientist may not be the greatest of all time, but the greatest artists are strangely timeless.
|
||||
|
||||
All sentiment is right; because sentiment has a reference to nothing beyond itself, and is always real, wherever a man is conscious of it.
|
||||
|
||||
Beauty is no quality in things themselves: It exists merely in the mind which contemplates them; and each mind perceives a different beauty.
|
||||
|
||||
A man in a fever would not insist on his palate as able to decide concerning flavours; nor would one, affected with the jaundice, pretend to give a verdict with regard to colours. In each creature, there is a sound and a defective state; and the former alone can be supposed to afford us a true standard of taste and sentiment. If, in the sound state of the organ, there be an entire or a considerable uniformity of sentiment among men, we may thence derive an idea of the perfect beauty; in like manner as the appearance of objects in day-light, to the eye of a man in health, is denominated their true and real colour, even while colour is allowed to be merely a phantasm of the senses.
|
||||
|
||||
Thus, though the principles of taste be universal, and nearly, if not entirely, the
|
||||
same in all men; yet few are qualified to give judgment on any work of art, or establish their own sentiment as the standard of beauty.
|
||||
|
||||
Strong sense, united to delicate sentiment, improved by practice, perfected by comparison, and cleared of all prejudice, can alone entitle critics to this valuable character; and the joint verdict of such, wherever they are to be found, is the true standard of taste and beauty.
|
||||
|
||||
It is plainly an error in a critic, to confine his approbation to one species or style of writing, and condemn all the rest. But it is almost impossible not to feel a predilection for that which suits our particular turn and disposition. Such preferences are innocent and unavoidable, and can never reasonably be the object of dispute, because there is no standard by which they can be decided.
|
||||
@ -3,8 +3,8 @@ title: "06-business-functions-and-use-cases"
|
||||
tags:
|
||||
- info201
|
||||
- lecture
|
||||
sr-due: 2022-06-04
|
||||
sr-interval: 17
|
||||
sr-due: 2022-07-22
|
||||
sr-interval: 47
|
||||
sr-ease: 270
|
||||
---
|
||||
|
||||
|
||||
66
content/notes/065-mary-woolstonecraft.md
Normal file
66
content/notes/065-mary-woolstonecraft.md
Normal file
@ -0,0 +1,66 @@
|
||||
---
|
||||
title: "065-mary-woolstonecraft"
|
||||
aliases:
|
||||
tags:
|
||||
- podcast/philosophizethis
|
||||
---
|
||||
|
||||
royal humane society - resusitation
|
||||
|
||||
saved mary woolstone craft from the river thames and resusitated after attempted suicide
|
||||
|
||||
suicide is crazy - all our intellect decides the only way is to end it all
|
||||
|
||||
born april 27th 1759
|
||||
|
||||
renaissanece - voltaire rossueau, burke
|
||||
|
||||
born into conservative household - dad was a drunk wifebeater
|
||||
she tried to protect her mother
|
||||
|
||||
lead to need to protect other women
|
||||
|
||||
helped her sister escape from bad marriage
|
||||
|
||||
becomes personal tutor to family with four young daughters
|
||||
* dfa
|
||||
- they were similar to other women of that age
|
||||
- conditioned to become a "good wife"
|
||||
- be quiet, loog good in a corset
|
||||
- sexual "plaything"
|
||||
- submission leads to a "good life"
|
||||
- not critical thinking etc
|
||||
- after being taught bny mary were incedibly succesful
|
||||
- despite reconsideration about slaves, there were no reconsiderations as women as slaves
|
||||
- john locke - tabula rossa - "maybe the content of someones character is dependent on their previous experiences"
|
||||
- jean jaque rosseau emilie - education of men versus education of women
|
||||
- women - "the whole education of women ought ot be relative to men, to please them, to be useful to them, to make themselves loved and honoured by them, to educate them when young, to care for them when grown, to counsel them to console them, and to make life agreeable and sweet to them, these are the duties of women at all times, and should be taught to them from their infancy"
|
||||
- sounds like slavery
|
||||
- this is what woolstone craft is reponding to
|
||||
- "strengthen the female mind by enlarging it, and there will be an end to blind obedience, but as blind obedience is ever sought for by power, tyrants and sensualists are in the right when they endevour to keep women in the dark, because the former only wants slaves and the latter a plaything"
|
||||
- the system that opreses womens is like a tyrant,
|
||||
- women are percieved and mentally and physically inferior to men
|
||||
- chicken vs egg, women always stupid or have men made them stupid
|
||||
- introduced the idea that equality is for women and men (wow)
|
||||
- pursuit of true equality
|
||||
- read edomnd burke reflections (exalted tradition as ultimate guide))
|
||||
- mary rejected this - tradition should be questioned
|
||||
-
|
||||
- after death was castaged for being a vixen "whore"
|
||||
- had many children without marrying
|
||||
- marraige laws were virtually legal slavery this is why she didn't marry
|
||||
- dared to questiont the social convention around her, while being hated
|
||||
- "successful life"
|
||||
- back then -> "submissive to husband who buys everything"
|
||||
- now -> "?" this is still happening - might be just as bad
|
||||
- what about men
|
||||
- "admirable behaviour" - contantly changing, with the culture and world - same for most cultural conventions
|
||||
- what is reponsible for this change
|
||||
- happen in bursts "revolutions"
|
||||
- some one points out a glaring injustice, then change occurs
|
||||
- philosophy and religion
|
||||
- who/what is the tyrant now - how am i being conditioned now.
|
||||
- futured generation will hate us as we have earlier generations
|
||||
- "ill just defend the best behaviour set I know of"
|
||||
- acknowleding how arbitrary our current norms are is freeing
|
||||
- what conditioning might have led to a convicts behaviour, can we change it
|
||||
@ -3,8 +3,8 @@ title: "07-business-process-modelling"
|
||||
tags:
|
||||
- info201
|
||||
- lecture
|
||||
sr-due: 2022-05-16
|
||||
sr-interval: 6
|
||||
sr-due: 2022-07-14
|
||||
sr-interval: 41
|
||||
sr-ease: 270
|
||||
---
|
||||
|
||||
|
||||
@ -3,8 +3,8 @@ title: "07-heuristic-evaluation-cont"
|
||||
tags:
|
||||
- info203
|
||||
- lecture
|
||||
sr-due: 2022-06-02
|
||||
sr-interval: 15
|
||||
sr-due: 2022-07-13
|
||||
sr-interval: 40
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
59
content/notes/077-marx-and-kierkegaard-religion.md
Normal file
59
content/notes/077-marx-and-kierkegaard-religion.md
Normal file
@ -0,0 +1,59 @@
|
||||
---
|
||||
title: "077-marx-and-kierkegaard-religion-pt1"
|
||||
aliases:
|
||||
tags:
|
||||
- podcast/philosophizethis
|
||||
---
|
||||
|
||||
something changes when you an actual photo of a philosopher. they become people, not enigmas (e.g., socrates).
|
||||
|
||||
# Marx
|
||||
"religion is the opiate of the masses".
|
||||
|
||||
lived in the era after the enlightenment. Dividends of these ideas are being paid. Trade is more available. There is ever increasing demand. Small crafter gave way to manufacturers. Power is given to these people. Max's thinks this is bad.
|
||||
|
||||
Marx liked hegels dialectic:
|
||||
- thesis
|
||||
- antithesis
|
||||
- synthesis
|
||||
|
||||
applied this to the economic history of the world.
|
||||
|
||||
"the history of all hitherto existing society is the history of class struggles"
|
||||
|
||||
always two classes of people, rulers, and the exploited. rulers - thesis, exploited - anithesis, then revolution - synthesis.
|
||||
|
||||
e.g.,
|
||||
- slavery vs slave master
|
||||
- peasants vs others
|
||||
|
||||
manufacturers - burgoise. others - politerate
|
||||
|
||||
we are the exploited class of this time period. rulers could be the big financial institutions
|
||||
|
||||
just because you dont feel exploited doesn't mean you aren't.
|
||||
|
||||
why would anyone be satisfied with this arrangement? why should be accept that revolution is necessary.
|
||||
|
||||
rulers try to maximise their time in power. video games, movies, etc. distactin us from the world.
|
||||
|
||||
ultimate method of distraction is religion
|
||||
|
||||
|
||||
|
||||
"religion is the opiate of the masses".
|
||||
|
||||
|
||||
|
||||
meant to mitigate the pain of being exploited. it is the ultimate fanstasy world. creates acceptance in the people. wverything is all "gods will". good for personal happiness, not good for society.
|
||||
|
||||
the structure of the religion of a time period mirrors the current econmic tactic of coercion by the ruling class.
|
||||
|
||||
e.g.,
|
||||
- heirachical structure of feudal system matches the religion of the time - catholism.
|
||||
- capitalism - liberty. religion abandons heirachical structure.
|
||||
|
||||
tell the people "the rich go to hell".
|
||||
|
||||
individual moral progress is an illusion. the only thing that matters is the moral progress of society toward an end goal - the ideal society.
|
||||
|
||||
41
content/notes/078-marx-and-kierkegaard-religion.md
Normal file
41
content/notes/078-marx-and-kierkegaard-religion.md
Normal file
@ -0,0 +1,41 @@
|
||||
---
|
||||
title: "078-marx-and-kierkegaard-religion-pt2"
|
||||
aliases:
|
||||
tags:
|
||||
- podcast/philosophizethis
|
||||
---
|
||||
|
||||
# Kierkegaard
|
||||
disagreed with marx. said progress is a conglomeration of individuals.
|
||||
|
||||
thought it was likely that a world would emerge where people were no longer individuals. he thought there would more people living vicariously through others, than there were individuals.
|
||||
|
||||
colloseum example
|
||||
|
||||
two pitfalls that make you less of an idividual
|
||||
- lost in infinite
|
||||
- "anxiety is the diziness of freedom"
|
||||
- "analysis paralysis"
|
||||
- need to take action
|
||||
- not using the ability to freely act - losing a part of your individuality
|
||||
- lost in finite
|
||||
- "mindlessly following cultural and social conventions"
|
||||
- usually unaware of their state
|
||||
- e.g., cows think they are freely acting, but they are actually folliwing the herd
|
||||
|
||||
can be in both states
|
||||
|
||||
The only way to stop thinking of the endless sea of possibilities is to "make a leap of faith". you can become an individual. "leap of faith" towards christianity.
|
||||
|
||||
was disgusted by the religion of his time. thought everyone was doing it wrong.
|
||||
|
||||
"Christendom is pampered with the nonsense that the Christian God is a decent and harmless chap a good fellow and especially a friend of female business and the beginning of children. All human effort tends towards hurting each other let us unite, etc. Naturally, this happens under all sorts of high sounding names, love and sympathy and enthusiasm the carrying out of some grand plan and the like. This is the usual hypocrisy of the scoundrels we are, but the truth is that in a herd, we are free from the standard of the individual, so millions of men live and die, they're just numbers and the Numerical becomes the horizon, that is to say, they are just copies, and Christianity which, in the divine love wants every one to be an individual, has been transferred by human bungling into precisely the opposite"
|
||||
|
||||
the bible is a system for bringing about the highest form of us as an individual.
|
||||
|
||||
the function of religion is to organise a commitment to a particular way of life. create own religion experiment
|
||||
|
||||
creates a "cheatsheet" for life.
|
||||
|
||||
avoid being lost is infinite or finite. so faith is the ultimate act of reason
|
||||
|
||||
43
content/notes/079-kierkegaard-anxiety.md
Normal file
43
content/notes/079-kierkegaard-anxiety.md
Normal file
@ -0,0 +1,43 @@
|
||||
---
|
||||
title: "079-kierkegaard-anxiety"
|
||||
aliases:
|
||||
tags:
|
||||
- podcast/philosophizethis
|
||||
---
|
||||
|
||||
"anxiety is the dizziness of freedom"
|
||||
|
||||
|
||||
the biggest danger in this life is the loss of yourself. you might not realise you are in this situation.
|
||||
|
||||
most people are lost
|
||||
- lost in finite
|
||||
- lost in infinite
|
||||
|
||||
truly being a self required the realisation that you must make a choice
|
||||
|
||||
when we are stuck between the two we experience "dizziness". we start catasrophizing.
|
||||
|
||||
essense of anxiety - fear of some future outcome that we may have no control over
|
||||
|
||||
"Anxiety may be compared with dizziness he, whose eye happends to look down into the awning abyss becomes dizzy. But what is the reason for this? It is just as much in his own eyes as in the abyss. Anxiety is the dizziness of freedom."
|
||||
|
||||
anxiety is the reaction we have to the sheer number of possibilites. What if i make a mistake?
|
||||
|
||||
this makes us uncomfortable, imbues a sense of *dread*. most peolple to avoid this. the road to becoming a self is tough.
|
||||
|
||||
after dread becomes despair. most people spend their life here. comes from the attempt to rid yourself of yourself. Despair is a sickness of the spirit. A disease affecting your emotional state. Its not always clear that you are in this state, you can be in despair and still seem like a happy person.
|
||||
|
||||
"most men are subjective toward themselves, and objective towards all others. Fightfully objective sometimes. but the task is precisely to be objective towards oneself, and subjective towards all others."
|
||||
|
||||
many types of despair. e.g., sickness of despair over something earthly. conflating identity with something external to yourself.
|
||||
|
||||
Using something to distract yourself from your state of despair. similar to kant idea of outsourcing things. echoes of buddism.
|
||||
|
||||
while you are feeling anxiety you are becoming closer to your true self.
|
||||
|
||||
aim to find a "truth that is true for me"
|
||||
|
||||
reject hegel notion that our choices are a product of our culture.
|
||||
|
||||
father of existentialism
|
||||
@ -3,8 +3,8 @@ title: "08-debugging"
|
||||
tags:
|
||||
- cosc202
|
||||
- lecture
|
||||
sr-due: 2022-06-03
|
||||
sr-interval: 16
|
||||
sr-due: 2022-07-15
|
||||
sr-interval: 42
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: "08-mergesort-2"
|
||||
sr-due: 2022-06-05
|
||||
sr-interval: 59
|
||||
sr-due: 2022-11-11
|
||||
sr-interval: 159
|
||||
sr-ease: 270
|
||||
tags:
|
||||
- cosc201
|
||||
|
||||
35
content/notes/083-henry-david-thoreau.md
Normal file
35
content/notes/083-henry-david-thoreau.md
Normal file
@ -0,0 +1,35 @@
|
||||
---
|
||||
title: "083-henry-david-thoreau"
|
||||
aliases:
|
||||
tags:
|
||||
- podcast/philosophizethis
|
||||
---
|
||||
|
||||
trancendentalist
|
||||
|
||||
graduated harvard, got a job as a school teacher. He was against corporal punishment and quit. opponent of slavery, conservationist.
|
||||
|
||||
how to persuade people to agree?
|
||||
|
||||
are you oblisged to agree with the majority ina democracy or the opposite.
|
||||
|
||||
read self reliance by ralph waldo emerson. meant to teach the importatnce of being an "individual" - "there comes a time in every mans education, when he arrives at the conviction that envy is ignorance, that imitation is suicide that he must take himself for better or for worse as his portion"
|
||||
|
||||
as a human we need to find out who we are. none of us are born with this knowledge so we conform with what others are doing. but imitation is suicide of you individuality.
|
||||
|
||||
best thing to do is figure it out for yourself. objective truth is hard to define
|
||||
|
||||
trancendentalism -> takes other ideas, and creates an approach to life needs meaning, and that one must find this meaning himself. aim to understand personal truth about the way things are.
|
||||
|
||||
society is in conspiracy againt the manhood of its members.
|
||||
|
||||
society promotes conformity, protects the mentally and physically lazy. obstacle blocking living individualy
|
||||
|
||||
the more you own , the more your stuff owns you.
|
||||
|
||||
try to "fix yourself using material things". not only material things, also e.g. travel.
|
||||
|
||||
when people are given freedom they act like everyone else.
|
||||
|
||||
|
||||
|
||||
@ -3,8 +3,8 @@ title: "09-documentation"
|
||||
tags:
|
||||
- cosc202
|
||||
- lecture
|
||||
sr-due: 2022-05-21
|
||||
sr-interval: 28
|
||||
sr-due: 2022-09-11
|
||||
sr-interval: 100
|
||||
sr-ease: 290
|
||||
---
|
||||
|
||||
|
||||
@ -3,8 +3,8 @@ title: "09-paper-prototypes-wiz-of-oz-video-prototypes"
|
||||
tags:
|
||||
- info203
|
||||
- lecture
|
||||
sr-due: 2022-05-23
|
||||
sr-interval: 26
|
||||
sr-due: 2022-08-26
|
||||
sr-interval: 84
|
||||
sr-ease: 270
|
||||
---
|
||||
|
||||
|
||||
@ -3,8 +3,8 @@ title: "09-stacks-queues-heaps"
|
||||
tags:
|
||||
- cosc201
|
||||
- lecture
|
||||
sr-due: 2022-05-29
|
||||
sr-interval: 11
|
||||
sr-due: 2022-07-01
|
||||
sr-interval: 28
|
||||
sr-ease: 210
|
||||
---
|
||||
|
||||
|
||||
@ -3,8 +3,8 @@ title: "10-continuous-integration-1"
|
||||
tags:
|
||||
- cosc202
|
||||
- lecture
|
||||
sr-due: 2022-05-17
|
||||
sr-interval: 7
|
||||
sr-due: 2022-07-12
|
||||
sr-interval: 39
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -3,8 +3,8 @@ title: "10-design-heuristics-1"
|
||||
tags:
|
||||
- info203
|
||||
- lecture
|
||||
sr-due: 2022-06-03
|
||||
sr-interval: 16
|
||||
sr-due: 2022-07-17
|
||||
sr-interval: 44
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: "10-heaps-and-heapsort"
|
||||
sr-due: 2022-06-04
|
||||
sr-interval: 42
|
||||
sr-due: 2022-09-28
|
||||
sr-interval: 115
|
||||
sr-ease: 270
|
||||
tags:
|
||||
- cosc201
|
||||
|
||||
@ -3,8 +3,8 @@ title: "10-oop-concepts-and-uml"
|
||||
tags:
|
||||
- info201
|
||||
- lecture
|
||||
sr-due: 2022-06-05
|
||||
sr-interval: 18
|
||||
sr-due: 2022-07-24
|
||||
sr-interval: 49
|
||||
sr-ease: 270
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: "11-continuous-integration-2"
|
||||
sr-due: 2022-06-06
|
||||
sr-interval: 44
|
||||
sr-due: 2022-10-03
|
||||
sr-interval: 119
|
||||
sr-ease: 270
|
||||
tags:
|
||||
- cosc202
|
||||
|
||||
@ -3,8 +3,8 @@ title: "11-sets-maps-trees"
|
||||
tags:
|
||||
- cosc201
|
||||
- lecture
|
||||
sr-due: 2022-05-26
|
||||
sr-interval: 33
|
||||
sr-due: 2022-09-10
|
||||
sr-interval: 99
|
||||
sr-ease: 270
|
||||
---
|
||||
|
||||
|
||||
@ -3,8 +3,8 @@ title: "12-automation"
|
||||
tags:
|
||||
- cosc202
|
||||
- lecture
|
||||
sr-due: 2022-05-30
|
||||
sr-interval: 37
|
||||
sr-due: 2022-09-16
|
||||
sr-interval: 105
|
||||
sr-ease: 270
|
||||
---
|
||||
links: [cosc-202-lectures](notes/cosc-202-lectures.md), [slides](https://cosc202.cspages.otago.ac.nz/lectures/L12-automation.pdf)
|
||||
|
||||
@ -3,8 +3,8 @@ title: "12-binary-search-tree-operations"
|
||||
tags:
|
||||
- cosc201
|
||||
- lecture
|
||||
sr-due: 2022-05-27
|
||||
sr-interval: 34
|
||||
sr-due: 2023-03-03
|
||||
sr-interval: 273
|
||||
sr-ease: 270
|
||||
---
|
||||
|
||||
|
||||
@ -3,8 +3,8 @@ title: "12-modelling-behaviour"
|
||||
tags:
|
||||
- info201
|
||||
- lecture
|
||||
sr-due: 2022-05-28
|
||||
sr-interval: 31
|
||||
sr-due: 2022-08-28
|
||||
sr-interval: 86
|
||||
sr-ease: 250
|
||||
---
|
||||
[slides](https://blackboard.otago.ac.nz/bbcswebdav/pid-2892846-dt-content-rid-18407618_1/courses/INFO201_S1DNIE_2022/2022/lectures/lecture_12_slides.pdf)
|
||||
@ -17,9 +17,17 @@ sr-ease: 250
|
||||
- compartmentalisation into "subsystems"
|
||||
|
||||
1. Compare and contrast the two typical approaches to inheriting behaviour in OO systems.
|
||||
2. What does it mean to “program to an interface� and why is this important?
|
||||
3. Compare and contrast “rich� versus “anaemic� domain models with regards to behaviour.
|
||||
4. Give an example of a “processor� in the context of OO system design and explain why these are useful.
|
||||
2. What does it mean to “program to an interface<63>? and why is this important?
|
||||
3. Compare and contrast “rich<63>? versus “anaemic<69>? domain models with regards to behaviour.
|
||||
4. Give an example of a “processor<6F>? in the context of OO system design and explain why these are useful.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -64,7 +72,7 @@ e.g.,
|
||||
|
||||
- Search specifies a set of common behaviour.
|
||||
- public methods and constant fields only (no variable fields)
|
||||
- effectively an “inheritable� public API (no implementation) ⇒ Catalogue must implement all Search methods
|
||||
- effectively an “inheritable<EFBFBD>? public API (no implementation) ⇒ Catalogue must implement all Search methods
|
||||
- independent of inheritance via specialisation
|
||||
- a class can implement multiple interfaces
|
||||
- Things that know how to use Search will also accept Catalogue.
|
||||
@ -82,7 +90,7 @@ e.g.,
|
||||
|
||||
- The public API defines what a class can do
|
||||
- e.g., read and write data, manage a list of items
|
||||
- effectively a “promise� or “contract� to other classes that use it
|
||||
- effectively a “promise<EFBFBD>? or “contract<63>? to other classes that use it
|
||||
- should be as stable as possible
|
||||
|
||||
- The private implementation defines how a class behaves
|
||||
@ -142,7 +150,7 @@ Anything coded to work with Collection will accept *any* Java collection type. (
|
||||
|
||||
## 3.1 Rich domain models
|
||||
|
||||
- True OO involves sending objects “native instructions� beyond basic getter/setter methods:
|
||||
- True OO involves sending objects “native instructions<6E>? beyond basic getter/setter methods:
|
||||
- e.g., they can save, display, update, validate, etc., themselves
|
||||
- often requires communicating with other objects
|
||||
- Advantages:
|
||||
@ -150,9 +158,9 @@ Anything coded to work with Collection will accept *any* Java collection type. (
|
||||
- methods are highly cohesive (focused)
|
||||
- natural fit with programming to an interface
|
||||
- Disadvantages:
|
||||
- many “chicken and egg� situations ⇒ harder to use
|
||||
- many “chicken and egg<67>? situations ⇒ harder to use
|
||||
- bordering on taking things too far (too much abstraction)
|
||||
- well beyond comfort zone of many developers (“exotic�)
|
||||
- well beyond comfort zone of many developers (“exotic<EFBFBD>?)
|
||||
|
||||
### 3.1.1 Rich domain example: Library system
|
||||
|
||||
@ -161,13 +169,13 @@ Anything coded to work with Collection will accept *any* Java collection type. (
|
||||
|
||||
## 3.2 Contrast with anaemic domain models
|
||||
|
||||
- Objects have relatively little “native� behaviour: (if any)
|
||||
- Objects have relatively little “native<EFBFBD>? behaviour: (if any)
|
||||
- mostly just state
|
||||
- don’t inherit from anything else (class or interface)
|
||||
- getters/setters don’t really encapsulate much
|
||||
- methods manipulate only internal state (no external communication)
|
||||
- generally referred to as JavaBeans in Java (also POJO)
|
||||
- Require a lot of “plumbing� code to shift data into and out of objects so we can do something useful with it.
|
||||
- Require a lot of “plumbing<EFBFBD>? code to shift data into and out of objects so we can do something useful with it.
|
||||
- De facto standard for most programmers/systems
|
||||
|
||||
|
||||
@ -182,8 +190,8 @@ Anything coded to work with Collection will accept *any* Java collection type. (
|
||||
- shipping (sub)system
|
||||
- inventory (sub)system
|
||||
- …
|
||||
- “Processor objects� can encapsulate these interactions:
|
||||
- effectively “(sub)system APIs� that group related behaviour
|
||||
- “Processor objects<74>? can encapsulate these interactions:
|
||||
- effectively “(sub)system APIs<49>? that group related behaviour
|
||||
- either classes or (Java) interfaces, as appropriate
|
||||
- methods take relevant domain objects as arguments
|
||||
- Third-party frameworks can reduce the amount of code you need to write even further. (see INFO 202)
|
||||
@ -196,6 +204,6 @@ Anything coded to work with Collection will accept *any* Java collection type. (
|
||||
- Behaviour can be inherited directly via specialisation, or indirectly by implementing an interface.
|
||||
- interfaces decouple public API from private implementation
|
||||
- programming to an interface
|
||||
- Domain models can be “rich� or “anaemic�.
|
||||
- Domain models can be “rich<EFBFBD>? or “anaemic<69>?.
|
||||
- anaemic more common
|
||||
- use “processors� to encapsulate “plumbing� code
|
||||
- use “processors<EFBFBD>? to encapsulate “plumbing<6E>? code
|
||||
|
||||
@ -4,154 +4,10 @@ aliases:
|
||||
tags:
|
||||
- info201
|
||||
- lecture
|
||||
sr-due: 2022-05-17
|
||||
sr-interval: 24
|
||||
sr-due: 2022-08-30
|
||||
sr-interval: 88
|
||||
sr-ease: 270
|
||||
---
|
||||
|
||||
sequence diagrams document a *sequence* of particpant interactions required to carry out a use case
|
||||
- actor <-> object
|
||||
- actors are outside the system
|
||||
- objects are otside the system
|
||||
- via a method call
|
||||
- might get a result
|
||||
- object <-> object
|
||||
- lifetime of interactions and objects
|
||||
- when they are created updated destroyed
|
||||
- time is a key aspect
|
||||
- [use-case-diagrams](notes/use-case-diagrams.md) dont have order
|
||||
|
||||
These diagrams are:
|
||||
- detailed, low level, bottom up
|
||||
- behavioural diagram
|
||||
- not structural
|
||||
- common in industry
|
||||
- along with class diagrams
|
||||
- need to be designed and read alongside corresponding class diagrams
|
||||
- e.g., class diagrams with inform sequences diagrams and vice versa
|
||||
- back and forth process
|
||||
|
||||
|
||||
General overview example: [annotated example](https://i.imgur.com/1myG3rU.png)
|
||||
- time goes from top to bottom
|
||||
- however no specific time units
|
||||
- can have actors as participants
|
||||
- but not usually
|
||||
- existence of actor usualy indicates a sequence is owned by a use case
|
||||
- interactions are indicated by messages (solid arrows)
|
||||
- e.g. actor to main menu
|
||||
- actor clicks a button
|
||||
- menu reacts
|
||||
- etc
|
||||
- messges are synchronous
|
||||
- i.e., thing sending message must wait for result
|
||||
- always method calls (or something that equated to a method call)
|
||||
- participants are supposed to be instances of classes
|
||||
- however we are usually more interested in the class name
|
||||
- the dashed lines are lifelines
|
||||
- can also be solid
|
||||
- basically indicate the existenc of something
|
||||
- e.g., Thingform gets destroyed, thingfinder and thing remain throughout
|
||||
- the rectangles (activation bars) indicate when an a thing is doing somethin
|
||||
- caused by incoming message
|
||||
- ended by a return
|
||||
- these can have sub activations
|
||||
- i.e., nested
|
||||
- these can be self-activations
|
||||
- implcit: not all methods return something
|
||||
|
||||
relevant slide:
|
||||
|
||||
|
||||
|
||||
# Messages
|
||||
[example](https://i.imgur.com/XedVmng.png)
|
||||
- direction
|
||||
- <- or ->
|
||||
- easier to under stand if most messages are ->
|
||||
- however this is not always possible
|
||||
- same object used by multiple other objects
|
||||
- an object calls back to the object that called it
|
||||
- can be conditions (guards) [example](https://i.imgur.com/yWTcD1F.png)
|
||||
- only sent if condition is true
|
||||
- able to approximate if-then-else using multiple branches with exclusive conditions
|
||||
- this is better done in activity diagram
|
||||
- looping messages [example](https://i.imgur.com/tcFZ4bb.png)
|
||||
- an asterisk idicated looping
|
||||
- repeat message until condition id false
|
||||
- send messge to each object in a collection
|
||||
- may also be better in activity diagram
|
||||
|
||||
# Interaction frames (UML 2.x)
|
||||
[example](https://i.imgur.com/V1Jhnd2.png)
|
||||
- loop frame
|
||||
- any kind of loop
|
||||
- replaces * notation
|
||||
- opt frame
|
||||
- optional or conditional processing
|
||||
- can replace [] notation
|
||||
- alt frame
|
||||
- if-then-else
|
||||
- can replace [] notation
|
||||
|
||||
one thing that can cause complications is
|
||||
- when something can a top level loop which is waiting for input.
|
||||
- a cancel anytime option
|
||||
|
||||
|
||||
# Basic process of creation
|
||||
|
||||
- identity participants of a use case (dont always need to use a use-case diagram)
|
||||
- use use case to create first version of the activity diagram. as you implement the code update the class and activity diagrams
|
||||
- identify messges required to carry out use case
|
||||
- for each message
|
||||
- it is always sent
|
||||
- is it sent conditionally
|
||||
- is it sent multiple times
|
||||
- assemble messages in correct sequence and attach to relevant lifelines/activations
|
||||
- add returns where necessary
|
||||
|
||||
# Case study ATM
|
||||
|
||||
bank is developing a new ATM system for their customers
|
||||
|
||||
scope and requirements
|
||||
- each customer has one or mor accounts
|
||||
- transaction types are
|
||||
- view balance
|
||||
- withdraw cash
|
||||
- deposit funds
|
||||
- the customer can cancel at any point before final confirmation
|
||||
- customer authenticates by inserting bank card and entering four digit pin
|
||||
|
||||
process
|
||||
- choose account
|
||||
- choose amount
|
||||
- check customer funds
|
||||
- check amount in cash dipenser
|
||||
- results
|
||||
- withdraw amount
|
||||
- dispense amount
|
||||
- remind user
|
||||
|
||||
|
||||
|
||||
this diagam is probably too general for this case
|
||||
|
||||
|
||||
|
||||
note navigability of domain
|
||||
|
||||
sequence diagram
|
||||
|
||||
- [part 1](https://i.imgur.com/PJJBZav.png)
|
||||
- [part 2](https://i.imgur.com/M3jRM8g.png)
|
||||
- [part 3](https://i.imgur.com/PhCYWsy.png)
|
||||
- [part 4](https://i.imgur.com/L0h4nb8.png)
|
||||
|
||||
|
||||
|
||||
|
||||
[full diagram](https://blackboard.otago.ac.nz/bbcswebdav/pid-2894257-dt-content-rid-18429333_1/courses/INFO201_S1DNIE_2022/2022/lectures/lecture_13_atm-withdraw-sequence-full.pdf)
|
||||
|
||||
[sequence-diagrams](notes/sequence-diagrams.md)
|
||||
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- info203
|
||||
- lecture
|
||||
sr-due: 2022-06-01
|
||||
sr-interval: 14
|
||||
sr-due: 2022-07-09
|
||||
sr-interval: 36
|
||||
sr-ease: 250
|
||||
---
|
||||
[aesthetic-and-minimalist-design](notes/aesthetic-and-minimalist-design.md)
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- cosc202
|
||||
- lecture
|
||||
sr-due: 2022-05-31
|
||||
sr-interval: 9
|
||||
sr-due: 2022-06-29
|
||||
sr-interval: 26
|
||||
sr-ease: 252
|
||||
---
|
||||
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- info203
|
||||
- lecture
|
||||
sr-due: 2022-05-24
|
||||
sr-interval: 31
|
||||
sr-due: 2022-09-08
|
||||
sr-interval: 97
|
||||
sr-ease: 270
|
||||
---
|
||||
|
||||
@ -23,7 +23,7 @@ object action model maps to real life environment
|
||||
|
||||
the designer needs to create mapping from the real world unicers ofb objects and intentios to the intrefac world universe of metaphors and plans
|
||||
|
||||
# fits law
|
||||
# fitts law
|
||||
time to point to something depends on its size and distance:
|
||||
$$
|
||||
MT = C1 + C2\ log_2(2A/W)
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- cosc202
|
||||
- lecture
|
||||
sr-due: 2022-05-27
|
||||
sr-interval: 18
|
||||
sr-due: 2022-07-27
|
||||
sr-interval: 54
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- info203
|
||||
- lecture
|
||||
sr-due: 2022-05-31
|
||||
sr-interval: 21
|
||||
sr-due: 2022-07-29
|
||||
sr-interval: 56
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- cosc201
|
||||
- lecture
|
||||
sr-due: 2022-06-02
|
||||
sr-interval: 15
|
||||
sr-due: 2022-07-11
|
||||
sr-interval: 38
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- info201
|
||||
- lecture
|
||||
sr-due: 2022-06-07
|
||||
sr-interval: 20
|
||||
sr-due: 2022-08-02
|
||||
sr-interval: 55
|
||||
sr-ease: 270
|
||||
---
|
||||
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- cosc201
|
||||
- lecture
|
||||
sr-due: 2022-06-08
|
||||
sr-interval: 19
|
||||
sr-due: 2022-07-26
|
||||
sr-interval: 48
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -4,12 +4,12 @@ aliases:
|
||||
tags:
|
||||
- info201
|
||||
- lecture
|
||||
sr-due: 2022-05-15
|
||||
sr-interval: 7
|
||||
sr-due: 2022-07-08
|
||||
sr-interval: 38
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
[revision questions](https://i.imgur.com/mPmQ28v.png)
|
||||
|
||||
|
||||
[data-access](notes/data-access.md)
|
||||
- [file-based-storage](notes/file-based-storage.md)
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- lecture
|
||||
- cosc202
|
||||
sr-due: 2022-05-16
|
||||
sr-interval: 8
|
||||
sr-due: 2022-07-16
|
||||
sr-interval: 43
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- info201
|
||||
- lecture
|
||||
sr-due: 2022-05-15
|
||||
sr-interval: 3
|
||||
sr-due: 2022-06-28
|
||||
sr-interval: 28
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- cosc202
|
||||
- lecture
|
||||
sr-due: 2022-05-21
|
||||
sr-interval: 8
|
||||
sr-due: 2022-07-10
|
||||
sr-interval: 37
|
||||
sr-ease: 252
|
||||
---
|
||||
|
||||
@ -15,4 +15,5 @@ sr-ease: 252
|
||||
- sketch how maven seeks to improve on ant
|
||||
- appreciated that there are many build tools
|
||||
|
||||
[build-tools](notes/build-tools.md)
|
||||
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- info201
|
||||
- lecture
|
||||
sr-due: 2022-05-26
|
||||
sr-interval: 7
|
||||
sr-due: 2022-06-30
|
||||
sr-interval: 27
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- cosc201
|
||||
- lecture
|
||||
sr-due: 2022-05-27
|
||||
sr-interval: 8
|
||||
sr-due: 2022-07-04
|
||||
sr-interval: 31
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- cosc202
|
||||
- lecture
|
||||
sr-due: 2022-05-16
|
||||
sr-interval: 3
|
||||
sr-due: 2022-07-03
|
||||
sr-interval: 30
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
@ -15,91 +15,4 @@ sr-ease: 250
|
||||
- explain risks from non-validation of user input
|
||||
- outline how injection attack works
|
||||
|
||||
# growing problem
|
||||
- more software around
|
||||
- more dependencies
|
||||
- resuse of old code rather than starting from scratch
|
||||
- more complex programs
|
||||
- "surface area" of risk is growing
|
||||
- speed of development has trumped security
|
||||
- some languages are inherently more secure than other
|
||||
- e.g., C can access any memory
|
||||
- software systems involve large numbers of components
|
||||
- large amounts of code is almost guaranteed to have bugs
|
||||
|
||||
# Security in development
|
||||
- - security isn't a single requiremtn you can tick off
|
||||
- it needs consideration throughtout the whole system
|
||||
- it is a cross-cutting concern
|
||||
- it is hard to retrofit
|
||||
- notion of security engineering is useful
|
||||
- affects design descision fromt the outset
|
||||
- changes how code is written and reviewed
|
||||
- add a specific type of testing to include
|
||||
- needs examination of how users interact with software
|
||||
|
||||
# Threat model
|
||||
- should character what you want to protect against
|
||||
- writin standalone software to be used by one person
|
||||
- typially dont have to worry about malicious attacks (on self)
|
||||
- software on a multi-user operating system
|
||||
- do need to think about cross-user data leaks
|
||||
- all OSs are multi user
|
||||
- software that has network availability
|
||||
- your software can and likely will be attacked
|
||||
- targeteted by state-sponsored teams? Good Luck...
|
||||
|
||||
# Divide into three areas
|
||||
- confidentiality - e.g., sensitive data is not visible
|
||||
- integrity e.g., data is protected from modification
|
||||
- avaliability e.g., services stay accessible
|
||||
|
||||
## Confidentiality
|
||||
- attacks on this involve stealing data
|
||||
- protect using encrytion (unsecured network or disk) or isolation of processes (if you trust the OS)
|
||||
- encrption does not necessarly work forever.
|
||||
|
||||
|
||||
## Integrity
|
||||
- attacks on data may aim to decieve users
|
||||
- defence: apply checksums (e.g., check secure hash of data)
|
||||
- attacks on code are often for *privilege esccalation*
|
||||
- e.g., attacker moves from normal user to super user
|
||||
- defence: avoid decisions being influenced by outside sources
|
||||
|
||||
## Availability
|
||||
- e.g., DDoS
|
||||
- ditributed denial of service
|
||||
- Defence: host services in multiple countries
|
||||
- use CDNs (content delivery networks) for data objects
|
||||
|
||||
## Key soft. dev. security area 1: dependencies
|
||||
- vulnerabilities in dependencies affect your code too
|
||||
- determine and examine your software bill of materials SBOM
|
||||
- subscribe to security alerts for your key dependencies
|
||||
- plan to rapidly rebuild and release you software at short notice
|
||||
- use tools to scan software for know problems
|
||||
- e.g., gitlab auto devOps scancs containers for vulnerabilites
|
||||
|
||||
- doesn't mean dont use them
|
||||
- use them if they are good
|
||||
- e.g.,
|
||||
- dont implement crypto yourself
|
||||
- use a secret manager for authentication
|
||||
- XACML libray
|
||||
- use libraries to parse data
|
||||
|
||||
## Key soft. dev. security area 1: santise input
|
||||
- treat user controlled inpuut to your code as malicious
|
||||
- databases must prevent SQL injection
|
||||
- many input sources
|
||||
- user docs
|
||||
- config files
|
||||
- env variables
|
||||
|
||||
# Injection attacks
|
||||
- rough def$^n$ some structure is not contained properly
|
||||
- 
|
||||
|
||||
# Resolving problems
|
||||
|
||||
[security](notes/security.md)
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- info201
|
||||
- lecture
|
||||
sr-due: 2022-05-20
|
||||
sr-interval: 3
|
||||
sr-due: 2022-06-27
|
||||
sr-interval: 24
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- cosc201
|
||||
- lecture
|
||||
sr-due: 2022-05-21
|
||||
sr-interval: 3
|
||||
sr-due: 2022-06-26
|
||||
sr-interval: 23
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- cosc202
|
||||
- lecture
|
||||
sr-due: 2022-05-30
|
||||
sr-interval: 10
|
||||
sr-due: 2022-07-06
|
||||
sr-interval: 33
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
10
content/notes/203-exam-prep.md
Normal file
10
content/notes/203-exam-prep.md
Normal file
@ -0,0 +1,10 @@
|
||||
---
|
||||
title: "203-exam-prep"
|
||||
aliases:
|
||||
tags:
|
||||
|
||||
---
|
||||
|
||||
example questions
|
||||
|
||||
https://blackboard.otago.ac.nz/bbcswebdav/pid-2827524-dt-content-rid-18670180_1/courses/INFO203_S1DNIE_2022/2022/INFO203_Lecture25.pdf
|
||||
@ -4,8 +4,8 @@ aliases:
|
||||
tags:
|
||||
- info203
|
||||
- lecture
|
||||
sr-due: 2022-05-28
|
||||
sr-interval: 3
|
||||
sr-due: 2022-06-18
|
||||
sr-interval: 15
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -5,8 +5,8 @@ tags:
|
||||
- info203
|
||||
- lecture
|
||||
- scott-video
|
||||
sr-due: 2022-06-01
|
||||
sr-interval: 7
|
||||
sr-due: 2022-06-23
|
||||
sr-interval: 20
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -30,7 +30,7 @@ REST principles were Co-developed with the web
|
||||
java servelts are code blocks that handle requests. java.servlet.http library
|
||||
|
||||
framworks like Spring support Java API development
|
||||
- wraps an aplicationserver around you data classes
|
||||
- wraps an aplication server around you data classes
|
||||
- can persist your data in a database
|
||||
- also provides servers that can host API access to your data
|
||||
|
||||
|
||||
@ -5,8 +5,8 @@ tags:
|
||||
- info203
|
||||
- lecture
|
||||
- scott-video
|
||||
sr-due: 2022-05-28
|
||||
sr-interval: 9
|
||||
sr-due: 2022-07-05
|
||||
sr-interval: 32
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -30,8 +30,8 @@ PlUS
|
||||
- several differnt types, e.g., composition, aggregation, associateive classes
|
||||
|
||||
### 3.1 multuplicity
|
||||
[multiplicity-1](https://i.imgur.com/1dSergW.png)
|
||||
[multiplicity-2](https://i.imgur.com/4TKsBKd.png)
|
||||
|
||||
|
||||
|
||||
ERDsd effectively only do zero one many
|
||||
UML can to any non negative integer
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: "cosc-202"
|
||||
year: 2022
|
||||
semester:
|
||||
semester: 1
|
||||
tags:
|
||||
- course
|
||||
- cosc202
|
||||
@ -27,12 +27,13 @@ links: [_index](_index.md)
|
||||
- [continuous-integration](notes/continuous-integration.md)
|
||||
- [automation](notes/automation.md)
|
||||
- [software library](notes/libraries.md)
|
||||
- [application-programming-interface](notes/application-programming-interface.md)
|
||||
- [containers](notes/containers.md)
|
||||
- [linker](notes/linker.md)
|
||||
- [loader](notes/loader.md)s
|
||||
- [operating-system](notes/operating-system.md)
|
||||
- [software-licensing](notes/software-licensing.md)
|
||||
- [application-programming-interface](notes/application-programming-interface.md)
|
||||
- [[security](notes/security.md)]
|
||||
|
||||
# Lectures
|
||||
- [07-testing](notes/07-testing.md)
|
||||
|
||||
@ -5,8 +5,8 @@ tags:
|
||||
- info203
|
||||
- scott-video
|
||||
- lecture
|
||||
sr-due: 2022-05-26
|
||||
sr-interval: 7
|
||||
sr-due: 2022-07-02
|
||||
sr-interval: 29
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
@ -1,3 +1,13 @@
|
||||
---
|
||||
title: Milestone 3
|
||||
subtitle: Jet Hughes 9474308
|
||||
geometry:
|
||||
- right=20mm
|
||||
- left=20mm
|
||||
tags:
|
||||
- assignment/mobile-app
|
||||
---
|
||||
|
||||
# Brain Storming
|
||||
## Concept 1 - Snowboard trick generator.
|
||||
This will be a mobile app that snowboarders can use to automatically generate random tricks. This app will be useful because snowboarders (riders) often get tunnel vision on a certain style of tricks or even a single trick. Using a algorithm to generate tricks provides a way for them to escape this focus. It can also be used when playing a game of SNOW, which is similar to a game of SKATE.
|
||||
@ -100,7 +110,8 @@ Takeaways:
|
||||
- Maybe incorporate some gestures
|
||||
- Consider using an aesthetic wich matches the culture/sport
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Skate tricks
|
||||
This app is a much more fully featured solution. It is oriented towards learning skateboarding, and keeping track of you progress while doing it. It also has a built in trick generator, and game of skate. One of the most unique features it had that the other apps didn't was a trick of the day. This is one of the core features I want to include in my app. Another interesting feature it had was a page informing the user about injury prevention.
|
||||
@ -132,7 +143,7 @@ This app is a much more fully featured solution. It is oriented towards learning
|
||||
- skill advanced (not with tricks just in general)
|
||||
- focus off piste/backcountry, sometimes goes into park with friends/kids
|
||||
|
||||
## Primary: Casual Kyle
|
||||
## Primary: Casual Kyle
|
||||
|
||||
|
||||
|
||||
@ -225,23 +236,23 @@ Logan is snowboarding on the mountain with a group of his friends. Logan and his
|
||||
The first thing I wanted to was get a clear picture of how each screen should interact with the others. Identified three main screens: Home, Friends, and Schedule. I also identified some supplementary screens: Trick options, other settings, and welcome, and some more optional screens: Trick lists, trick dictionary.
|
||||
|
||||
I also listed some things that each screen should contain
|
||||
|
||||
|
||||
|
||||
### General protoypes
|
||||
Next I started to get down down general ideas about all of the screens. The main goal of this step for was to figure out the general flow of the app, and to get a general idea of how each screen should look.
|
||||
|
||||
This first two pages I was experimenting mostly with the home screen. I tried three different layouts: Top tabs, Bottom tabs, and floating bottom buttons. I also started to explore ways for the user to navigate from the home screen to the trick options screen, and the schedule screen.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
The second page I explored a some variations on the floating button design. And begin experimenting with the navigation and layout of the friends screen.
|
||||
|
||||
|
||||
|
||||
|
||||
On the third page I kept experimenting with the friends page.
|
||||
|
||||
|
||||
|
||||
|
||||
## In depth prototypes
|
||||
### Home screen
|
||||
@ -252,20 +263,20 @@ I started with creating an partly new design that combined the floating buttons,
|
||||
I also decided against the swipe feature to show tricks, and opted instead for a button which opened another screen.
|
||||
|
||||
I also tried out some other designs features a black background and round buttons.
|
||||
 
|
||||
 
|
||||
|
||||
### Other settings
|
||||
|
||||
|
||||
|
||||
### Trick Options
|
||||
For the trick Options I considered a few three main designs: the swipe/scroll, the modal, and the full screen.
|
||||
|
||||
|
||||
### Welcome
|
||||
|
||||
|
||||
|
||||
### Schedule
|
||||
|
||||
|
||||
|
||||
## Refinement
|
||||
Firstly I converted the lo-fi prototypes into Adobe XD designs.
|
||||
|
||||
@ -4,14 +4,14 @@ aliases:
|
||||
tags:
|
||||
- assignment/mobile-app
|
||||
---
|
||||
#
|
||||
|
||||
Firstly I converted the lo-fi prototypes into Adobe XD designs.
|
||||
|
||||
|
||||
|
||||
I decided I wanted to make some chagnes to the design here so I saved this as version 1.
|
||||
|
||||
### Schedule changes
|
||||
## Schedule changes
|
||||
|
||||
I wanted to chagne the way the schedule/altude options worked. My first rough redesign was this:
|
||||
|
||||
@ -37,7 +37,7 @@ I also changed the alignment of the weekday selection buttons. And the altitude
|
||||
|
||||
|
||||
|
||||
### Trick options Changes
|
||||
## Trick options Changes
|
||||
I decied to change the way this worked. Instead of have the save cancel buttons I wanted the settings change to have immediate effect, so the user didn't have to save. This was the first redesign:
|
||||
|
||||
|
||||
@ -48,12 +48,12 @@ This is largely the same, except I added a head with back button and remove the
|
||||
|
||||
|
||||
|
||||
### "Color" scheme changes
|
||||
## "Color" scheme changes
|
||||
|
||||
After I had mostly finished the Layout. I changed the look to match the snowboarding "aesthetic", by making the app primarily black
|
||||
|
||||
|
||||
|
||||
### More layout changes
|
||||
## More layout changes
|
||||
I decided to add the home row navigation back to the trick options screens to improve **user control and freedom**
|
||||
|
||||
|
||||
@ -12,18 +12,6 @@ links: [_index](_index.md)
|
||||
- [assignments tiddlywiki](https://isgb.otago.ac.nz/info201/shared/assignments_release/raw/master/output/info201_assignments.html)
|
||||
- [labs folder](file:///"C:/Users/Jet%20Hughes/Documents/Personal/courses/info-201/Labs")
|
||||
|
||||
# Labs Checklist
|
||||
- [x] 2
|
||||
- [x] 3
|
||||
- [x] 4
|
||||
- [x] 5
|
||||
- [x] 6
|
||||
- [ ] 7
|
||||
- [x] 8
|
||||
- [x] 9
|
||||
- [x] 10
|
||||
- [x] 11
|
||||
|
||||
# Outline
|
||||
- [version control system](notes/version-control-systems.md)
|
||||
- [stakeholders](notes/stakeholders.md)
|
||||
@ -46,8 +34,9 @@ links: [_index](_index.md)
|
||||
- [business-process](notes/business-process.md)
|
||||
- [business-process-model](notes/business-process-model.md)
|
||||
- [business-process-model-and-notation](notes/business-process-model-and-notation.md)
|
||||
- [unified-modelling-language](notes/unified-modelling-language.md)]
|
||||
- [use-case-diagrams](notes/use-case-diagrams.md)
|
||||
- [unified-modelling-language](notes/unified-modelling-language.md)
|
||||
- [sequence-diagrams](notes/sequence-diagrams.md)
|
||||
- [use-case-diagrams](notes/use-case-diagrams.md)
|
||||
- [what-are-uml-diagrams](notes/what-are-uml-diagrams.md)
|
||||
- [use-case-diagrams](notes/use-case-diagrams.md)
|
||||
- [entity-relationship-diagrams](notes/entity-relationship-diagrams.md)
|
||||
|
||||
@ -68,6 +68,7 @@ links:[_index](_index.md)
|
||||
- [running-in-person-experiments](notes/running-in-person-experiments.md)
|
||||
- [running-web-experiments](notes/running-web-experiments.md)
|
||||
- [analyzing-experiments](notes/analyzing-experiments.md)
|
||||
|
||||
# Lectures
|
||||
- [04-evaluation-methods-birth-of-hci](notes/04-evaluation-methods-birth-of-hci.md)
|
||||
- [07-heuristic-evaluation-cont](notes/07-heuristic-evaluation-cont.md)
|
||||
@ -82,4 +83,4 @@ links:[_index](_index.md)
|
||||
- [16-distributing-cognition-and-visual-design-typography](notes/16-distributing-cognition-and-visual-design-typography.md)
|
||||
- [17-grids-grouping-alignment-reading-and-navigation](notes/17-grids-grouping-alignment-reading-and-navigation.md)
|
||||
- [18-ethics-in-hci](notes/18-ethics-in-hci.md)
|
||||
-
|
||||
- [22-trends-in-hci](notes/22-trends-in-hci.md)
|
||||
|
||||
55
content/notes/initial-ideas-mind-map.md
Normal file
55
content/notes/initial-ideas-mind-map.md
Normal file
@ -0,0 +1,55 @@
|
||||
- customisable trick generator
|
||||
- trick lists --> users can create lists for the generator to choose a trick from
|
||||
- some built in lists
|
||||
- share lists with friends
|
||||
- options
|
||||
- trick types
|
||||
- jump
|
||||
- rail
|
||||
- pipe
|
||||
- butters
|
||||
- flips
|
||||
- spins
|
||||
- grabs
|
||||
- spin direction
|
||||
- bring back or not
|
||||
- stance
|
||||
- regular
|
||||
- goofy
|
||||
- daily trick
|
||||
- same for all users?
|
||||
- auto notification
|
||||
- schedule
|
||||
- weekly
|
||||
- custom
|
||||
- auto when at an altitude
|
||||
- App widget with daily trick?
|
||||
- search for tricks
|
||||
- options similar to generator
|
||||
- save tricks to a list for generator
|
||||
- link with other users
|
||||
- methods
|
||||
- qr code
|
||||
- url/link
|
||||
- contact
|
||||
- social media
|
||||
- people
|
||||
- friends
|
||||
- coach
|
||||
- parents
|
||||
- features
|
||||
- daily/sheduled trick group
|
||||
- how would this work with altitude detector
|
||||
- share trick lists
|
||||
- community section for trick lists
|
||||
- like spotify playlists
|
||||
- users can share tutorials
|
||||
- Ease of use - (hard to use with gloves)
|
||||
- voice controls
|
||||
- gesture controls
|
||||
- goals tracking
|
||||
- goal lists
|
||||
- daily/weekly/yearly goals
|
||||
- trick generator can choose a trick from goals
|
||||
- share (or keep private) with coach and friends
|
||||
- trick tutorials
|
||||
12
content/notes/into-the-wild.md
Normal file
12
content/notes/into-the-wild.md
Normal file
@ -0,0 +1,12 @@
|
||||
---
|
||||
title: "into-the-wild"
|
||||
aliases:
|
||||
tags:
|
||||
- film
|
||||
---
|
||||
|
||||
|
||||
happiness is only real when shared.
|
||||
|
||||
henry david [083-henry-david-thoreau](notes/083-henry-david-thoreau.md)
|
||||
|
||||
8
content/notes/karl-marx.md
Normal file
8
content/notes/karl-marx.md
Normal file
@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "karl-marx"
|
||||
aliases: marx
|
||||
tags:
|
||||
|
||||
---
|
||||
|
||||
<% tp.file.cursor(4) %>
|
||||
@ -24,8 +24,8 @@ Frequency of collisions and time to find a new space are proportional to the *lo
|
||||
|
||||
# Deletion
|
||||
we cant just empty cells as this will break search. We could:
|
||||
1. we could replace it by a "tombstone" maker. This counts as "full" for search and load purposes, but empty for insertion.
|
||||
2. we search foward form the element we're removing until we find something that belongs in that location or earlier - swap it back into this location and repeat until an empty cell is found.
|
||||
1. we could replace it by a "tombstone" marker. This counts as "full" for search and load purposes, but empty for insertion.
|
||||
2. we search foward from the element we're removing until we find something that belongs in that location or earlier - swap it back into this location and repeat until an empty cell is found.
|
||||
|
||||
[^1]: Since we are able to do about n operation before we need to resize, we can spread this cost among those operation.
|
||||
[^2]: By not doubling exactly, the modulo remainder is "scrambled" a bit thus reducing collions.
|
||||
|
||||
@ -46,7 +46,6 @@ I also tried out some other designs features a black background and round button
|
||||
## Other settings
|
||||
|
||||
|
||||
|
||||
## Trick Options
|
||||
For the trick Options I considered a few three main designs: the swipe/scroll, the modal, and the full screen.
|
||||
|
||||
@ -57,3 +56,25 @@ For the trick Options I considered a few three main designs: the swipe/scroll, t
|
||||
|
||||
## Schedule
|
||||
|
||||
|
||||
# Version 1
|
||||
After getting a general Idea of the basic layout of the app, I compiled my favourite versions of each screen into one design. This allowed to informally evaluate the design and find things to change.
|
||||
|
||||
 
|
||||
|
||||
# Version 2
|
||||
The first Thing I want to change is the schedule/altitude screen. I thought I could remove the separation and combine the two screens. But this didn't work so well. However, I think the ability to switch between meters and feet was good as this improves **user control and freedom**. Also the use of the spinner for time and altitude selection will be familiar to most users. This improves use of **consistency and standards**, and **recognitiona over recall**. I also decided to try a "switch" type design, where the user is forced to chooose between the schedule and the altitude.
|
||||
|
||||
I think think this works much better as it **shows the system status** clearly. And has a less cluttered more **miniml, aesthetic design**. I kept the weekday selection on both screens as the might only want use the altitude system on certain days. This improves, **user control and freedom**.
|
||||
|
||||
I also thought it might not be super clear what the functions of the two options were, especially the altitude option. So decided to add a closable info card with some information. This improves **help and documentation**
|
||||
|
||||
I also wanted to change the way the trick options worked. Instead of have the save cancel buttons I wanted the settings change to have immediate effect, so the user didn't have to save. These changes are in the second row of the first page of version 2. The actual options themselves are largely the same, except I added a header with a back button and removed the bottom save and cancel buttons. Next I changed the dropdown for each of the trick types to individual screens with the commonly used right chevron icon.
|
||||
|
||||
I also added the bottom navigation bar back to the trick options screens to improve **user control and freedom**
|
||||
|
||||
 
|
||||
|
||||
# Version 3
|
||||
After I had mostly finished the Layout. I changed the look to match the snowboarding "aesthetic", by making the app primarily black. However I dont think this design was as easy to use as the normal light design.
|
||||
|
||||
|
||||
14
content/notes/lyrics.md
Normal file
14
content/notes/lyrics.md
Normal file
@ -0,0 +1,14 @@
|
||||
---
|
||||
title: "lyrics"
|
||||
aliases:
|
||||
tags:
|
||||
---
|
||||
|
||||
# Figaro
|
||||
|
||||
It's to hot to handle, you got blue sandals
|
||||
Who shot ya? Ooh got you new spots to vandal?
|
||||
Do not stand still, boast yo' skills
|
||||
Close but no krills, toast for po' nils, post no bills
|
||||
coast to coast Joe Shmoe's flows ill, go chill
|
||||
Not suposed to overdose no-doz pills
|
||||
@ -6,6 +6,8 @@ tags:
|
||||
- info203
|
||||
---
|
||||
|
||||
[full-assignment](notes/full-assignment.md)
|
||||
|
||||
[pdf](https://blackboard.otago.ac.nz/bbcswebdav/pid-2827493-dt-content-rid-18385743_1/courses/INFO203_S1DNIE_2022/Assignment3.pdf)
|
||||
|
||||
[idea](notes/idea.md)
|
||||
@ -18,14 +20,14 @@ tags:
|
||||
- [x] Development [personas-development](notes/personas-development.md)
|
||||
- [x] Primary [Primary Casual Kyle](notes/personas-final.md#Primary%20Casual%20Kyle)
|
||||
- [x] Secondary [Secondary Logan the learner](notes/personas-final.md#Secondary%20Logan%20the%20learner)
|
||||
- [ ] Storyboard
|
||||
- [x] Storyboard
|
||||
- [x] Low-fi Prototypes [low-fidelity-prototypes](notes/low-fidelity-prototypes.md)
|
||||
- [x] drawings stage 1
|
||||
- [ ] drawing stage 2
|
||||
- [ ] more alternatives for navigation diagram
|
||||
- [ ] more intial designs
|
||||
- [ ] document
|
||||
- [ ] add references to design heuristics
|
||||
- [x] drawing stage 2
|
||||
- [x] more alternatives for navigation diagram
|
||||
- [x] more intial designs
|
||||
- [x] document
|
||||
- [x] add references to design heuristics
|
||||
- [x] Hi-fi Prototype
|
||||
- [ ] Presentation
|
||||
|
||||
|
||||
12
content/notes/philosophize-this.md
Normal file
12
content/notes/philosophize-this.md
Normal file
@ -0,0 +1,12 @@
|
||||
---
|
||||
title: "philosophize-this"
|
||||
aliases:
|
||||
tags:
|
||||
- podcast
|
||||
---
|
||||
|
||||
# Episodes
|
||||
```dataview
|
||||
LIST FROM #podcast/philosophizethis
|
||||
SORT title ASC
|
||||
```
|
||||
15
content/notes/philosophy.md
Normal file
15
content/notes/philosophy.md
Normal file
@ -0,0 +1,15 @@
|
||||
---
|
||||
title: "philosophy"
|
||||
tags:
|
||||
- moc
|
||||
---
|
||||
|
||||
# People
|
||||
[[soren-kiekegaard]]
|
||||
[[karl-marx]]
|
||||
[[henry-david-thoreau]]
|
||||
[065-mary-woolstonecraft](notes/065-mary-woolstonecraft.md)
|
||||
[[david-hume]]
|
||||
[[voltaire]]
|
||||
[[bishop-berkely]]
|
||||
[[socrates]]
|
||||
@ -15,9 +15,8 @@ Intro
|
||||
- Time/Project Mangement
|
||||
- Main Issues
|
||||
- Main Non-Issues
|
||||
- Conclusion
|
||||
|
||||
Communication/Division of tasks
|
||||
Communication
|
||||
- Discord
|
||||
- Notes/resources
|
||||
- Webhooks
|
||||
|
||||
@ -1,7 +1,34 @@
|
||||
---
|
||||
title: "reflective-statement"
|
||||
aliases:
|
||||
geometry:
|
||||
- left=10mm
|
||||
- top=10mm
|
||||
- right=10mm
|
||||
- bottom=10mm
|
||||
tags:
|
||||
- cosc202
|
||||
---
|
||||
### COSC202 Reflective Statement - Jet Hughes 9474308
|
||||
#### Intro
|
||||
I was honestly not expecting this paper to be as interesting as it was. The lecture were informative and interesting, and the semester-long project was a joy to work on. My team for this project was great. The member were Myself, Brad, Will, Arlo, and Riley. We communicated using Discord and used Trello for project management. We encountered a few small issues, but nothing catastrophic, and I had some clear favorite parts of the project.
|
||||
|
||||
#### Communication
|
||||
The first thing we had to decide as a team was how to communicate. We agreed to use Discord. I created channels for general discussion, notes and resources, and bug discussion. The bugs channel was rarely used, but the other channel, general, was very lively, and the notes and resources channel was very useful. The notes and resources channel had quick links to the lab book, and other resources. It also had a snapshot of the project tasks and the deadline. One additional thing I added to the server that was immensely useful was the git-updates channel. I set up a gitlab-discord integration which send a message to discord every time a push was made to the repo. This integration was very useful because it made it very easy to keep up with the state of ANDIE. If I were to repeat this project, I would definitely do this again.
|
||||
|
||||
#### Project/Time Management
|
||||
The first thing we did once communication had been established was to delegate tasks to team members. We each selected a task that we were interested in, and the rest of the tasks were to be assigned at a later date. I think this method worked very well, as each of us was able to do something we thought would be enjoyable, and the workload was very evenly distributed. We quickly realized we would need to use a project management tool. One of the group members suggested Trello, which uses a Kanban board. Since many of us had used it before, we agreed this was a good choice. I set up a simple Trello board with 3 lists: To-do, doing, and done. Later I added, a list for ongoing tasks like commenting and unit testing, and a list for extra features we wanted to add. We were then able to easily assign team members to tasks, and track their progress with checklists.
|
||||
|
||||
#### Main Issues
|
||||
One main issue was that more menial tasks like commenting and creating unit tests were left unattended to. Hiding them away in the "Ongoing" task list was not helpful. I think a better way of doing this would have been to add commenting and unit testing to a checklist within each task. I think we should have used checklists within tasks much more in general. My final issues were the (almost) lack of a proper extra feature. Throughout the first half of the second part of the project, almost all of our team was sick. We were able to do the Posterise, negative, and extended filters, relatively quickly. But the Area Select feature created a bottleneck, blocking the drawing and crop features. Luckily, we were able to finish the rest of the features. However, we did not have an extra feature ready. Fortunately, Arlo was able to create the pen drawing feature quickly. Looking back, we should have re-delegated the tasks as soon as we knew the assigned team member was sick. This would have enabled us to avoid the bottleneck and progress faster. I also think we could have found other things to work on while waiting for Area Select [^3].
|
||||
|
||||
#### Highlights
|
||||
My first and top highlight was the Posterise Filter. I decided to implement this using the K-Means algorithm. I was interested to see how a k-means could be done in Java. I was able to create a first version relatively using [this](https://stackabuse.com/guide-to-k-means-clustering-with-java/) article as a guide[^1]. I had some trouble long the way, so when I got it somewhat working I had a little-jump-around-the-room celebration. On the final day of the assignment, I realized that the centroids were not actually changing and that it was essentially using random colors. Thankfully, I was able to fix the issue of the centroids not updating. However, I am still not sure if it works as intended. In retrospect, I should have done better testing for this feature. When I saw a picture split into colors, I blindly assumed that it worked, without actually checking that it was working. If I were able to go back, I would first look at the results of other implementations first, and add more testing.
|
||||
|
||||
Another highlight was creating my own convolve operation class[^2]. I made this to solve the problem of negative and extended filters. I think there probably was an easier way of doing this, but I thought this method would also clean up a lot of the repeated code in the filter actions. The creation of this class went a bit smoother than the Posterise filter. I had [this](http://ramok.tech/2018/09/27/convolution-in-java/) article to use as a guide. I was able to significantly simplify their code to suit my need. However, it ran *very* slowly compared to the in-built java ConvoleOp class. I briefly considered changing it to run on the GPU using a library, but thankfully, Riley was able to speed it up by changing the RBG get and set operations.
|
||||
|
||||
#### Conclusion
|
||||
Overall I think our project was very successful. This was reflected in our mark for part one and (hopefully) part two, and by the fact that the workload was evenly distributed across the team. The main issues were the delays of commenting, the lack of thorough testing. We had a small crunch in the final hours of the project, when we had issues with saving and exporting, but thankfully we were able to get it done.
|
||||
|
||||
[^1]: I just realized I forgot to reference this in the Javadoc.
|
||||
[^2]: I still don't know what to call this.
|
||||
[^3]: This would have been adding comments and testing.
|
||||
@ -5,8 +5,8 @@ tags:
|
||||
- info203
|
||||
- scott-video
|
||||
- lecture
|
||||
sr-due: 2022-06-01
|
||||
sr-interval: 7
|
||||
sr-due: 2022-06-23
|
||||
sr-interval: 20
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
|
||||
86
content/notes/security.md
Normal file
86
content/notes/security.md
Normal file
@ -0,0 +1,86 @@
|
||||
---
|
||||
title: "security"
|
||||
aliases:
|
||||
tags:
|
||||
- cosc202
|
||||
---
|
||||
|
||||
# Growing concern
|
||||
since there is more software, dependencies, and they are getting increaingly complex the "surface area" of risk is growing.
|
||||
|
||||
Speed of development is more important than security.
|
||||
|
||||
Software systems involve a large number of components, and this means they are more likely to have bugs.
|
||||
|
||||
# Elements of Security
|
||||
## Confidentiality
|
||||
- Protecting data from being stolen.
|
||||
- Usually contered using encryption and/or isolation of processes
|
||||
- Encyption is not time proof.
|
||||
- computational power is increasing
|
||||
|
||||
## Integrity
|
||||
- Attacks on data may aim to decieve users
|
||||
- countered using checksums
|
||||
- attacks on code are often *privilege escalation*
|
||||
|
||||
## Availability
|
||||
- DDoS
|
||||
- countered by hosting in multiple countries
|
||||
- use CDNs (content delivery networks) for data objects
|
||||
|
||||
# Dependencies
|
||||
- vulnerabilities in [libraries](notes/libraries.md) extend to your code.
|
||||
- You should
|
||||
- determine and examine your software bill of materials (SBOM)
|
||||
- subscribe to security alerts
|
||||
- plan to rapidly rebuild and re-release your software
|
||||
- use tools to scan software for know problems
|
||||
- However, still use them when appropriate
|
||||
|
||||
# Non-Validation of user input
|
||||
- Assume user input is malicious
|
||||
- Prevent SQL injection attacks
|
||||
- Input from many sources
|
||||
- user docs
|
||||
- config files
|
||||
- env variables
|
||||
|
||||
# Injection Attack
|
||||
## Example:
|
||||
```java
|
||||
String query = "UPDATE pw='NEW_PW' WHERE user='user'"
|
||||
```
|
||||
|
||||
malicious input: Bobbie' OR 1=1 wil change all passwords.
|
||||
|
||||
use SQL prepared statements or secure DB abstraction
|
||||
|
||||
buffer overruns also inject attacker's data:
|
||||
- e.g., C array that too short for data copied in from network
|
||||
- attacker overruns end of the C aray: maybe injects code.
|
||||
|
||||
# resolving problems
|
||||
|
||||
|
||||
# Threat model
|
||||
- should character what you want to protect against
|
||||
- writin standalone software to be used by one person
|
||||
- typially dont have to worry about malicious attacks (on self)
|
||||
- software on a multi-user operating system
|
||||
- do need to think about cross-user data leaks
|
||||
- all OSs are multi user
|
||||
- software that has network availability
|
||||
- your software can and likely will be attacked
|
||||
- targeteted by state-sponsored teams? Good Luck...
|
||||
|
||||
# sec in dev
|
||||
- - security isn't a single requiremtn you can tick off
|
||||
- it needs consideration throughtout the whole system
|
||||
- it is a cross-cutting concern
|
||||
- it is hard to retrofit
|
||||
- notion of security engineering is useful
|
||||
- affects design descision fromt the outset
|
||||
- changes how code is written and reviewed
|
||||
- add a specific type of testing to include
|
||||
- needs examination of how users interact with software
|
||||
152
content/notes/sequence-diagrams.md
Normal file
152
content/notes/sequence-diagrams.md
Normal file
@ -0,0 +1,152 @@
|
||||
---
|
||||
title: "sequence-diagrams"
|
||||
aliases:
|
||||
tags:
|
||||
- info201
|
||||
---
|
||||
|
||||
|
||||
equence diagrams document a *sequence* of particpant interactions required to carry out a use case
|
||||
- actor <-> object
|
||||
- actors are outside the system
|
||||
- objects are otside the system
|
||||
- via a method call
|
||||
- might get a result
|
||||
- object <-> object
|
||||
- lifetime of interactions and objects
|
||||
- when they are created updated destroyed
|
||||
- time is a key aspect
|
||||
- [use-case-diagrams](notes/use-case-diagrams.md) dont have order
|
||||
|
||||
These diagrams are:
|
||||
- detailed, low level, bottom up
|
||||
- behavioural diagram
|
||||
- not structural
|
||||
- common in industry
|
||||
- along with class diagrams
|
||||
- need to be designed and read alongside corresponding class diagrams
|
||||
- e.g., class diagrams with inform sequences diagrams and vice versa
|
||||
- back and forth process
|
||||
|
||||
|
||||
General overview example: [annotated example](https://i.imgur.com/1myG3rU.png)
|
||||
- time goes from top to bottom
|
||||
- however no specific time units
|
||||
- can have actors as participants
|
||||
- but not usually
|
||||
- existence of actor usualy indicates a sequence is owned by a use case
|
||||
- interactions are indicated by messages (solid arrows)
|
||||
- e.g. actor to main menu
|
||||
- actor clicks a button
|
||||
- menu reacts
|
||||
- etc
|
||||
- messges are synchronous
|
||||
- i.e., thing sending message must wait for result
|
||||
- always method calls (or something that equated to a method call)
|
||||
- participants are supposed to be instances of classes
|
||||
- however we are usually more interested in the class name
|
||||
- the dashed lines are lifelines
|
||||
- can also be solid
|
||||
- basically indicate the existenc of something
|
||||
- e.g., Thingform gets destroyed, thingfinder and thing remain throughout
|
||||
- the rectangles (activation bars) indicate when an a thing is doing somethin
|
||||
- caused by incoming message
|
||||
- ended by a return
|
||||
- these can have sub activations
|
||||
- i.e., nested
|
||||
- these can be self-activations
|
||||
- implcit: not all methods return something
|
||||
|
||||
relevant slide:
|
||||
|
||||
|
||||
|
||||
# Messages
|
||||
[example](https://i.imgur.com/XedVmng.png)
|
||||
- direction
|
||||
- <- or ->
|
||||
- easier to under stand if most messages are ->
|
||||
- however this is not always possible
|
||||
- same object used by multiple other objects
|
||||
- an object calls back to the object that called it
|
||||
- can be conditions (guards) [example](https://i.imgur.com/yWTcD1F.png)
|
||||
- only sent if condition is true
|
||||
- able to approximate if-then-else using multiple branches with exclusive conditions
|
||||
- this is better done in activity diagram
|
||||
- looping messages [example](https://i.imgur.com/tcFZ4bb.png)
|
||||
- an asterisk idicated looping
|
||||
- repeat message until condition id false
|
||||
- send messge to each object in a collection
|
||||
- may also be better in activity diagram
|
||||
|
||||
# Interaction frames (UML 2.x)
|
||||
[example](https://i.imgur.com/V1Jhnd2.png)
|
||||
- loop frame
|
||||
- any kind of loop
|
||||
- replaces * notation
|
||||
- opt frame
|
||||
- optional or conditional processing
|
||||
- can replace [] notation
|
||||
- alt frame
|
||||
- if-then-else
|
||||
- can replace [] notation
|
||||
|
||||
one thing that can cause complications is
|
||||
- when something can a top level loop which is waiting for input.
|
||||
- a cancel anytime option
|
||||
|
||||
|
||||
# Basic process of creation
|
||||
|
||||
- identity participants of a use case (dont always need to use a use-case diagram)
|
||||
- use use case to create first version of the activity diagram. as you implement the code update the class and activity diagrams
|
||||
- identify messges required to carry out use case
|
||||
- for each message
|
||||
- it is always sent
|
||||
- is it sent conditionally
|
||||
- is it sent multiple times
|
||||
- assemble messages in correct sequence and attach to relevant lifelines/activations
|
||||
- add returns where necessary
|
||||
|
||||
# Case study ATM
|
||||
|
||||
bank is developing a new ATM system for their customers
|
||||
|
||||
scope and requirements
|
||||
- each customer has one or mor accounts
|
||||
- transaction types are
|
||||
- view balance
|
||||
- withdraw cash
|
||||
- deposit funds
|
||||
- the customer can cancel at any point before final confirmation
|
||||
- customer authenticates by inserting bank card and entering four digit pin
|
||||
|
||||
process
|
||||
- choose account
|
||||
- choose amount
|
||||
- check customer funds
|
||||
- check amount in cash dipenser
|
||||
- results
|
||||
- withdraw amount
|
||||
- dispense amount
|
||||
- remind user
|
||||
|
||||
|
||||
|
||||
this diagam is probably too general for this case
|
||||
|
||||
|
||||
|
||||
note navigability of domain
|
||||
|
||||
sequence diagram
|
||||
|
||||
- [part 1](https://i.imgur.com/PJJBZav.png)
|
||||
- [part 2](https://i.imgur.com/M3jRM8g.png)
|
||||
- [part 3](https://i.imgur.com/PhCYWsy.png)
|
||||
- [part 4](https://i.imgur.com/L0h4nb8.png)
|
||||
|
||||
|
||||
|
||||
|
||||
[full diagram](https://blackboard.otago.ac.nz/bbcswebdav/pid-2894257-dt-content-rid-18429333_1/courses/INFO201_S1DNIE_2022/2022/lectures/lecture_13_atm-withdraw-sequence-full.pdf)
|
||||
41
content/notes/soren-kiekegaard.md
Normal file
41
content/notes/soren-kiekegaard.md
Normal file
@ -0,0 +1,41 @@
|
||||
---
|
||||
title: "soren-kiekegaard"
|
||||
aliases: kierkegaard
|
||||
tags:
|
||||
- person/philosopher
|
||||
---
|
||||
|
||||
Father of existentialism
|
||||
|
||||
"Anxiety is the dizziness of freedom"
|
||||
|
||||
# Religion
|
||||
[078-marx-and-kierkegaard-religion](notes/078-marx-and-kierkegaard-religion.md)
|
||||
|
||||
The function of religion is to organise a commitment to a particular way of life
|
||||
|
||||
Disagreed with [marx](karl-marx)'s opinion that "religion is the opiate of the masses"
|
||||
|
||||
Loss of the individual
|
||||
- lost in infinte
|
||||
- lost in finite
|
||||
|
||||
He thought the best way to avoid these states was to take a "leap of faith" (toward religion), and that the bible was a system for bringing about the highest form of us an an individual
|
||||
|
||||
|
||||
# Anxiety
|
||||
[079-kierkegaard-anxiety](notes/079-kierkegaard-anxiety.md)
|
||||
|
||||
"Anxiety is the dizziness of freedom"
|
||||
|
||||
"The biggest danger, that of losing oneself, can pass off in the world as quietly as if it were nothing; every other loss, an arm, a leg, five dollars, a wife, etc. is bound to be noticed."
|
||||
|
||||
"Anxiety may be compared with dizziness he, whose eye happends to look down into the awning abyss becomes dizzy. But what is the reason for this? It is just as much in his own eyes as in the abyss. Anxiety is the dizziness of freedom."
|
||||
|
||||
People can be lost in the finite or in the infinite. When we are balancing between the infinite and the finite we experience this anxiety, which imbues a sense of dread. After dread comes despair. Despair is a sickness of the spirit, and is often unnoticable.
|
||||
|
||||
People try to "hide" from this despair by attaching themself to something "earthly". This is similar to Kant idea of outsourcing things from what is enlightenment.
|
||||
|
||||
When we are experiencing anxiety we are coming closer to our true self.
|
||||
|
||||
"What I really lack is to be clear in my mind what I am to do, not what I must know what matters is to find a purpose, to find a truth that is true for me. to find the idea for which I am willing to live and die. That is what my soul thirst for as the african desert thirst for water"
|
||||
@ -1,4 +1,4 @@
|
||||
---
|
||||
---
|
||||
title: "typography"
|
||||
aliases: Typography
|
||||
tags:
|
||||
|
||||
@ -9,7 +9,7 @@ tags:
|
||||
# Java -> UML reverse engineering
|
||||
reverse of [uml-java-forward-engineering](notes/uml-java-forward-engineering.md)
|
||||
|
||||
- parse java doe and generate corresponding uml diagrams
|
||||
- parse java docs and generate corresponding uml diagrams
|
||||
- useful to generate models of existing systems
|
||||
- code usually has more detail than can be represented in diagrams
|
||||
- automated diagram layout likely to be ugly ⇒ manual clean up
|
||||
|
||||
Loading…
Reference in New Issue
Block a user