Our values as a society in tech

I know it’s been a long time since I wrote anything even remotely technology related here. This is almost tangential.

About 10 days ago, quite a lot of the world was hit by a piece of malware which has come to be known as WannaCry. It was a piece of ransomware which took over your machine if you were so unlucky, encrypted your files and demanded money to hand them back. I call that amoral, but it appears to be a viable business option for some people as occasionally the ransoms get paid.

The impact of WannaCry was tempered by a piece of work done by a young malware researcher whose name I don’t know but you can find him on Twitter as MalwareTech here. He discovered by accident that if you registered a particular domain name and pointed it at something, the malware stopped replicating from one computer to another. WannaCry reached a lot of computers but it was stopped reaching a lot more by this. In the grand scheme of things this guy is a hero, should be able to name his price for security consultancy and after that, if he wants the glory and the stardom, well that’s his choice. If he does not, however, that’s another kettle of fish.

Today I learned that in general terms, he wasn’t up for celebrity status, but this did not stop the UK press going after him. He got doxxed – lovely word that – by a major UK newspaper and journalists from a couple of others went after his girlfriend and other friends. You can read the twitter thread here. He is apparently moving house because of this.

To be honest, I think trying to pay people to spill the beans on their friends is a fairly amoral thing to do. What sort of a human being do you have to be to do it? Sure, we all think UK media is a cesspit of despair, particularly certain of its newspapers, but still… wouldn’t it be nice if instead of going after people who never meant to be famous, who did something quite special as part of their day job, and who would like to go back to doing that day job in peace, they went after people who seek the limelight, and control? How much time have UK newspapers devoted to actually holding Jeremy Hunt to account before now? Where were they when he and his team decided to nix the NHS’s support contract for their XP machines? Is’t it just too easy to go after members of the public who aren’t actually limelight hunting? I don’t know this guy but I don’t think he’s being hypocritical by wanting to stay out of the limelight. He’s not preaching one thing and doing another. I’m not sure there’s a single journalist with the nous to be able to figure out if he is, like, doing all his work on an unpatched Windows Vista machine…

The problem is this: we need guys like MalwareTech. We need them a lot. Security defence is a thankless job, it is largely not sexy and it seems to only gain importance when something goes wrong. Before that, it’s release early and often and if it opens up a risk…well we’ll fix it in the next release. Great stuff and we’re all making money until we are not.

Seriously, how good is it if your fridge can be held hostage? We are massively and increasingly dependent on computerised systems, and connected devices (although I defy anyone to explain to me why a toaster might ever need to be connected to anything other than a power socket). The least we can do is ensure they  do not create risk vectors for our lives. To protect us from skullduggery of a digital nature, the world needs young tech people turning their mind to security and malware investigation in order to mitigate our risks here.

It would help if we didn’t also allow our media to exploit them and doxx them just for the sake of a few page turns and clicks. It is not bringing anything to the world and it is not in anyone’s interest to be invading the privacy of someone in whose life the sole interest is prurience.

Interpreters – male or female?

I was catching up with Troublesome Terps earlier today and was interested to have a listen to their views, and the views of their guest speaker on the question of the male female split in interpreting. You can have a listen to the piece here and they have provided some reading material which I have not yet had a chance to have a look at.

In summary though, the theme of their piece is that the gender split in interpreting is not even and there is a preponderance of women and they discussed why that may be. Amongst the items being discussed were rationales along the lines of career opportunity and whether men desired a clear promotional structure.

I found it interesting to listen to the discussion, and it covered a lot of interesting things relating to voice, and the different use of language depending on whether the speaker was male or female. If you are interested in interpreting, it is certainly worth a listen, and some of it is thought provoking.

