Read on Twitter
Ok. Scenario:
You have done iOS app development 6 years ago when Swift wasn't a thing.
Today, you have a macOS app codebase that is 3.5 years old, a combination of objective C and Swift3, runs only on XCode 9 (current latest version is XCode 12).
You want to add a feature.
You have done iOS app development 6 years ago when Swift wasn't a thing.
Today, you have a macOS app codebase that is 3.5 years old, a combination of objective C and Swift3, runs only on XCode 9 (current latest version is XCode 12).
You want to add a feature.
You use the latest XCode (12), fix all the cryptic compilation errors and update to Swift5 with your limited knowledge of Swift. Now it compiles but there are runtime crashes caused by some kind of constraint layout issues with no helpful logs - breakpoints don't help
You stare at the cryptic NSConstraintLayout errors, the stack trace completely useless. You look through the plain, unhelpful xib files, wincing each time you open a viewcontroller xib that contains a single, empty View.
You comment out all calls to layoutSubviewsIfNeeded - still crashes, remove constraints - nothing shows up, can't reach the crashing app flow, change build options > debug mode to DWARF with dSYM, still seeing assembly code. Nada.
You decide to download XCode9 to be able to at least run the app and work on updating it that way, for the time being, because there's an urgency for maintenance. Owait, XCode9 is not supported on macOS 10.14+; your macbook is the latest, 10.15.
Okay, you pull out your old macbook which is dead, so you look for the old macbook charger and plug it in to charge. Finally, you power it on, it has macOS 10.11. XCode 9 requires macOS 10.13+. Your macbook's hardware doesn't support macOS past 10.11.
You look at the 4 screens on your desk. "How am I not a 10x engineer even with 4 screens????" you think to yourself. You close them all. The day has won for now.
Stay tuned to find out what happens on the next episode of..
Süm Code Chronicles
*outro*