We developers spend so much time focusing on the details of our work that we sometimes forget about the big picture. The presentation below from try! Swift Tokyo has some really helpful perspective. π€―
Think about building the right thing before building it right.
Why are you making software? Know your motivations. It affects how you do your job.
Who do you write code for? Think about how you relate to your company and the end user.
What happens when your tech stack changes? Be resilient in your career. Try new things while also shipping apps.
Be less precious about code.
Realistically, how long will this code last? How robust is robust enough? Be pragmatic. Almost all the code Iβve written in the last few years is gone by now, either retired or completely rewritten.
Donβt try to be perfect. Donβt hold back out out fear.
Real artists ship.
Steve Jobs
How often do you test? Unit tests are a means to an end. Passing unit tests alone does not mean itβs a good app.
A great article via iOS Dev Weekly on defining a design system for your app. A design system ensures consistency, efficiency, accessibility, and reusability.
A design system defines the visual language of a product’s design.
It’s looking easier than ever to learn from Stanford University. The Computer Science department has posted their latest class on Developing Apps for iOS online. π€―.
It’s free. It has lecture videos, handouts, and assignments. As far as I can tell, you get everything but grades and a diploma. π€·π»ββοΈ. But feel free to make an app!