Thanks for posting that educational video! Was at WWDC 2022 and would love to have a salad like there were there today (learned at WWDC that rich people can afford actually nutritious food (part of what causes disparity) that also tastes great…and that made Me realize how much of the food I have eaten in My life has had relatively little taste compared to the much better food that rich people can afford). Had some interviews with Apple after that, but sadly haven’t been hired yet. Actually I had to declare one of the interviews basically over when the interviewer said he hired a C programmer that had never done OOP…for a role doing OOP…and then that same interviewer HORRIBLY used the ee pronunciation of a certain background services utility that is ACTUALLY pronounced dae and has a VASTLY BETTER meaning than the SEVERELY WRONG “dee” pronunciation…I declared that interview was SOOOOOO OVER when he said that.
By the way, there were some app performance issues when nested a bunch of SwiftUI views. Any recommendation for eliminating the app performance issues SwiftUI caused? (There aren’t any animations, but there are view size relation calcs in those subviews). So far swiftui has sadly inspired to find best programmatic UIKit tool such as snapkit. Felt as though swiftui was such a fcking scam and apple fail.
There is a some sense of familiarity when it comes to Sean's Videos. I have been watching your videos even before I started my career 4.5 years back. I still enjoy these videos so much.
Great video as always Sean! I have an extra tip for number 18: You could put a release build compile time error so you can make sure you change or do something before releasing the app: #if !DEBUG error(“change these before release!”) #endif This way the error will only happen when archiving for release, so you can freely test everything you want in debug mode without worrying that you would forget to do it in the end
8:50 we can get an error without the preprocessor command. Just write any text like "hello" on an empty line and it will say something like "Cannot find 'hello' in scope"
Ah dude this is honestly my biggest struggle with Swift and Apple dev stuff in general. I'm a f---ing boss with Vim and I'm ok going back to vscode when I need to for Jupyter stuff or the occasional debug sesh... but X-code is such a huge change. It's super powerful and I admire the people that are super good with it, but it's been a struggle for this vim-bro.
Got to learn to do both. An IDE is just a tool to help you finish a task. You should have the skills to complete it regardless of the tool. There’s a lot of documentation.
Nice video. I am used to appcode (RIP) so I found this video quite interesting. Unfortunately Xcode is nowhere close to the refactoring capabilities of appcode and in general code editing isn’t xcodes strong suite. They should have spend more time on configuration instead of fancy animation. I am really hoping for a major overhaul at wwdc so Xcode won’t be the last ide without ai code sense.
Also regarding indentation, ⌘] will indent the selected lines and ⌘[ will outdent. I use these all the time because the same keyboard shortcuts work across many text/code editors, and because I’ve never been a big fan of auto-indent (maintain indent when pressing return: yes, decide the indent for me based on context: no thank you).
Another Single Asset App Icon tip: Xcode will take an use an SVG without issues. I shows a warning and I think I had to do some trickery of initially giving it a PNG then swapping it out in the filesystem with an SVG, but it builds and generates a PNG for device without issue.
i am software enginner working for several 3years. I want to become an Apple software developer (using Apple product development language). What do you think about the learning materials and the future as an Apple developer?
Great tips. Unfortunately, not all of them works for me. The tip 17 “Extract subview” at 7:23 doesn’t work for me. I use Xcode 15.0.1. Right-click brings the popup with multiple different functions grouped in sections. The multiple extract functions are under the “Refactor”, but it is no “Extract into Subview”. Am I do something wrong or Apple removed this function in XCode 15?
If I execute print, I want the print output currently in the console to be cleared, and the new print output to appear there. It's annoying to click on the trash can icon every time. I haven't found anything in the settings.
I just downloaded Xcode on my Mac (Ventura) but when it asks me to type in my password after reading the lil policy agreement thingy, it keeps rejecting my password thought it’s correct. What could I be doing wrong or how can I bypass it?
Excellent video as always! There's one thing I can't get to work though. From 17:07 to 17:19 you demonstrate option clicking a file in the Navigator and then hovering over the existing split panes to decide where it should go. That does not work for me. When I option click the file it immediately goes to a seemingly random split pane. Is there some setting I need to change to enable the behavior in the video?
hmmmm... i'm not sure. It's always worked that way with default settings for me. Do you have more than 2 editors open? If you only have 2 open, it will automatically open up in the secondary window. This feature only works with 2+ editors open.
@@seanallen Yes, I have two editors open when I option-click a file in the Navigator. But it still just immediately places the file in one of the open editors. After you option-click a file do you need to hold anything down while hovering over the open editors?
@@seanallen I tried again with 3 editors open and I get the same behavior. The file that I option click in the Navigator goes to an arbitrary editor and doesn't wait for me to hover over one and click.
I figured this out! You need to option-shift-click the file, not just option-click it. This works regardless of the number of editors open, even if it's only one.
I'm AppCode user and because it will be sunset next year I'm trying to get used with Xcode. But its like a nightmare... All Xcode users that I have worked with making a lot of grammar mistakes. In the video there was section about Spell Check. I tried and it much worse than AppCode propose. In AppCode we can fix or add to dictionary with Alt+Enter shortcut, not touching mouse (and it will actually apply rename in all places needed). In Xcode - CMD+: and then we need to interact with this badly designed popup to pick change and it will correct only one place. Very bad user experience... Quick Refactor - Extract View - Not quick at all. Extract, rename, add property, change init signature. disgusting Hope next year there will be some improvements for refactoring otherwise I will need to change language or suffer in Xcode. Also Copilot would be useful - save a lot of time for boilerplate code.
LOL…warning list…worked hard to make an app that has had less than 150 US DOLLARS in profits in a month…as if there was any reason worth having a warnings list that was ONLY those manually specified
hey sean! i love your videos! but you talk too fast, and in a monotonous (although high energy, which is appreciated!) way. its makes it difficult to absorb