One point which was only barely touched upon came from a passing comment of Jonathan Downie on the subject of the pipeline. I don’t think he called it that, but pipeline is the accepted term in technology for the incoming cohort of people training to come into the sector, and I think it’s a suitable term also for upcoming potential interpreters. The pipeline is core to discussions about the lack of women in the tech sector. In truth, the tech sector has a chronic lack of women, and its problem is largely two fold: comparatively few women study fields that would line them into technical roles in the technology sector, and of those who do, a lot of them drop out of the sector, or the technical roles, over time. The pipeline is often targeted as a useful and simple solution of the “if we only got more women studying comp sci, it would all be more diverse later”. For various reasons, this is probably not enough but I will come to that later.

Jonathan made the comment that in the interpreting pipeline, it wasn’t so much the lack of men which he noticed at masters level as the lack of British students in the field. As it happens, I’ve previously done some number crunching in the language pipeline for the UK excluding Scotland, and Ireland, going back to 2015. You’ll find a very quick overview of the findings here. The reason Scotland isn’t included is that at the time I ran those numbers (ages ago now), I did not have access to the corresponding figures for the Scottish Highers. The key line that I want to take away from this however is this:

on average, twice as many girls study languages at school leaving stage in both the Irish leaving certificate system and at A-level stage in England/Wales

If I recall correctly, the general finger in the area calculation for the split of interpreters between female and male was around 2:1 or 3:1. It can vary slightly depending on the language.

By the way, in absolute terms, more students study higher level French in Ireland than take A-Level French in England/Wales (I can’t remember if Northern Ireland was included in those figures). Additionally, the supply of language teaching at third level is drying up in the UK with a couple of very common languages (I did research on that too) scattered across the UK and, I think, 2 or 3 schools dealing with the wider range of less common languages.

However, that is all by way of an aside. In the UK and Ireland, at least there is a serious pipeline issue with language skills for boys. In general there are at least 2 girls for every one boy studying language at advanced secondary level. However, it is wrong to extrapolate from the experience in the UK and Ireland to any other country for a variety of reasons, the key one being that other countries make a better fist of teaching their young people foreign languages in general terms (cf Finland, the Netherlands and how to make me feel inadequate Luxembourg), so the lack of a cohort prepared for specialist language courses is potentially not such an issue there. However, it looks in practical terms as though men are not following them. The question is why. I am pretty sure that the answer to that question is not straightforward, but similar to the situation for women in computer science, for example, it has its roots far earlier in the school system. There is research around to suggest that girls are caused to be disinterested in maths and science related subjects based on how they are treated as early as primary school. Socialisation may have a lot to do with how people perceive their strengths for different subjects at an early age. This is a useful piece dealing with that, although it’s six years old and I’m pretty sure there’s been more in depth stuff, particularly in terms of mathematics, in the interim.

So this is one issue with the pipeline. The second issue with the pipeline relates to the perception of the job itself, and this is where I’m going to pop up with a certain amount of speculation. Because of how the system in Ireland works in terms of winning places at university, there is evidence to suggest that a key motivator for some students in terms of their choice of university studies is the likelihood of economic success. In Ireland, that tends to be law and veterinary sciences, with pharm a little way back, and then, things vary according to economic fashion. The bottom fell out of architecture and construction related courses, comparatively speaking, a few years ago, for example. Language related careers are rarely up there with their name in lights. No one mentioned interpreting to me at school (I hardly knew they existed) and we did family research before we even tracked down translation because the school was more interested in marketing courses which were trendy when I was a young one.

So, generalising wildly, there’s a pipeline issue because boys are funneled towards technical courses and in general terms, the career of interpreter is not necessarily high profile as a good earning opportunity.

I suppose the question which next arises is what happens to men once they are in the pipeline and in the industry. I cannot really answer this question as I don’t currently work as an interpreter. I took an interest in this piece because I trained as an interpreter but work primarily in the tech sector where matters are largely inverse, and where there is a great deal of discussion on the question of women in the pipeline, women in the industry, diversity in the industry. Yesterday or the day before, Susan Fowler, a site reliability engineer, published this on her blog. My personal experience has involved men telling me the only reason women go to college is to get married and anyway they don’t know how to work (imagine a 21 year old bachelor student saying this to a female masters student with more than 10 years experience working in the tech sector and you’ll get an idea of just how stupidly obnoxious some people can be).

