allsystemsgo

That's correct. UIKit isn't like, baked into Swift. Whatever platform you're writing for would need to provide to you UI components and then some.

But, that wouldn't make any sense to include UI components in a programming language. And I think the interest level is already "spiked".

Apple Pencil is pretty incredibly and trumps the stylus offered by Microsoft IMHO.

They'll likely put a lot of emphasis on their services number(s), which is growing substantially.

Dev? I wouldn't think so. Autolayout and size classes handle most of that.

Even being in California? Salaries I've seen have been not that great considering the cost of living. If I can get 6 figures in the southern states, why would I go out to Twitter/FB/Google etc?

Oh my god. Thank you!

I'm glad to see such an active Swift community. There are a few too many newsletters though however. I actually subscribed to the Swift.org mailing list and it's terribly difficult to follow. It's like reading a giant email thread. Actually, that's exactly what it is. It's pretty unpleasant and it definitely detracts me (and I imagine others) from contributing to the conversation. The thing is though, that's really the only newsletter I want to follow. I personally get a bit anxious about submitting my email to yet another newsletter. I have no idea what's being done with my email address or if it will be used for profit.

I'm sure their hardware engineers would beg to differ.

Agreed. It creeps up on you too. Always be looking for the next great learning opportunity.

This comment feels a bit underhanded. The free speech argument is pretty good, is it not?

HN is just a forum. I think this article is referring to official PR statements from major tech firms.

Haven't looked recently but I think the Google Images API is really expensive to use.

Meh. Developers will always be in demand. Yes, unicorn startups like "Yo" might have a bad time but, aside from that, I'd feel safe in continuing to be a bit picky.

Easy on the spam buddy.

totes ma goats.

I would think it would be the opposite.

Yeah I disagree. I work for an agency that's almost all giant big-brand apps. You just task developers with separate sections in the app. You can use multiple storyboards in your app (which comes as a surprise to some). So you break down the user flows so its more manageable. The merge conflicts should be few and far between.

How is setting up constraints a pain in xibs? It's hardly anymore difficult than typing it in code.

Right but you'd have to document what each constant represents. Interface builder gives us a universal language. You know what the UI will look like or how it will resize etc. because it's right there. There's no confusing constant names with magic numbers. You know the why behind the constraint values because you can see it.

Wait, why would you fix your layout bugs by searching through XML? Why not just use interface builder?

> You don't have to forego all of the features of the IDE just because you prefer to do UI layout in code.

I don't understand why you would do your UI layout in code if you can avoid it. If someone ever joins my team or inherits my code base, they're now partly responsible for maintaining the UI. Xib's and storyboards help with maintainability, legibility, and drastically lower the number of lines of code. The author even says:

> Find an example program that works then reduce lines until I can reduce no more making a minimal example that works - then understand every line

If you care about the line count, then why are you doing all your UI in code?

I have 3/4 of an MBA. Stopped with just an MS in IT Management. I could finish it but, didn't seem that useful.

This will end well.

I use my own machine. That and you have to keep in mind a few things. Does the company actually have the money to spend to go after a developer who made some simple app? Would doing so piss off their entire engineering department? Is it really worth it to them? Usually the answer is no.

Not that any of the above matters since I do this on my own time, with my own resources.

Why would you quit your job to make an app? I have bootstrapped 3 apps and pushed them to the app store in my own time.

To be fair, every time I do it, it's hard. I have to prepare my family that I'm undertaking something that will take up a lot of my time. It's tough but, they know I love it.

Great, I'll reach out to you.

I've used careercup a few times, primarily for resume review. I've had mixed results though.

Appreciate the feedback.

I've actually seen your posts before and know about your service. I'd love to check it out but, I'm out of state :-( I'm honestly surprised there isn't a service where I can just do a google hangout with someone to help get me up to speed.

It was confusing to me. "Wait... I'm favoriting it? What does that mean? I mean I like it but, why favorite the tweet? Will I want to come back to this tweet later? What's the point? Should I just retweet it? I don't like it that much that I want to RT it, and I don't want to spam my followers."

Maybe I over think things but, it was a bit confusing to me.

I'm sure Basecamp is going to be thrilled about this. It's ironic since google is the antithesis of all that is preached in Rework.

You could look at working remotely. You could still stay in tech but also live a healthy lifestyle.