Plagarism, idea theft, and writing online. @ Irrational Exuberance

Hi folks,

This is the weekly digest for my blog, Irrational Exuberance. Reach out with thoughts on Twitter at @lethain, or reply to this email.

Posts from this week:

- Plagarism, idea theft, and writing online.
- Mailbag: Did I become a manager too soon?

Plagarism, idea theft, and writing online.

I’ve been in a handful of discussions over the past few weeks about plagiarization: how should authors approach their work being directly or indirectly copied?

When I started writing online in 2007, I was writing to learn to write, and my early stuff showed that, by which I mean it wasn’t very good. I mostly documented stuff I was learning in Django like creating a middleware for Google Analytics (please don’t follow any advice in that article: it’s 15 years out of date) or setting up Django and Nginx on Slicehost (Slicehost no longer exists). As I moved towards management, I was particularly inspired by Michael Lopp’s blog, who was, for me, a rare and thoughtful writer on engineering management.

There were certain elements of Lopp’s writing that made it a Lopp post, in particular the illustrative introduction story, like this one starting Free Electron. Did I try to steal Lopp’s approach to using introductory stories? Absolutely! Even today, much of my writing starts with a story following the pattern that I stole from Lopp, like this recent post on migrations. You can argue that Lopp is “just” using a lede, which I certainly learned about in school, but his particular approach to ledes was the one that inspired me.

There are many other cases where I’ve adopted folks’ techniques after reading them. When I started reading Brie Wolfson’s The Kool-Aid Factory, her brilliant approach of including ready-to-use templates inspired me to experiment with the same approach in my latest project. Even the approach of grounding Staff Engineer in individual’s stories was strongly influenced by reading Peter Siebel’s Coders at Work some years back. Neither Brie nor Peter were the first person to use templates or interviews, but their specific usage directly influenced me and my writing.

These sorts of stylistic thefts are, from my perspective, an inevitable part of writing. Most early writers start by copying, but any developing writer, even if they’ve been writing for many decades, is encountering and incorporating new ideas of style into their approach. If an author accumulates enough of the specific writing tells from another author, I think it’s reasonable for the latter to privately grump about it, but if it’s a slight then it’s a very minor one. If you look closely enough, in most cases the “real” crime is being too successful with a borrowed style, which to a bystander is quite difficult to distinguish from jealousy.

On the other end of the plagiarism spectrum, sometimes folks will copy your written words verbatim. My most memorable plagiarism story is about a paid online course that later became my most consistent source of referral traffic. A reader realized the online course had plagiarized this post on system architecture, complained to the website hosting the course, and they added a link to my article. This was a direct theft of my words, but I also never bothered reaching out about it. It’s not that I wasn’t annoyed, rather online plagiarism is simply so fertile a loam that combatting it is futile. At that moment, it was particularly common to see spam blogs that would populate their articles by consuming and reformatting the contents of your RSS feed. It wasn’t unusual to see a few RSS-feed copying blogs spin up each week, and I simply ran out of care. Every case of bulk, verbatim plagiarism is driven by the myriad, anonymous denizens of the internet. Every minute spent pursuing automated mass word theft is a minute lost to a greater endeavor (and the bar for “greater” here is low, you could pass it by walking to the kitchen to fetch a nice snack).

Somewhere between these two extremes is the deliberate theft of ideas. It’s not unusual to see some successful writer’s most popular pieces rewritten by other authors without attribution. Rewrites come in many forms. Some capture all the ideas from an original post while also introducing new ideas, a hesitant stretch towards Hegelian synthesis. Others precisely follow the original post’s structure and ideas while avoiding reuse of the original words. Sometimes flawed writing practices facilitate deliberate idea theft cascading into the theft of words as discussed in this piece, but I’ve found that relatively infrequent.

Of these three categories–style theft, automated word theft, idea theft–this third category is the one that I find folks have the hardest time coming to terms with. Unlike new authors borrowing your style, it unequivocally exceeds social norms of good behavior. Unlike mass plagiarism by bots, it’s committed by an identifiable individual. Further, it’s subtle enough that you’ll usually only notice your writing’s direct, unauthorized descendents if one becomes particularly successful.