Is the interpreting sector sexist? I don’t know if it is, or whether the split is a symptom of wider attitudes in society which have their roots at a far earlier stage of education. It seems to me, however, that there is not necessarily a similar level of pushing men out of interpreting as can be seem in certain parts of the tech sector. Would we better off with a better balance? I think yes we probably would but that’s because in general, society is better off with a better balance across most jobs. Do I think interpreting as a skill is adequately valued? The straight answer to that is right now, and depending on your culture, probably not. Clearly, the large international organisations could not function without interpreters. Nor could the US or British armies in Iraq and Afghanistan. However – anecdote alert – when I did CPD in Heriot-Watt in Edinburgh last year – one course participant noted that historically, in her country, at certain times, interpreters tended to be men because it was a distinguished role and could not be left to mere women. Strangely enough, software development and programming, in the early days, was left to women because it was not considered to be particularly difficult (hah) and the men did more praiseworthy and important work with hardware engineering. It seems culture and perception have an awful lot to answer for on both fronts.

WordPress tells me this is nearly 1,500 words, so for the tl;dr version: it strikes me as though the lack of men in interpreting is programmed into the system quite early, and subsequently, the lack of economic value linked with the role may serve to lessen the attraction for men who tend to target economically important jobs (or perceived better paying roles anyway), or who potentially tend to get paid more when the majority of their cohort are also male.

From that point of view – and it kills me to say it – one of the best things female workers in areas which are predominantly female staffed (so nursing, teaching, interpreting, translation) could do to improve their earning potential is to increase significantly the number of men in their sector.

And a corollary of this, by the way, strikes me as being a likely motivation for getting more women into computer science and related fields – namely reducing the cost of those roles.

Okay. I might revisit this later when I am awake.




Github alerts on Inbox

A day or so ago, the product team at Google Inbox made some updates in terms of how the application handles email coming from Github. I think they made similar changes to Trello too but I haven’t been using Trello much (tbh I had forgotten about it and it looks like I set up my account 4 years ago) so this probably applies to Trello if you have teams using Trello and as a result, receive lots of emails from Trello. I don’t.

I am watching a dozen or so Github open source projects, however, none of them huge, but a couple of them are relatively active and generating email on a regular basis.

One of the reasons I liked Inbox was that it effectively sorted my email into stuff that was worth annoying me about and stuff that wasn’t. This means that for all those Facebook, Twitter and other automated and mass email sendings, my phone didn’t bother me and I could review those at my leisure, like waiting for stuff to cook or whatever. Github was sorted into the Forums post and this suited me because anyone who needs to check who has updated a Github repo on their phone while they are out is not really the sort of person I tend to consort with.

As of yesterday though, this has stopped. Inbox now informs me every single time I get an email from Github. The sad part about that – for me probably – is that there are a good deal more Github notifications yesterday for one project than a) usual and b) I get from human beings on a day to day basis. As a result, Inbox has been annoying me with Github alerts, alerts which I can only get rid of by unwatching the projects in Github. Amongst the things I cannot tell Inbox to do at the moment is not to send lock screen/audible alerts to the phone for Github originating email.

The way they bundled Github in the Inbox itself is nice. But I cannot understand why it occurred to no one in Google land that enforcing an audible/buzz alert on the phones without a way to switch that off was a stupid, stupid idea which had the potential to wreck Inbox utility for some users. As for anyone whose subscribed to a lot of Github projects, their phones must be going crazy. Mine was annoying because it meant that a buzz alert no longer meant that I’d gotten actual email from a human for the most part, only that someone somewhere had updated a Git repo. Essentially, my phone started crying wolf over the email it was receiving. It used to alert me to personal/potentially important email. Now it alerts me to definitely not urgent for me email, email I want to receive, but do not want a lockscreen alert for.

I sometimes think that people working in the tech sector work inside a bubble and do not have access to a diverse enough pool of users for testing purposes. The first thing I would have said to someone if I’d been testing this is “You have to give users the options to switch off audible and lock screen alerts for these things. For many people, they may represent non-essential, non-urgent email and you’re stripping away useful meaning of those alerts”.

