2,063 karma · joined March 4, 2010
On the other hand, having enough people or money to throw at something were never a problem, so…
I really enjoyed this session, but I can see how it could be stressful to others.
Am I the only one who is tired of all these shorthand names?
> Why can’t we put a read-only archive online currently? The Wiki, even in it’s read-only state, was presenting security risks, and it was deemed necessary to take it offline.
> Root cause is Catalina regression that fails keyboard inputs when a UIKeyCommand is registered for the same key. UIResponder chain regression most likely.
Anecdote: I’ve worked on a few large iOS teams at well-known companies. At all of them, we have moved toward building UI in code and specifically banning the use of XIBs and Storyboards (we still use all of Apple’s frameworks — e.g. UIKit). Part of the reason is merge conflicts — in much the same way that merging Xcode project files requires every engineer to understand and be able to parse the syntax when looking at a diff, merging changes in XIBs and Storyboards is fraught with danger (at best).
Open office floor plans are the worst.
You'd be surprised. (Source: I work at a unicorn.)
Building a solid standalone monitoring/metrics package is apparently next up on the "todo list" for Chris McCord (creator of Phoenix): https://www.youtube.com/watch?v=pfFpIjFOL-I
They may not have been thought of that way, but I've very much seen them treated that way.
From the hardware side, maybe. The developer experience for it is a miserable one.
Ouch. It will be interesting to read the results of the investigation as to why the landing thrusters turned off prematurely.