Skip to main content

Leaving Linguamatics


The big news in my world at the moment is that I'm leaving Linguamatics. It's a massive decision for me because I'm one of the founders and I've ploughed untold time and effort, blood, sweat, and (yes) tears into it over the years. 

I realise that I'm very fortunate to even be able to contemplate leaving the company given the global situation. However, despite all that's going on and the uncertain future, now still feels like a good time to part ways, for me and for the company. 

I'm immensely proud of what we've achieved at Linguamatics and what the company is set up to achieve next. My Test team have been challenging and inspiring in equal measure (if you don't like everything you say being questioned, don't  build a team of excellent testers) and I am confident they can continue to do good work without me. I also manage a small team of technical authors and I've been delighted to see what people who agree what a good job looks like and care to do it efficiently can achieve.

I was going to write a blog post about this, but I realised that I'd said it all in my email to the company already, so below there's a lightly-edited version of that.

--00--

Hi everyone,

I wanted to let you all know that I'll be leaving Linguamatics at the end of the year.  As you can imagine, that'll be a moment of very mixed emotions for me.

Linguamatics was started around 20 years ago after me and the other founders were made redundant from our previous employer. I think our first meeting as a company was around a dinner table and we sat back-to-back in a tiny office in St John's Innovation Centre for years as we created I2E from the ground up, learning how to build software, how to be a business, and how to work together.

Along the way were moments of great tension (like the time I accidentally unplugged the indexing servers) and great innovation (like the time I took the case off the web server and gaffa-taped a desk fan to it for cooling) and great satisfaction (like getting our first patent for the technology we invented).

We've taken on many wonderful people over the years - and that includes you all. I'm thrilled to have been involved in a significant amount of that recruitment and proud when I see how colleagues that I helped to hire have contributed and grown and become key to the company's success. With your help we've turned one product into a suite of products which are dedicated to the same vision we had originally: using natural language processing to extract information from unstructured text powerfully, efficiently, and with the ability to tune precision and recall to suit any need.

Where we've ended up is amazing. We have made Linguamatics into an incredible international business with a top-notch reputation doing work that helps make the world a better place. That's not to be sniffed at. When the opportunity to become part of IQVIA appeared there was a tough choice to make but I believed then, and continue to believe, that the two companies are a strong strategic fit and complement each other well.

On a personal level I've learned a tremendous amount from working at Linguamatics. I've done pretty much everything in the company at some point, including accidentally becoming the health and safety officer because I happened to pick up the phone when the local Council called asking for one. I'm always delighted when a colleague does something that I didn't know how to do, or shows me where my knowledge is lacking, because that's an opportunity to improve my skills and add to my toolbox. There have been lots of those occasions in the last two decades :)

Which brings me to today. It's been a long journey for me and, frankly, I'm now very tired. I want to take a break and then I want to look for a new challenge with new opportunities to learn. I'm extremely conscious that my entire working career has been at Linguamatics and I wonder how much of what I know is specific to here, and what could apply in other contexts, and what I could find out about how to test from other people in those other contexts. There's also a bunch of courses I have wanted to do for years but not found the time for, and I want to put some energy into my role as Vice President of the Association for Software Testing.

As I said, it's a time of mixed emotions, but after Linguamatics was basically my life for so long I think I can now move on without the company and I'm confident that the company can move on just fine without me too.

Thank you very much for being great colleagues and making Linguamatics a great place to work.

James

Image:https://flic.kr/p/57p1gv

Labels:

Comments

  1. Andrew BurrowsOctober 13, 2020 at 7:44 PM

    Exciting stuff! I really enjoyed our brief time as colleagues and feel like I learned a lot from you in that short time. All the best for this next chapter and I hope you'll keep up the blog as it is really good.

    ReplyDelete

Post a Comment

Popular posts from this blog

Can Code, Can't Code, Is Useful

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "If testers can’t code, they’re of no use to us" My first reaction is to wonder what you expect from your testers. I am immediately interested in your working context and the way
Post a Comment
Read more

