mopoke

As, indeed, they should. If you don't track something, how do you know if it's effective? Measure everything you can.

That reminds me very strongly of this: http://www.youtube.com/watch?v=pdOomYvnyNI&t=1m13s

If you were a heavy user, it's likely the costs were pretty clear early on, even if they weren't public. We got costings sent to us in the middle of 2011. However we chose to reduce our map impressions as the prices quoted were nowhere near what we could afford.

We use Yammer at our 300-person company and we've found it really valuable. We're roughly evenly distributed in 4 countries, so having somewhere which is asynchronous where people can see what's happening around the group provides a sense of connection between our staff. Anecdotaly, I've found it particularly valuable amongst IT people who feel more comfortable sharing ideas and opinions on there than they might do in person.

This would appear to violate the Google Maps API Terms of Service: http://code.google.com/apis/maps/terms.html

(b) Restrictions. In using Google Brand Features, you will not: [...] (ii) display a Google Brand Feature in your Maps API Implementation or on your site if your Maps API Implementation or site contains or displays adult content or promotes illegal activities, gambling, or the sale of tobacco or alcohol to persons under 21 years of age;

(f) No Violation of Google Policies. You must not violate any policies in the Maps APIs Documentation or violate Google's Software Principles (available at http://www.google.com/intl/en/corporate/software_principles.... or such successor URLs that Google may designate from time to time) and other policies as Google may develop from time to time, including but not limited to the Google policies below, under which you agree not to: [...] (xv) promote or provide instructional information about illegal activities;

Classifieds : cars, jobs, houses...

I get worried by blanket statements such as "leaving KeepAlive on will probably not be in your best interests." Using Keep-Alive is generally a good thing in terms of web performance. Not having to establish a new HTTP connection for each new asset request is gold.

The problem is not with Keep-Alive per se, it's more about Apache's process model (assuming you're using mod_php) - the fact that you have a large (10-100 MB) process sitting there doing nothing. My advice would be to either use Apache with mod_fcgid (and php-fpm) or jump to nginx + php-fpm.

We host a number of WordPress sites using Nginx and the stability has improved massively.

From my brief reading of Werner's blog post, it seems that this is very similar to what Nasuni have been selling.

Why single out India? Sure, it's become a bit of a byword for "outsource" but I think you'd find the same were you to outsource to any country - even within your own country.

The problems pointed out largely surrounding happen due to the difficulty of communicating with a remote team. Having the product owner and the development team geographically distant make everything ten times harder; doesn't matter if they're in India or on the other side of the same country.

I agree. There's no way I'm giving over my credit card details and being pre-billed when I have no idea if there is even anyone registered to be poached.

Take a lead from dating sites - tease and squeeze.

I like this solution and am definitely tempted to give it a go.

Anyone got any thoughts on the best way to do this on a page with personalisation? (and this is really simple personalisation - one section of the page changes depending on whether you're logged in or not).

My solution would probably be to have the personalised section load as an async request but then you'd need to make sure that the async request can handle the same load as the microcached content.

Any other ideas?

Apart from a sentence at the end, there's no mention at all of culture and people which is really the key to doing DevOps. You can use all of the tools mentioned but still encounter the same problems as a traditional ops setup if you don't get the teams working together.

Maybe I'm being a hypersensitive brit, but "Fuzzy Wuzzy" is as a pretty offensive term in the UK.

See top entry: http://www.urbandictionary.com/define.php?term=fuzzy+wuzzy

Not to take anything away from the tech - that looks awesome and I can already think of a few uses for it.

Author's comment on his site:

"It's not wrong to use client-side methods to do initial validation, but it's wrong to trust that validation on the server side."

The title should probably read "Why relying only on client-side verification is bad". I don't think the author is suggesting that doing client-side verification is a bad thing in itself.

Can we all stop talking about "the cloud" please? It makes responding to this kind of article far more difficult. After all, you can't really compare something like Dropbox with EC2 - they do completely different things and there is really very little in common. If you're talking about remote file storage, call it that. Don't get Hung up on this mythical "cloud".

I think amazon have set a pretty competitive benchmark with Route 53. ($1 per zone per month plus $0.50 per million queries)

Bulk change of records (change all instances of IP address x.x.x.x to y.y.y.y)

Import/export zone files (useful for migrating to/from the service)

Low cost :-)

Location is probably it - there is a much smaller pool to draw from where we are (Malaysia). It may get better responses in the US, Europe, etc. It was as much an experiment as it was a job ad - we also use other channels to recruit. But given linkedin is a global site, I was disappointed with the results.

Testing. Put the hard yards in early and it'll look after you later. Build up the quality by starting slower.

See also "built to last" by Jim Collins which covers the same ground from a different angle.

Depends on the definition of "some time" compared to the 2 weeks (solid?) it would take the automate. And how long you expect to continue doing said tasks.

That said, I would always err on the side of automating - at least some of the tasks. Take the low hanging fruit and tackle those first.

For example, I send out a weekly report containing a bunch of metrics sourced from our website monitoring tool. It took me a couple of days to automate that, but it saves me a good hour every week (and means I don't make mistakes copying and pasting figures which I used to with alarming regularity). It also means that my Monday mornings can start immediately without pounding through a repetitive task.

Balsamiq - Not free but, IMHO, it's the best out there.

http://balsamiq.com/

Because many people prefer reading on an eBook reader over a tablet:

- Cheaper ($149 or $249 compared to $499)

- Easier to read (eInk is a lot easier on the eye when reading for long periods than a backlit display)

- Not confusing (Granted, an iPad is pretty easy to figure out, but for an average consumer a device that does one thing is generally easier to grasp)

- Better battery life (Nook claims 10 days, iPad claims 10 hours)

The two technologies may converge in the future, but for now, the dedicated eBook Reader still has its place.

My comment was a little tongue-in-cheek. I do still follow slashdot's RSS feed, but I tend to only notice stories because I remember having seen them elsewhere a few days before. I don't remember Slashdot ever really having much in the way of enlightening discussion.

Slashdot?

> Perhaps the main reason most of us are not using HTTPS to serve our websites is simply that it doesn't work with virtual hosts.

That's a bit confusing. They mean when multiple sites share the same public IP. You can run SSL on a "virtual host" (i.e. a host running as a VM rather than on bare metal).

Also not mentioned is the general increase in server load by having to encrypt/decrypt all traffic. (or the additional cost of investing in a dedicated layer to do that for you).

For me, the most useful case is when hiring. I usually look up a candidate on linkedin. I can see if their work history for public consumption is similar to the one which is on their resume (tailored for the position). I can also see if anyone I know has worked with them before and then get an off the record assessment of their previous work and a feel for them as a person. Neither of those directly contributes to a hire/no-hire decision but it does help with getting to know what the candidate is like. As a side note, I tried posting a job recently and was hugely underwhelmed with both the quality and quantity of applicants.

My kid's an Android geek ;-) Seriously though, he does know his way around a touch interface scarily well (he's 4) and he is fascinated with trying all the different options available on the laptop (my work VPN username mysteriously transformed into his name after I left it alone a while back).

The article refers to children under the age of 5. Not toddlers. Pre-school is probably a more accurate description.