In the past, I invested a lot of emotional energy into being frustrated by this, but my learned perspective is that authors should focus on viewing the writing community as a source of inspiration to learn from and be challenged by. We should avoid the temptation to police it, even when behavior is unequivocally bad, simply because authors are poorly positioned to police these crimes. It’s difficult to determine if our motivation is coming from a place of hurt, fairness, legalism, gatekeeping, or elsewhere. Worse, the attempt to police behavior warps our relationship with the wider community of authors into something poisonous and like most poisons it doesn’t benefit us: even when it’s wholly accurate, calling folks out creates more visibility of their derived work, generates an impression of our own insecurity, and consumes our emotional energy.

It’s not that no one should pay attention to this, rather that the role of rating, ranking and remunerating authors is the dominion of readers. As I’ve never seen a single positive thing come from authors pursuing others for alleged idea theft, I’m grateful that readers take this on rather than me!

Mailbag: Did I become a manager too soon?

I recently got an email about moving into an engineering management role too early in the email writer’s career:

I became an engineering manager two years ago, which was also two years into my career. The reason is mainly that we were a small team and when the time came to add line management I was around and down for it. I have loved this position, and find it extremely fulfilling to be able to remain technical and still have a deeply human job and build strong relationships with my team and across the company. I was quite successful at this job and well recognized in the company. Yet now that I am considering leaving the company, I feel like the “normal” path for an EM is to first have a lot of technical seniority and expertise (more than two years of IC work anyway). Deep down I want to remain a manager, but I am wondering if you think the sensible thing to do if I ever want to join a large organization as an EM, would be to instead go back to an IC role and build up my expertise?

The specific advice I give to folks who ask me this question is: if you are considering being a career manager, rather than just trying it for a few years, make sure you’ve accomplished what you want to as an engineer before cementing the transition. If you’re successful as a manager, it can be difficult to move back without slowing down your career.

Why do I give this advice?

You absolutely can move back and forth between manager and individual contributor work, as captured in Charity Majors' classic post on the engineer, manager pendulum. I’ve worked with many folks who’ve moved back and forth between these roles for the first ten or fifteen years of their career. That said, I do find it less common for folks to continue rotating across these roles as they get more senior, as there is a level of specialization that is difficult to attain while rotating.

Related to specalization, I’ve found that many folks encounter breakout roles in their careers which significantly advance them down the path they’re current on. My first breakout role was working in Uber’s infrastructure organization and founding the Uber SRE team. I could have moved back into an individual contributor role after that point, but there was an intense gravity pulling me to continue in the management track: over those two years I’d become a significantly stronger manager candidate than engineer candidate, and it was hard to walk away from the stronger career opportunities and compensation. This is a theme that I see in many folks’ careers: after a breakout role, it takes a lot of courage to walk away from that accelerating path, and very few folks do.

It’s not solely courage, it’s also a practical issue. The day to day work of a line manager in a small company has a lot in common with the work a senior engineer might be doing. This is less and less true the further you go up the technical and managerial career trees. As a VP of Engineering, you might spend most of your time on compensation policy and troubleshooting alignment between product strategy and the financial plan. As a Staff Engineer, you’d be doing very different work. This makes switching paths increasingly difficult as you move up the career ladder, unless you’re able to tolerate a reset in your career momentum. And maybe you should be, striving towards increasingly senior roles isn’t a very deliberate plan for working across a forty-year career.

These are all future concerns, and looking at your decision today, you can’t really make a wrong decision here. Similarly to you, I personally moved into a manager role after two years of full-time development experience, and it was entirely due to the company’s needs as all the managers had quit or been laid off. This early shift hasn’t harmed me, although I do wish I’d spent more time as an engineer simply because I really enjoyed that work. That said, forty years is a long time, and you can do a lot of stuff across that horizon!

That's all for now! Hope to hear your thoughts on Twitter at @lethain!

This email was sent to you why did I get this?    unsubscribe from this list    update subscription preferences Will Larson · 77 Geary St · co Calm 3rd Floor · San Francisco, CA 94108-5723 · USA