Meet Me Halfway?

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "Stop answering my questions with questions." Sure, I can do that. In return, please stop asking me questions so open to interpretation that any answer would be almost meaningless and certa
Post a Comment
Read more

Not Strictly for the Birds

  One of my chores takes me outside early in the morning and, if I time it right, I get to hear a charming chorus of birdsong from the trees in the gardens down our road, a relaxing layered soundscape of tuneful calls, chatter, and chirrupping. Interestingly, although I can tell from the number and variety of trills that there must be a large number of birds around, they are tricky to spot. I have found that by staring loosely at something, such as the silhouette of a tree's crown against the slowly brightening sky, I see more birds out of the corner of my eye than if I scan to look for them. The reason seems to be that my peripheral vision picks up movement against the wider background that direct inspection can miss. An optometrist I am not, but I do find myself staring at data a great deal, seeking relationships, patterns, or gaps. I idly wondered whether, if I filled my visual field with data, I might be able to exploit my peripheral vision in that quest. I have a wide monito
1 comment
Read more

Postman Curlections

My team has been building a new service over the last few months. Until recently all the data it needs has been ingested at startup and our focus has been on the logic that processes the data, architecture, and infrastructure. This week we introduced a couple of new endpoints that enable the creation (through an HTTP POST) and update (PUT) of the fundamental data type (we call it a definition ) that the service operates on. I picked up the task of smoke testing the first implementations. I started out by asking the system under test to show me what it can do by using Postman to submit requests and inspecting the results. It was the kinds of things you'd imagine, including: submit some definitions (of various structure, size, intent, name, identifiers, etc) resubmit the same definitions (identical, sharing keys, with variations, etc) retrieve the submitted definitions (using whatever endpoints exist to show some view of them) compare definitions I submitted fro
Post a Comment
Read more

Testers are Gate-Crashers

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "Testers are the gatekeepers of quality" Instinctively I don't like the sound of that, but I wonder what you mean by it. Perhaps one or more of these? Testers set the quality sta
3 comments
Read more

Vanilla Flavour Testing

I have been pairing with a new developer colleague recently. In our last session he asked me "is this normal testing?" saying that he'd never seen anything like it anywhere else that he'd worked. We finished the task we were on and then chatted about his question for a few minutes. This is a short summary of what I said. I would describe myself as context-driven . I don't take the same approach to testing every time, except in a meta way. I try to understand the important questions, who they are important to, and what the constraints on the work are. With that knowledge I look for productive, pragmatic, ways to explore whatever we're looking at to uncover valuable information or find a way to move on. I write test notes as I work in a format that I have found to be useful to me, colleagues, and stakeholders. For me, the notes should clearly state the mission and give a tl;dr summary of the findings and I like them to be public while I'm working not just w
Post a Comment
Read more

Build Quality

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "When the build is green, the product is of sufficient quality to release" An interesting take, and one I wouldn't agree with in general. That surprises you? Well, ho
1 comment
Read more

Make, Fix, and Test

A few weeks ago, in A Good Tester is All Over the Place , Joep Schuurkes described a model of testing work based on three axes: do testing yourself or support testing by others be embedded in a team or be part of a separate team do your job or improve the system It resonated with me and the other testers I shared it with at work, and it resurfaced in my mind while I was reflecting on some of the tasks I've picked up recently and what they have involved, at least in the way I've chosen to address them. Here's three examples: Documentation Generation We have an internal tool that generates documentation in Confluence by extracting and combining images and text from a handful of sources. Although useful, it ran very slowly or not at all so one of the developers performed major surgery on it. Up to that point, I had never taken much interest in the tool and I could have safely ignored this piece of work too because it would have been tested by
Post a Comment
Read more

The Best Laid Test Plans

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "What's the best format for a test plan?" I'll side-step the conversation about what a test plan is and just say that the format you should use is one that works for you, your coll
Post a Comment
Read more

Test Now

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "When is the best time to test?" Twenty posts in , I hope you're not expecting an answer without nuance? You are? Well, I'll do my best. For me, the best time to test is when there
Post a Comment
Read more