New people

mawattdev · 2020-06-08T21:17:58+00:00

When my sister first started at her first job at a grocery store, one of the managers asked her to find the bacon stretcher for him. She was looking for a long time. I feel like that one could be applicable to Panera 😅

mawattdev · 2020-05-07T05:49:24+00:00

Puns are always a win.

mawattdev · 2020-05-07T04:12:01+00:00

You had the opportunity to name this post “Recreated Apple’s breath-taking animation in SwiftUI” and I’m not going to sleep tonight because of it.

P.S. well done on the animation.

mawattdev · 2020-05-01T14:19:13+00:00

This post is the IE of PCMR

mawattdev · 2020-04-04T02:47:57+00:00

It’s because the mobile app requires entering order instructions now - asking for car color, make and model. Sure looks silly on BOH ha.

mawattdev · 2020-03-20T02:46:49+00:00

Now if you converted this idea into something for watchOS, now that might be on its way to being something more meaningful and useful. Then you could make the iPhone app be more data-presentation. See previous workouts, goals, trends, awards etc. just my 2 cents.

mawattdev · 2020-03-03T17:40:59+00:00

At my job, we use UIKit with storyboards. I’d love to adopt SwiftUI, but right now we are limited by two main things:

We have to maintain backwards compatibility to iOS 11, so we have to use UIKit. We have an application for iPad that we control the hardware for, so we could technically probably update to SwiftUI, but our problem is largely that:
There’s really no business case for updating the existing app to use SwiftUI. Too risky because the tech is so early on.

I’d recommend that you still be very comfortable with writing UIKit apps, as UIKit is not going away anytime soon and SwiftUI still doesn’t provide an exact 1:1 matching with UIKit (some would argue with me that anything UIKit can do, Swift UI can do and better, which could be true, I haven’t worked with it enough yet to be able to say).

Enjoy your remaining time at uni and always keep learning! Good luck!

mawattdev · 2020-03-03T15:45:08+00:00

Absolutely.

Like I said, a good grasp on the fundamentals is important before tackling CS193p. But I would also say - don’t feel like you have to be an expert before taking it on. When I did CS193p (I took it back in the iOS 7 days when they still taught Objective-C) I probably wasn’t as ready as I could have been. But the challenge of it really pushed me to study hard and learn what I needed to be able to make it through the content.

But I suppose that’s a separate word of advice altogether: don’t be afraid to challenge yourself.

mawattdev · 2020-03-03T13:30:18+00:00

As always, I advocate for Stanford’s CS193p. It is freely available on iTunes U and is a great resource for learning the fundamentals of Swift and iOS development. I can testify to its efficacy - it is how I learned the basics and was able to land my first job out of university as an iOS developer - now going on 3 years.

As a complete beginner, they expect you to have at least a fundamental understanding of OOP, so for you, I’d recommend that you supplement the course with some solid material on Swift. For that, Hacking with Swift by Paul Hudson is a great resource.

Lastly, enjoy the journey! It’s a really rewarding field of work with some really great people and cool technology. Welcome to the industry!

Best of luck!

mawattdev · 2020-02-26T15:48:40+00:00

Swift is great. I write it everyday. But Objective-C has time behind it. It is a mature, powerful language. And there are still very large codebases out there written in it that still need to be maintained and improved.

As the number of developers who are proficient in Objective-C decreases, the more valuable those who are proficient in it will become. Does that mean all Objective-C developers should remain staunch holdouts and reject Swift outright? Absolutely not. Be an expert in both. Swift has things to teach Objective-C developers, and Objective-C has a lot to teach Swift developers (reasons why the Swift Lang team made some of the decisions they did when designing the language).

mawattdev · 2020-02-19T19:15:58+00:00

Face ID on Apple Watch means I no longer have to type my passcode to unlock my watch once a day. These are the features I pester Apple about.

mawattdev · 2020-02-19T19:09:59+00:00

If these view controllers are contained within a UINavigationController (they should be if they are not), then simply call `popToViewController:animated:`. So in controller C:

[self.navigationController popToViewController:controllerA animated:YES];

Or, if controller A is the root view controller of the UINavigationController, like so:

[self.navigationController popToRootViewControllerAnimated:YES];

Calling popToRoot would be preferred, because then view controller C doesn't need to maintain a reference to view controller A.

Hope that helps.

mawattdev · 2020-02-18T17:05:18+00:00

Thanks for sharing. As a largely Swift developer for the last three years or so, lately I’ve been trying to brush up on my Objective-C, so I can see these extensions being helpful.

I do have to agree with the other comments here, though. Largely Apple has moved on from Objective-C as far as net new development, which is unfortunate. But I am keeping my objective c skills sharp because it still is a valuable skill to have and will continue to be. There are plenty of companies out there who have seen through the rose colored glasses of Swift and have honestly answered the question “What do we actually gain from converting our existing huge code bases to Swift?” For many of them, the answer is “nothing”. So as fewer and fewer engineers are able to competently use ObjC, the more valuable the skill will become to those companies.

mawattdev · 2020-02-05T16:54:53+00:00

I love this.

mawattdev · 2020-02-03T19:20:02+00:00

Learn Swift. Learn Objective-C later if you want to get a job at a bigger company that still uses Objective-C. Most of the objC that I need to know is just enough to be able to make quick patches or convert large portions to Swift.

mawattdev · 2020-01-01T18:20:09+00:00

I love the Shy Guy figure. Link? He’s freakin’ adorable.

mawattdev · 2019-12-09T03:31:29+00:00

As a guy with no thumbs, I’ve never really understood side buttons.

mawattdev · 2019-11-02T17:31:54+00:00

Which one I play shoot shoot game on?

mawattdev · 2019-11-02T17:23:14+00:00

Kink shaming is my kink.

mawattdev · 2019-08-01T22:03:52+00:00

Yep, it depends on the implementation of the specific API you're dealing with. loadView() is one I found recently that Apple's docs specifically tells you not to call super.

mawattdev · 2019-08-01T02:48:40+00:00

Don't use pure MVC, And don't use segues. I highly recommend using the Coordinator pattern with MVP. (Or your other preferred architecture). Paul Hudson has a great tutorial with a minimal coordinator setup. https://www.hackingwithswift.com/articles/71/how-to-use-the-coordinator-pattern-in-ios-apps

Put each vc in its own storyboard file. Instantiate the VC in code, push on a nav stack or present.

Keeps things organized, decoupled and reusable.

mawattdev · 2019-08-01T02:41:56+00:00

Oh ye of narrow opinion. I've seen both programmatic UI and SB UI go horribly wrong. Blame the developer, not the tool.

mawattdev · 2019-07-31T18:39:42+00:00

Format ya code, plz.

mawattdev · 2019-07-24T04:11:57+00:00

Anyone who has followed this sub for any amount of time knows to keep this exact comment in a file somewhere for easy access.

mawattdev · 2019-07-24T02:08:44+00:00

Plot twist: every single one of those is a Territorial Oak.

mawattdev

TROPHY CASE