pablobm
As power users, we tend to ignore the power of default settings. Their values have to be chosen carefully because only a small part of the public are even aware of them.
Several commenters here seem to imply that they shouldn't be the ones personalising their browsers. Turns out it's the other way around: they are the ones who know how to personalise it, whereas defaults should be about users who don't know how to do it.
> Separate address and search bars is old-fashioned.
> As a user, I don't want to have to make this
> distinction, and it's hard to imagine most
> users-on-street wouldn't find this confusing
Although a UI problem, this is actually a privacy feature.As you type into the search bar, autocomplete queries are sent to the search provider. This happens even if your intention was not to search, but just to enter URL manually.
In simpler terms: you are telling Google what sites you are visiting even when you don't use Google.
(AndrewDucker mentions this on this thread too, but his comment emphasises the UI aspect, whereas I think the privacy aspect needs to be stressed).
Also, the fact that a t-shirt can be made out of this supports Patrick McKenzie's article [1] yesterday, commenting on how this bug (or rather, its announcement) has been a case of successful marketing.
[1] http://www.kalzumeus.com/2014/04/09/what-heartbleed-can-teac...
As gyardley says, there's the option to enable images. I rarely enable them, but sometimes I decide that I gain more from seeing them than from avoiding the tracking.
Another mechanism is links: clicking on one will get you tracked too. Normally, if there's something that catches my eye I look it up on Google instead of clicking on the link. But sometimes I either don't care or don't see a benefit to do it.
Now, the above is my behaviour, which is that of a paranoid, tech-savvy, power user who, for example, wasn't surprised in the slightest when the whole Edward Snowden story came about. Think of how a normal user will behave instead.
On that sentence though, I think it's different. The first part of the sentence is long enough that the comma is welcome as a natural stop (and breather) before delivering the second half.
By the way: I'm not a native speaker either.
[1] Also better known as "Oxford comma": https://en.wikipedia.org/wiki/Serial_comma
The first time, it broke. I called on a Tuesday at 6pm, they acknowledged the problem, and the day after I had a new one at 10am. I can't remember exactly how I returned the broken one, but I think I did it myself on the following days, to their freepost address.
The second time, I lost it. A couple of days later, they contacted me saying somebody had found it and called them. They shipped it back to me for free.
If I'm not mistaken, it makes the site safe from Man In The Middle attacks.
Several times in the past I have looked up information on them, and all I find seems to be in the realm of urban legend -slash- marketing ploy.
What is the physical principle behind this tech? Does anyone have reliable information?
The FizzBuzz test might be very easy, but you are assuming that these challenges will be for people of your own skill level. Probably the site will want to cater for a wider audience, from beginner to advanced, and FizzBuzz provides a good starting point for both.
And anyway, we have all read enough about FizzBuzz to know that even "experienced" "professionals" can fail spectacularly at it.
It looks like there's a lack of experienced developers in London, or at least in some technologies. Therefore companies needs must resort to finding "generic" good programmers who can be trained.
Of course I don't have any statistically significant data, only anecdotal experience. However it does resonate with the difficulty that we have had finding Ruby devs at New Bamboo in the last few months.
Does this sound familiar to anyone? I wonder if there's the same lack of supply of PHP devs.
However, normally have a problem: when he comes to me with links to these services, I have great difficulty to see exactly what they do, because all I can find is marketing jargon. Technical documentation is often buried deep within the guts of the site, and I have a hard time seeing if the service is actually worth integrating.
The way I recall it, it said something along the lines of "OK, Flash is not very good, but now we are working to address the issues mentioned on this article". I checked in archive.org, but there are no copies of the page there.