The problem with the labs is that the slots fill fast and you end up waiting in line for hours behind developers asking the most basic of questions. I really wish they'd do two conferences — one for those new to the platform and another that would be a deep dive for the experienced devs.
Sometimes, the labs are completely useless anyway. I had a question about masking text glyphs to CGPaths with the new UITextKit stuff last year. I stood in line for an hour and a half to ask my question.
I sat down with an Apple engineer who did not have a firm grasp on the English language, and he pulled out his laptop and googled my question right in front of me. He clicked the first Stack Overflow post, saw it didn't have the answer I was looking for, and sent me on my way.
Words cannot describe the rage I had at that moment.
Was that an engineer, or an intern? Interns often staff labs, but they're usually taught that anything beyond an introductory question warrants seeking out the appropriate experienced engineer and introducing the developer to them. Heck, even real engineers who simply don't have expertise in the area know how to find the right person who does have the appropriate expertise.
Googling or using Stack Overflow to answer someone's question is simply wrong. Even if it was a really basic introductory question.
Maybe my math is off, but I calculated $35/mo for medium utilization m3.medium vs $32/mo for heavy utilization. In that case, I don't think a heavy utilization reservation makes sense but a medium utilization reservation still might (as you're saving ~$20/mo over on-demand).
Janky way around it: bundle your assets separately and put them on S3. It's a crappy user experience, to be sure, but it at least doesn't waste disk space. Granted, you can't do that with all your assets (default.png and icons).
I'm not saying that Apple doesn't need to fix this, but there are some other approaches.
iOS has support for something called XPC. IIRC, it's how the mail composer, etc is invoked by apps (behind the scenes). I'd be very surprised if the API isn't made public in the next version of iOS, which would help facilitate some of these things - it would at least allow easier app-to-app integration.
Not detracting from the feeling that it looks really hard to do, but I think some people are just wired to think about this kind of stuff naturally — for them, it's more of a sense of how things should be framed than a second-by-second analytical breakdown.
Having studied drawing and painting in the last few years, composition is one of these things that I just didn't get. Then it suddenly clicked, mostly by switching to photography to experiment quickly with framing (crop it in photoshop), interesting leading lines and such.
It now feels totally natural, but the road to it was totally obscure for me until I just started taking tons of pictures. Interestingly, I now usually focus on composition / shape / focal points "consciously", planning it out, doing designs, while the more "technical" side of painting (mixing colors, brushstrokes, dark/light) is totally muscle memory.
I have made a lot of music, until it felt "part of myself", then tried out painting/drawing, which is now an integral part of my life and way of seeing the world. But my primary background and ultimately my "self-identity" is software. It is funny how art is pretty much the opposite in terms of process: I will consciously and "technically" work on the part that will affect the viewer/listener the most (composition, buildups/breakdowns in music, tension/relaxation, color/shape/form), and once a good "solution" is found the technical part of it kind of solves itself.
In software, I prefer working on system level things, threading designs, database / scaling, embedded systems. The architectural part of the system is very intuitive, I usually have an idea pop up in my head or while showering. They are often wrong, but I take care of that by doing a lot of miniature systems in their own branches and discard them when not good. However, the technical side of implementing that idea of a design is extremely demanding, and needs iterations and thinking and just plain focused work.
Yup. A football player who dashes into space and makes a cross to another player who will be in open space is making tonnes of calculations in his head about moving bodies, acceleration, etc- but he isn't, either. He's internalized such thinking. Same for musicians, and same for artists of any kind.