Up to yesterday I knew that if my phone buzzed an email alert, it was probably something I needed to look at now. As of yesterday, now if it buzzes, it’s probably a Github alert. This does not improve my life.

Google’s mic drop

I like to think that somewhere in Mountain View, a kindly manager of product managers is holding a meeting with the Gmail product team and shaking her head in disappointment over what I would personally consider to be a serious fiasco on 1 April.

Drop Mic was bad on so many levels, it is hard to decide where to start with the wrongness. The other issue is that it was so obviously wrong, it is hard to understand why anyone involved in letting it out into the wild didn’t realise it was a mess.

Typically, one of the core things which any company should be doing is protecting the integrity of their product. Do they have a product which has built up a lot of trust over years? And are various other parts of their business dependent on that product? The answer to both those questions was yes.

In a lot of respects, I suspect Google is heavily dependent on the continued will of people to actually sign into google accounts to maximise their advertising revenue. Gmail might be “free” at the point of use but it is not really free at all because the average google user, by signing into their gmail – and hence google – account is paying for it in cold hard data about their habits and interests. It is unlikely that the micdrop stunt will stop massive numbers of people using gmail…but they may trust it a little less. Google’s interests are served by people continuing to use Gmail. Someone, somewhere in GoogleLand should be saying “Do Not Mess With The Product For A Joke” over and over again.

It is not a case of people not having a sense of humour. It is a case of people expecting their tools to be reliable and not trying to kill them. Sure the micdrop button was orange but it shouldn’t have been there in the first place. It was located right next to the send button, in a location where a lot of users have a send and archive button. To say that it was put in the most stupid possible place is fair. It was guaranteed to cause problems. It got pulled quite quickly which suggests to me that in Google, at least one grown up works.

But possibly only one.

Google’s initial message to announce pullage was insulting “Oh it looks like we pranked ourselves” and an implication that if one or two bugs hadn’t existed it would have been fine. It was never fine. The subsequent follow up did not consider the fact that they should never have tried to actually implement it either. For this reason, even though Google has probably done some internal investigation and talking about this, they probably have not quite worked out that they should never have tried to implement it at all.

People in Gmail land need to recognise that one of the cornerstones on which their company’s wider business interests lie is trust in the gmail product and that when they mess with the integrity of that product, it can cost money.


Hysteria of Hype

Somewhere around the web, there’s a cycle of hype which generally pins down where we are in terms of a hype cycle. I have not the time to go looking for it now but put simply, it has bunch of stages. I have decided it is too complicated for the tech sector.

Basically, the point at which you start seeing comments around X is the next big thing is the point at which something else is the next big thing. Sounds contradictory? Well yeah, it is.

Most people talking about the next big thing being X tend not to know a whole lot about X. Their primary objective is to make money off X. They do not really care what X achieves, so long as it makes them money.

Five years ago up to oh I don’t know, middle of 2014, early 2015 sometime, Big Data Is The Next Big Thing. Being blunt about it, there has been very little obvious Life Changing going on courtesy of Big Data and that is because by the time people started screaming about big data in the media and talking about how it was the future, it had ceased to be the future in the grand scheme of things. Artificial intelligence and machine learning, now they are the next big thing.

I have to declare an interest in machine learning and artificial intelligence – I wrote my masters dissertation on the subject of unsupervised machine learning and deep learning. However, I am still going to say that machine learning and artificial intelligence are a) a long way short of what we need them to be to be the next big thing b) were the next big thing at the time everyone was saying that big data is the next big thing.

It is particularly galling because of Alpha Go and the hysteria that engendered. Grown men talking about how this was the N.

