2015 UIKonf Notes
UIKonf was one of a kind, it combined: high level talks + great networking + good wifi signal. It was my first time there and I’m looking forward for next year.
Mike Lee — “World Modeling”
- The modern world will collapse if we don’t change and become more sustainable according to this paper.
- You can use a programming language called Modelica to help you model complex system based on equations.
Natasha Murashev — “Swift Thinking”
- Should use more value type, e.g use classes only when you need a mutating object (you need to keep a state) for the other cases Structs are better.
- Enums and tuples are also value types.
Reactive Native Workshop by Facebook
Reactive Native is a very powerful and promising technology, Nick Lockwood gave a small workshop on how to use the framework.
- “Functional UI”: Takes a state and returns a view.
- It uses Flow to make Javascript “safer”.
- You can describe your view using JSX.
- The table view generated with React Native doesn’t support view recycle but removes the cell view when it is not visible.
- You can have Reactive Native + native code on the same project.
Claus Höfele — “Practical WatchKit Development"
- You can use Darwin Notification Center to communicate between the phone and watch.
- The WATCH apps should complement the user interface. (an extension of the phone app)
Marcel Weiher — “Software Architecture in iOS and OS X applications”
- Swift helps developers to solve problem on a more “algorithmic layer” rather than the daily basis UI problems.
- Objective-C + Smalltalk = objective-smalltalk.
Tom Adriaenssen — “Async View Controllers”
- If you have to deal with very large and complex view, it is better to compose using small view controllers.
- IIAsyncViewController
JP Simard — “Fixing the Swift Tooling Problem”
- The community can work on the fill the lack of tooling for Swift.
- Class-dump to do some reverse engineering.
- Swift Abstract Syntax Tree (AST)
- SwiftLint.
Ash Furrow — “Teaching and Learning”
Very inspiring talk on why you should aways blog and contribute to open source.
- Should blog on daily or weekly basis.
- Contribute to the community.
2nd day
Halle Winkler — “Duct-taping the gates of chaos shut: the weird, little, useful, sustainable indie (by design)”
- OpenEars
- HWHorrorShow
- If you are very worried about a problem you should stop, think deeply about it, what is the worst thing that can happen and how will you going to deal with it for about 4–5 minutes and then stop thinking about that and move on.
Brian Gesiak — “iOS API Design: Swift Patterns”
- Kent Beck: “It’s all about trade-offs” when deciding which a pattern to use.
- Composing X Subclassing — Composing is more preferable.
- Prefer immutability.
- Use @avalibilty when deprecating code.
- Use typealias.
- JVFloatLabeledTextField
Joe Burgess — “Learning Swift Through Lessons in Haskell”
- Some intersting Haskell frameworks: Yesod, Heist, Blaze, Snap.
- You can use Enums to have a pattern matching.
- Partial application
Chris Eidhof — “Functional View Controllers”
Jens Ravens — “Functional Reactive Programming without Black Magic — Build your own ReactiveCocoa from scratch”
Saniul Ahmed — “Prototyping Touch Interfaces (and my open-source story)”
Maxim Cramer — “A Journey into Design”
- Think about design upfront before doing (like code)
- A design should be consistent.
- Design Hackers.
Graham Lee — “Object-Oriented Programming in Objective-C”
Very powerful talk and I think biggest take way is:
Get Marcio Klepacz’s stories in your inbox
Join Medium for free to get updates from this writer.
KNOW YOUR PARADIGM: If your are doing O.O write code that is O.O don’t fall into traps that make you write Procedural Programming with an O.O language, think about object sending messages, methods shouldn’t return void.









