4 ms·
So I understand you have Objective-C experience but not Swift experience? It was so easy to pick up on Swift, just remember to never force unwrap and always use
by dep_b 10y ago
So I understand you have Objective-C experience but not Swift experience? It was so easy to pick up on Swift, just remember to never force unwrap and always use guard or if let. Just stick to that religiously even when it doesn't make sense sometimes and a dramatically more stable app will be your reward.
Of course you should try to actually do something useful inside the guard else so the user knows what went wrong or just log it with a remote logger so you can fix it for your next release.
The hard part is maintaining a large Swift application, but as long as your clients are paying the bills you shouldn't worry as a freelancer.
- wsc981 10y agoI have Swift experience (about 7-8 months for my own tvOS game) and I like the language a lot. It is not hard to pick up Swift. But to write Swift code with the same quality as my Objective-C code, I would need more experience. Which is why many clients preferred to pick up a more experienced Swift developers for some projects. After all, idiomatic Swift code can be quite different from idiomatic Objective-C code. Learning the Swift idioms takes some time. I think for a freelancer a client has much higher expectations than from a permanent employee. An employer doesn't want a freelancer to learn (much) on the job. The employers is paying for an experienced developer that can deliver on quality from day one. After all, freelancers are usually much more expensive.
- pjmlp 10y agoThe sad part of it, is the vicious circle that side projects aren't accepted as experience, even if cool ones, and one doesn't get the contracts to actually be able to earn the experience as official customer projects. Been on that path a few times...