add contents for ios notes

Author: ANYMS-A

_posts/2023-01-01-about-the-author.md

@@ -0,0 +1,93 @@
+---
+layout: post
+title: "iOS Development Notes"
+author: "Yalun Hu"
+categories: journal
+tags: [Blog, iOS, Swift]
+
+image: mountains.jpg
+--- 
+
+## 如何快速查看文档
+
+在Xcode中按住Option然后点击对应的关键字或builtin types，便能快速跳转到对应的文档下。
+
+## 类和结构体对比
+
+Structures and classes in Swift have many things in common. Both can:
+
+- Define properties to store values
+- Define methods to provide functionality
+- Define subscripts to provide access to their values using subscript syntax
+- Define initializers to set up their initial state
+- Be extended to expand their functionality beyond a default implementation
+- Conform to protocols to provide standard functionality of a certain kind
+
+For more information, see [Properties](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/properties), [Methods](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/methods), [Subscripts](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/subscripts), [Initialization](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/initialization), [Extensions](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/extensions), and [Protocols](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/protocols).
+
+Classes have additional capabilities that structures don’t have:
+
+- Inheritance enables one class to inherit the characteristics of another.
+- Type casting enables you to check and interpret the type of a class instance at runtime.
+- Deinitializers enable an instance of a class to free up any resources it has assigned.
+- Reference counting allows more than one reference to a class instance.
+
+For more information, see [Inheritance](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/inheritance), [Type Casting](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/typecasting), [Deinitialization](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/deinitialization), and [Automatic Reference Counting](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/automaticreferencecounting).
+
+## 协议[Protocols]
+
+A *protocol* defines a blueprint of methods, properties, and other requirements that suit a particular task or piece of functionality. The protocol can then be *adopted* by a class, structure, or enumeration to provide an actual implementation of those requirements. Any type that satisfies the requirements of a protocol is said to *conform* to that protocol.
+
+Multiple protocols can be listed, and are separated by commas:
+
+```swift
+struct SomeStructure: FirstProtocol, AnotherProtocol {
+    // structure definition goes here
+}
+```
+
+If a class has a superclass, list the superclass name before any protocols it adopts, followed by a comma:
+
+```swift
+class SomeClass: SomeSuperclass, FirstProtocol, AnotherProtocol {
+    // class definition goes here
+}
+```
+
+## MVVM设计模式
+
+Model-View-ViewModel is a design paradigm. 
+
+It must be adhered to for SwiftUI to work.
+
+### Model
+
+- UI Independent
+- Data + Logic
+
+### View
+
+- The reflection of the Model
+- Stateless
+- Declared(只有“var body”决定了view是如何绘制的)
+- Reactive (Always reacting efficiently to the change on the model)
+- Automatically observes publications from ViewModel( or subscribe what they interested at from the ViewModel) .Pulls data and rebuild itself.
+
+### ViewModel
+
+- Binds View to Model(so the change on the model cause the view to react and get rebuilt)
+- Interpreter (between Model and View). Help View code stay clean and neat.
+- Gatekeeper.  
+- Constantly noticing changes in the Model
+- Publish a message globally once any change in the Model is noticed (avoid have any connection to any of the View that using it to access the Model)
+- Processing User Intent(Change the Model based on the events occurs in the View)
+
+### Rules in MVVM
+
+- The View must always get data from the Model by asking it from the ViewModel.
+- The ViewModel never stores the data for the Model in side of itself.
+
+
+
+
+

_posts/2023-07-16-ios-dev-notes.md

@@ -4,15 +4,35 @@ title: Welcome to Algorithmic!
 permalink: /about
 ---
 
+## About Algorithmic
+
+![sky](/assets/img/about/shanklin.jpg)
+
 Algorithmic is a place where I share my technical notes at.
 
 Hope you can find something you're interested in my blog.
 
-![sky](/assets/img/about/shanklin.jpg)
-
 ## About the author
 
-[Hi I'm Allan!]({{ site.github.url }}{% post_url 2023-01-01-about-the-author %})
+![me](/assets/img/2023-01-01-about-the-author/author.jpg)
+
+Hi there! I'm Allan.
+I’m a physics major turned programmer.
+I got my Msc of Artificial Intelligence in the University of Southampton in 2019.
+
+I started to work at [SynSense](https://github.com/synsense) as an Algorithm Engineer from 2021.
+Before that, I worked as a machine-learning researcher at a game start-up in Chengdu, China for about 1 year.
+
+My research interests consists of: 
+
+- Machine Learning
+- Computer Vision
+- Neuromorphic Computing
+- Heterogeneous Computing
+
+etc.
+
+Hope you can find something you're interested in my blog.
 
 ## Blogs