insertion

I've wondered why partisanship doesn't exist to nearly the same extent in business and consumer behavior. This explains a lot.

Two reasons:

1. You'll come across it and apply for a job at Google.

2. You'll have a positive interaction with the Google brand.

A big part of this: it's something people want to share. Without that element, it would only ever be seen by a few dozen people.

I would like to see a language use decimal by default. Under the hood, it could use floating point for certain types of calculations where less precision is required. If I want to know the answer to 0.2 + 0.1, chances are I want the answer to be 0.3. If I'm writing performance-sensitive code, maybe I can drop down a level and opt for float(0.2) + float(0.1). Are any languages doing this currently?

I find it highly unlikely this was a coordinated PR stunt. If revealed, this would damage the reputation of both parties, particularly Taylor. On a risk-adjusted basis, it’s not worth it for such established players to do this sort of thing. There’s also the secondary issue of how Apple would initially raise this topic. What are the chances she would have wanted to play along? Maybe she has a close friend at Apple who’d feel safe suggesting this, but it seems unlikely.

It’s very hard to exactly predict how stories will develop. What if lots of other artists came out and publicly supported Taylor’s stance? Then, even if Taylor agreed to Apple’s next deal, the other artists might not. In which case, Apple finds itself in a pickle and nobody would be suggesting that this was coordinated – even if it was.

The article ends like this: "As Cowen puts it, 'what are humans still good for?'"

For the most part, programmers program better than programs. It's amazing to think about the possibilities as this statement becomes less true.

This doesn't seem right to me:

> 3) How do you determine which devices and OS versions we should test on?

> This should generally be an easy question for the candidate. Good candidates will point to app analytics as the best measure, looking for the most used devices for their particular app. Another good answer would be to check the app reviews where people might have complained about specific issues happening on their devices. Less creative candidates might simply suggest “looking at the top devices” on the market

Looking at top devices is also incredibly important, and it seems foolish to dismiss that strategy.

What if your website doesn't work on iPhones, and so you have no iPhone users? What if, because people can't even sign up on an iPhone, they don't bother complaining about specific features not working?

Surely it makes more sense to test based on your target market, rather than the subset of people who are self-selecting to use your product?

Ideally you should be looking at both usage and market data. If your target market contains lots of iPhone users, but everyone's on Android, this points to a potential problem.

This is possibly the most source-friendly piece of tech journalism I've read in a while. I don't think there is a single point in that piece that would make Yahoo PR the least bit uncomfortable. Credit where it's due, the article is incredibly well written and beautifully presented. It's just a shame to see such unquestioning faith in a source. One by one, Levy hammers away at every recent criticism of Yahoo. Anything that could not justified was deemed to be overblown.

"Some of the various flaps involving her leadership were crazily overblown, like her personal child care accommodations, or an edict against working at home that affected a tiny percentage of Yahoo’s workforce."

Every original fact in this article is information Yahoo would obviously want to share, like the success of its revamped ad platform. Based on the way he has failed to question anything else that Mayer has done during her tenure, it is hard to believe that these facts were questioned and examined in any detail.

Don't get me wrong: I think that Mayer may be doing a good job. I'm not too sure either way. I just think, as a piece of tech reporting, this is embarrassing.

Looking at the release as a whole, I'd be fascinated to hear what features have taken the most time and effort? What turned out to be much harder than expected?

This looks pretty elegant, but it's a shame that Elixir uses the Ruby-style multi-line code blocks with do end. Looking at those code examples, 'end' take up around 25% of the lines with code. Does anyone know if they considered taking the Python approach? Would be curious to hear the arguments behind the decision. I've noticed that most people seem to favor the Python approach after trying it, but that it's rarely used in new languages.

As someone who is more familiar with OOP, I would love to see examples/hear more alternative approaches to organising code.

Let's say that you want to design a CRUD app, but you're not going to use OOP. What are some of the ways you could choose to structure your code? Would you still use a pattern like MVC?

Why a countdown? Probably because they're launching a watch. Wait and see. My guess is they hint at the why during the event, probably in the opening minute or so. They will also probably use time-based headlines in the slides.

That doesn't make sense. Not unless the introduction of the tablet caused people to buy PCs and laptops. There might be some dynamics between the two, but it doesn't relate to the age of the tablet being equal to the average lifetime of a PC.