Right now, artificial intelligence is still highly task limited. Sure it is fantastic that a machine can beat a human being at Go. In another respect, it isn’t even remotely special. AlphaGo was designed to do one thing, it was fed with data to do one thing. Go, and chess to some extent, are the same thing as brute forcing a password. Meanwhile, the processes designed to win games of Go and chess are not generally also able to learn to be fantastic bridge players, for example. Every single bit of progress has to be eked out, at high costs. Take machine translation. Sure, Google Translate is there, and maybe it opens a few doors, but it is still worse than a human translator. Take computer vision. It takes massive deep learning networks to even approximate human performance for identifying cats.

I’m not writing this to trash machine learning, artificial intelligence and the technologies underpinning both. I’m saying that when we have a discussion around AI and ML being the next big thing, or Big Data being the next thing, we are having the equivalent of looking at a 5 year old playing Twinkle Twinkle Little Star and declaring he or she will be the next Yehudi Menuhin. It doesn’t work like that.

Hype is dangerous in the tech sector. It overpromises and then, screams blue murder when delivery does not happen. Artificial intelligence does not need this. It’s been there before with the AI winter and the serious cuts in research. Artificial intelligence doesn’t need to be picked on by the vultures looking for the next big thing because those vultures aren’t interested in artificial intelligence. They are only interested in the rentability of it. They will move on when artificial intelligence fails to deliver. They will find something else to hype out of all order. And in the meantime, things which need time to make progress – and artificial intelligence has made massive jumps in the last 5 or 6 years – will be hammered down for a while.

For the tl;dr version, once you start talking about something being the next big thing, it no longer is.

The invisible conduit of interpreting

Jonathan Downie made an interesting comment on his twitter this morning.

Interpreting will never be respected as a profession while its practitioners cling to the idea that they are invisible conduits.

Several things occurred to me about this and in no particular order, I’m going to dump them out here (and then write in a little more detail how I feel about respect/interpreting)

  1. Some time ago I read a piece on the language industry and how much money it generated. The more I read it, the more I realised that there was little to no money in providing language skills; the money concentrated itself in brokering those skills. In agencies who buy and sell services rather than people who actually carry out the tasks. This is not unusual. Ask the average pop musician how much money they make out of their activities and then check with their record company.
  2. As particular activities become more heavily populated with women, the salary potential for those activities drops.
  3. Computers and technology.

Even if you dealt with 1 and 2 – and I am not sure how you would, one of the biggest problems that people providing language services now have is the existence of free online translation services and, for the purposes of interpreters, coupled with the ongoing confusion between translation and interpreting, the existence Google Translate and MS’s Skype Translate will continue to undermine the profession.

However, the problem is much wider than that. There are elements of the technology sector who want lots of money for technology, but want the content that makes that technology salable for free. Wikipedia is generated by volunteers. Facebook runs automated translation and requests correction from users. Duolingo’s content is generated by volunteers and their product is not language learning, it is their language learning platform. In return, they expect translation to be carried out.

All of this devalues the human element in providing language skills. The technology sector is expecting it for free, and it is getting it for free, probably from people who should not be doing it either. This has an interesting impact on the ability of professionals to charge for work. This is not a new story. Automated mass production processes did it to the craft sector too. What generally happens is we reach a zone where “good enough” is a moveable feast, and it generally moves downwards. This is a cultural feature of the technology sector:

The technology sector has a concept called “minimum viable product”. This should tell you all you need to know about what the technology sector considers as success.

But – and there is always a but – the problem is not what machine translation can achieve – but what people think it achieves. I have school teacher friends who are worn out from telling their students that running their essays through Google Translate is not going to provide them with a viable essay. Why pay for humans to do work which costs a lot of money when we can a) get it for free or b) a lot less from via machine translation.

This is the atmosphere in which interpreters, and translators, and foreign language teachers, are trying to ply their profession. It is undervalued because a lower quality product which supplies “enough” for most people is freely and easily available. And most people are not qualified to assess quality in terms of content, so they assess on price. At this point, I want to mention Dunning-Kruger because it affects a lot of things. When MH370 went missing, people who work in aviation comms technology tried in vain to explain that just because you had a GPS on your phone, didn’t mean that MH370 should be locatable in a place which didn’t have any cell towers. Call it a little knowledge is a dangerous thing.

