sekasi

A lot of talk around Beacons and the promise of 'Low Energy', without that much factual data around the amount of power they source from your smartphone battery mostly.

Hi.

I hire for a global tech organization, and I'd just like to give you a little bit of insight:

1. Don't use middleware unless you have to. Your salary will be lower, and you won't get to work on 'as' amazing things. This includes Xamarin, PhoneGap, Trigger and all the things in between

2. Pick one first. iOS or Android. Don't dual-learn. It'll take you longer. Get a decent foundation on one first, and pick the one that makes more sense to you from a language point of view. (hint: Objective-C is weirder than it looks, Java is insanity)

3. I've hired people who had less than 1 year experience with mobile development who have subsequently turned into extremely senior developers. It's totally possible buddy.

4. Reading is (mostly) useless to form a foundation. Pick a project, work on it, scrap it, begin again with newfound knowledge and keep doing that until you feel comfortable with the concept of creating mobile apps.

Hope that helps ;)

mā ma qí mǎ, mǎ màn, mā ma mà mǎ

That's a legitimate sentence, and there's only the slightest intonation difference between the different words.

This to me is why Mandarin is hard. Not the writing, not the history of the language and not the 'construction of words'.

It's the extremely subtle differences in tonality which makes it madness for a westerner (Swedish born here) to try and comprehend, and even worse to try and speak.

Terrifying. But like you said, basically kids during the war forced to do a lot of things most modern day guys could never even imagine.

well that's a lie.

For anyone curious in the field, there's a version of Michael Abrash's black book publicly available at github;

https://github.com/jagregory/abrash-black-book

A little bit too similar to 'threes' on the app store.. I like it, but again, it's too much of a ripoff.

Except that Storyboards are pretty detrimental to large project maintenance, especially universal apps. AND they have a really awful habit (or most developers do!) to keep copy IN the storyboards.. which is an unimaginably bad practice.

Storyboards are good for small, simple apps where you're the sole developer (or maybe a team of 1-3). Go bigger, drop storyboards.

Another stab at using 'Trusted proxies' huh? I thought we had learnt that lesson a while ago.. Can we move on please, internet?

Honestly, I can't believe some of the responses here. 'Fix it yourself'. 'Fixing bugs is more important' and a number of other black and white missing-the-point dravel.

Let me help. Here are a few pieces of irrefutable truths:

- Any developer who doesn't see, or care, about attention to visual details is a bad member of the team.

- priorities. Of course big bugs are more important. Why would you even mention that.

- Good designers have their set of priorities. A good developer understands that, and doesn't say mind numbing things like 'don't waste my time'.

- Will all visual enhancements increase conversion rates? No. Does that mean you're free to be sloppy? No.

- At the end of the day, the balance between perfect code and perfect visual design is up to the product owner. Discussion about what's more important is pointless. It all matters.

Can you be any less likable if you tried? It's been advertised, you just haven't seen it.

That's not entirely their fault, advertising is not free. You don't have to be all snobby about it. Sheesh.

Core bitcoin team member.

moar credibility than <randomguy15> on any irc/dark/use-net I can think of.

Huh what? what do people in chatrooms and reddit have to do with anything? If that's your choice of credible information then life must be very dark.

If you follow the article you'll find that some of the core bitcoin team is confirming the flaw.

But maybe reddit is right. Clearly.

Apple will fight all day and all night to maintain control of money on their app store. The way they push their weight around against anything that tries to do anything outside their walled garden is nothing short of disgusting.

This. So much this. The article is not trying to drum dramatics or hype or anything that western media is brainwashed to do with everything. It's just simple, honest and very brutal.

Extremely interesting (and open) write-up reginaldo. Congratulations on the payout.

If that difference in price versus getting it early to tinker bothers you, then you're probably not that interested in the product to begin with ;)

OP: Great writeup, thanks for that. I was wondering.. if price wasn't a part of the equation (I know it is, but humor me), would you still have migrated?

I look at the offerings in general and despite the fact that I've used neither, but am going to, it does look like Linode offers slightly 'more', albeit for a substantially higher cost?

This is absolutely and wholeheartedly true.

I hire technical staff for a fairly large agency, and I can tell you right away that the climate is getting a lot more difficult.

This article touches on the same progression from another angle; http://www.daedtech.com/how-developers-stop-learning-rise-of...

We now have a completely saturated market with people that started with HTML and CSS, with very little knowledge of actual programming. With the emergence of Atwood's law, and everything javascript.. these 'jQuery experts' have little to no relevance in the long term.

Unless FEDs actually understand programming, and unless they actually apply that knowledge in their work, they are being rapidly commoditized.

This is a real issue for the career future of many FEDs, but very few seem to realize it.

The tables are a bit busted on the smallest breakpoint, but other than that it's pretty awesome for the size. Well played sir.

Very nice. As mentioned below, it shouts for a UX/ExD review, but I'm impressed nonetheless.