🦅There is a terrible amount of risk for everyone that wants to build apps and publish them in the App Store: you need to build the app and submit it to know if it's allowed.
https://t.co/qkMPbtypt7
🐓"But, after you publish your app to the App Store, what then? It depends. If your purpose is to try and make a living as an indie developer, then unfortunately publishing your app to the App Store is only the first step in an arduous journey."
https://t.co/OAyKPyOOyN
🐥This is excellent Twitter thread by Mike Sanderson explains why it's literally impossible to "correctly" size a multi-line label in UIKit (or any framework whatsoever).
https://t.co/5bD1byTJBg
🐣"I have an idea for an app..."
If I had a quarter for every time I heard that phrase 😅. Well, you can learn how to build your own! And you can learn from the best: Apple engineers.
https://t.co/XfjMOwqK72
🦅The reason I have been wary about SwiftUI for all this time isn’t about SwiftUI, but about Apple. When it comes to UI, Apple is lacking a clear direction for developers.
Great thread by @featherless on SwiftUI.
https://t.co/qXbue3pX5f
🐓Enter @amyngyn clearly explaining how to behave yourself during an interview. The advice given is excellent. Best of all is the fact that she clearly has a path to follow.
https://t.co/znVMW4thTW
🐥 Concepts become more important as you go on your journey because problems grow more and more complex. You go from following tutorials to trying to build your own solutions and, hopefully, you’re failing spectacularly.
Nice article by @jhandguy.
https://t.co/uoW926GFxH
🐣 Following tutorials is the easiest way to get better. You have to do things to improve your skills. However, setting a concrete goal is difficult.
Here's insight regarding goals from Jason Fried.
https://t.co/gUmMoMz3um
🦅 I saw someone ask "Does a senior iOS developer need to know Objective-C?" and I was (almost) literally stunned by some of the responses saying "no".
I shouldn't be surprised, but still. A good take on the Obj-C -> Swift migration by @taquitos.
https://t.co/NnDOfvSwtA
🐓 This article by @hashnode explains the basics of localization in SwiftUI. That should be enough to get you started and will absolutely be a good talking piece when you're in an interview process.
https://t.co/YC3n7nKkYV
🐥I'm sharing because it's important to remember that you will be dealing with designers while at work and being able to provide meaningful feedback is important. It gives you street cred and increases team morale.
A great twitter thread by @lobau!
https://t.co/qIs5ohJisO
🐣 @StewartLynch's video tutorials are excellent, not only because you get to build something that you can show other people, but also because you get to see how someone more experienced than you uses Xcode.
https://t.co/1NDS27vOWz
🥚 This is the complement to any practical intro course out there.
Here, our breadth will be minuscule: we will explore only 14 lines of code. However, our depth will be vast. We will explore the same piece of code over the course of several articles.
https://t.co/M8R3MDh7Z5
🦅You need to get out of that phase and start understanding why things happen, while keeping your eyes on the prize: shipping. That’s what makes Rob’s question powerful: should I understand things or should I ship things?
https://t.co/IowFkYzPlk
🐓Your #1 goal when you’re a junior is to get that job and, guess what? The easiest way of doing that is having an online presence.
Great article by @hybridcattt!
https://t.co/f5L99NEHcd
🐥The algorithm – what the code does – is usually going to be understandable to everyone that can read code; but there is always more than just what it does, isn't it?
https://t.co/Jx2OREF02x
🐣There's great tutorials out there, but there's no substitute to hearing it straight from the horse's mouth.
This great tutorial by Apple on SwiftUI is great if you're diving into SwiftUI.
https://t.co/jkKHRGy8Lo