Most people are not aware of how limited their knowledge is. This is nothing new. English as She is Spoke is a classic example dating from the 19th century.

I know well who I have to make.

My general experience, however, is that people monumentally over estimate their foreign language skills and you don’t have to be trying to flog an English language phrasebook in Portugal in the late 19th century to find them…

All that aside, though, interpreting services, and those of most professions, have a serious, serious image problem. They are an innate upfront cost. Somewhere on the web, there is advice for people in the technology sector which points out, absolutely correctly, that information technology is generally seen as a cost, and that if you are working in an area perceived to be a cost to the business, your career prospects are less obvious than those who work in an area perceived to be a revenue generating section of the business. This might explain why marketing is paid more than support, for example.

Interpreting and translation are generally perceived as a cost. It’s hard to respect people whose services you resent paying for and this, for example, probably explains the grief with court interpreting services in the UK, why teachers and health sector salaries are being stamped on while MPs are getting attractive salary improvements. I could go on but those are useful public examples.

For years, interpreting has leaned on an image of discretion, a silent service which is most successful if it is invisible. I suspect that for years, that worked because of the nature of people who typically used interpreting services. The world changes, however. I am not sure what the answer is although as an industry, interpreting needs to focus on the value add it brings and why the upfront cost of interpreting is less than the overall cost of pretending the service is not necessary.

Glitches in the matrix and Viber

I ran into an interesting problem with the messaging service Viber yesterday – I had a brand new computer which developed a fault rather quickly and which, prior to my returning it to the vendor, could not be made to operate in such a way as I could get at the data I had stored on it.

In theory, there was not much such data – I had not finished installing software on the machine, and nor had I started uploading backups from the previous machine to it. However, I had installed Viber and I had opened one conversation with a friend online. Six hours after I bought the machine, the operating system would not load and so it went back to the vendor.

I cannot fault the vendor in this case between their phone customer support and the behaviour of the staff at the branch where I did buy the machine. I was concerned though that the fault might be fixed at some point in their workshop and whether there was any risk that Viber would attempt to sync any subsequent discussions as I had been unable to de-install it before I handed the machine back. What was on the machine itself was low risk. I just wanted to ensure that Viber would not be able to subsequently sync with any subsequent conversations.

When you go looking for information on this front, the general assumption is that people have lost access to Viber on their phones and not necessarily to their desktops.

In theory, the two obvious solutions for the operating system loading error would have been replacement hard drive or reinstalling the operating system. I obviously could not do the the first, and the latter had been kiboshed by the fact that I had not even got as far as making a recovery disk. When I looked into it in detail, there is a theoretical fix involving rebuilding the BCD in the kernel. I found a single document which was detailed on the process but it did not, for example, outline what happened to any other data on the machine. As such, it did not leave me much peace of mind.

Viber is a handy messaging platform which you can use from both phone and desktop. Its user documentation is of mixed quality and, again assumes the reason you might want to nuke your Viber service is that you no longer have access to your phone. If you’re looking to deal with a desktop which has your account on it, it is actually possible.

When you set up Viber on your phone, you’re effectively setting up an instance of an account and any desktop installations of Viber are tied to that. You can, from the desktop installation, deactivate that particular desktop installation via settings. If you do not have access to the desktop installation, you MUST deactivate Viber on your phone and this will deactivate all Viber installations linked with that instance of an account, ie, Viber on your phone, viber on any desktops or tablets associated with Viber linked to your phone number.

You cannot pick them off remotely and individually. It’s all or nothing.

What happens then is that if someone tries to access Viber on any of the desktop installations linked with the account is a dialogue over whatever was most previously opened in Viber at the time of the previous synch, a dialogue box opens to tell you that the account is no longer active. They will have to respond to that dialogue box and in my experience, that kills the Viber data behind. There is a window of risk that someone might see something in your messaging software that you would not want, but at least there is an option for destroying the connection between your phone number and that desktop instance remotely, even if it’s the equivalent of a nuclear option.

The downside is that you lose all your messaging data unless you back the messages up before which you must do on your phone.

In short, assuming you’ve lost a non-phone device with Viber data on it, here’s how you kill things:

  1. Back up your viber messages on your phone if you want to keep them. If you don’t, you don’t have to do this.
  2. Go to the privacy setting and select Deactivate. You’ll probably have to scroll to the bottom to find it. This will kill your viber service on your phone and any associated non-phone installations (desktops for the most part).
  3. Set up viber on your phone again. I did not actually have to de-install, reinstall Viber on the phone to do this – it sent me a new 6 digit code and I was up and running.
  4. Set up viber on your desktop again by obtaining a new code. I did not have to reinstall Viber to do this.

I had to deactivate the machine remotely for some subscription software – MS Office and Adobe Creative Suite – and I could do this. I think it would be useful if, somehow, it was possible to review how many machines were receiving push notifications from Viber so that you could deactivate them at will rather than having to nuke everything and start from scratch.

Code Reviews

This piece on code reviews landed in my email via an O’Reilly newsletter this morning.

I’ve posted a brief response to it but I wanted to discuss it a little further here. One of the core issues with some code reviews is that they focus on optics rather than depth. How does this code look?

There are some valid reasons for having cosmetic requirements in place. Variable names should be meaningful, but in this day and age, that doesn’t mean they also have to be limited to an arbitrary number of characters. If someone wants to be a twerp about it, they will find a way of being a twerp about it no matter what rules you put in place.

However, the core reason for code reviews should be in terms of understanding what a particular bit of code is doing and whether it does it in the safest way possible. If you’re hung up on the number of tab spaces, then perhaps, you’re going to miss aspects of this. If you wind up with code that looks wonderful on the outside but is a 20 carat mess on the inside, well…your code review isn’t understanding what code is doing and it’s not identifying whether it is safe or possible.

So what I would tend to recommend, where bureaucratically possible, is that before any code reviewing is done, coding standards are reviewed in terms of whether they are fit for purpose. Often, they are not.

It won’t matter how you review code if the framework for catching issues just isn’t there.


One of those simmering arguments in the background has been blowing up spectacularly lately. The advertising industry, and to a lesser extent, the media industry, is up in arms about ad-blocking software. They do not like it and to some extent, you can probably understand this. It does not, exactly, support their industry.

There are two approaches which I think need to be considered. The advertising industry and the media industry, instead of bleating about how stuff has to be paid for, need to consider how they have contributed to this mess. On mobile, in particular, advertising is utterly destroying the user experience. When I wind up with content that I want to read because I can’t access because there is a roll over ad blocking it, for which I cannot find a close button, then the net impact is not that I feel a warm fuzzy feeling about the advertiser and the media site in question. The net impact is that I spend less and less time on the media site in question.

So, instead of screaming about how stuff has to paid for with advertising, maybe the media companies need to recognise how advertising is wrecking their user experience and how, ultimately, that is going to cut their user numbers. The fewer eyes they have, the less their advertising is going to be worth. I have sympathy for their need to pay their bills but at some point, they need some nuance in understanding how the product they are using to pay their bills now will likely result in them being unable to pay their bills at some point in the future.

As for the advertising industry, I have less sympathy. They appear to think they have a god given right to serve me content which I never asked for, don’t really want and which might cost me money to get particularly on mobile data. Often, the ads don’t load properly and block the background media page from loading. They have made their product so completely awful as a user experience that people are working harder than ever before to avoid it. Instead of screaming about how adblockers are killing their business, it would be more in their line to recognise that they have killed their business by making it a user experience which is so awful, their audience are making every effort to avoid it.

The ability to advertise is a privilege, not a right. It would help if advertisers worked towards maximising user engagement on a voluntary basis because by forcing content in the way which is increasingly the normal – full screen blocking ads – on users they are damaging the brands and the underlying media channels. Maybe advertisers don’t care. Maybe they assume that even if every newspaper in the world closes down, they will still find some sort of a channel to push ads on.

Adblocking software should be reminding them that actually, they probably won’t.