The Developer's Sacred Vow on Documentation

Level 1: Chores? Not Today

Imagine your teacher or parent asks you to write down instructions for a game you made or to clean your room. It’s something you know you should do, but you really don’t feel like doing it right now. So you cheekily respond, “Not today.” You’re not saying “no, never”; you’re just pushing it off because it feels like a boring or difficult chore. This meme is exactly that, but for computer programmers and their “chores.”

In this picture, a programmer is joking that writing documentation (which is like writing an instruction manual for their code) is the task they want to avoid. It’s like when you say “I’ll do my homework tomorrow” every day. Developers often say “I’ll write the docs later.” The funny part is we all recognize that feeling of procrastinating — whether it’s cleaning your room or writing stuff for work. By using the heroic line “Not today,” the meme makes a simple lazy answer sound bold and epic. It’s as if refusing to do a boring task today is a brave act (when in reality, it’s just putting it off!).

So, the easy takeaway: programmers find writing documentation to be a bit of a dull duty, kind of like kids find chores or homework. The meme shows a common playful excuse: “Not today.” It’s humorous because it’s a fancy way to say “I don’t want to do it right now,” and we’ve all been there.

Level 2: I'll Do It Later

At this level, let’s break down the joke in simpler terms. The image is a screenshot of a tweet where a developer asks, “What do we say to writing documentation?” and then answers, “Not today.” This is a playful twist on a famous line from Game of Thrones. In the show, a character is taught to say “Not today” when faced with death. The meme replaces “death” with “writing documentation,” implying that for developers, being asked to write docs feels like facing something they'd rather avoid at all costs!

Documentation in software development means any written text or guides that explain what the code does, how to use a system, or how to set up and run a project. It can be things like README files, wikis, API guides, or even comments in the code. Good documentation is super helpful: it’s like a map or instruction manual for other developers (or your future self) to understand the project. It improves the developer experience (DX) by making it easier to onboard new team members, troubleshoot issues, or use a tool without having to ask someone else for help. When documentation is missing or poor, it leads to frustration and confusion – these are the DocumentationWoes the tags mention.

Now, why would a developer joke about saying “Not today” to writing docs? Because procrastination (putting things off until later) is a very common habit, especially for tasks that feel tedious or secondary. Writing docs often falls into that category. Many developers enjoy writing code and solving problems but cringe at the idea of spending time writing instructions or explanations. It’s not that they don’t see the value; it’s more that coding new features or fixing bugs always feels more urgent or rewarding. So, documentation keeps getting delayed. Teams might say “We’ll document this in the next sprint” (meaning the next development cycle) and then push it again. It becomes a running joke – everyone knows docs are important, yet somehow there’s never time today to do them. That’s what we mean by documentation_procrastination or documentation aversion: continuously deferring the task of writing things down.

The tweet format itself is a bit of TechHumor that’s very common on developer Twitter. The account @iamdevloper (specifically spelled without the second 'e') is famous for these kinds of relatable programming jokes. By screenshotting the tweet, it turned into a meme that spread across other platforms. Many devs saw it and thought, “Haha, so true!” because it captured an experience they deal with daily. This is labeled RelatableDevExperience since pretty much any programmer, junior or senior, can relate to the guilt of not writing documentation and joking about it.

Let’s clarify the Game of Thrones reference a bit more for those unfamiliar: In that show, a young swordswoman’s mentor asks, “What do we say to the God of Death?” and she answers, “Not today.” It’s a way of saying she’s not going to give up or die today. In the meme, the “God of Death” is replaced by “writing documentation.” It humorously suggests that writing docs is as scary or unwelcome as death to a developer. Of course, that’s an exaggeration – writing docs isn’t actually life-threatening! – but exaggeration is a big part of humor. This falls under ProcrastinationHumor because it’s making fun of how we avoid tasks.

So, for a junior developer or someone new to tech, the meme is basically saying: developers often delay writing documentation, jokingly acting like it’s a big scary thing they’ll deal with some other day. It highlights a real issue in software teams: everyone prefers coding over documenting, so documentation tends to be incomplete. The impact is that later, other devs (maybe you!) will have a tough time understanding the code. That’s why experienced folks emphasize how important it is to write docs, even if the meme makes us laugh at the tendency not to. After all, it’s funny because it’s true.

Level 3: The "Not Today" Syndrome

This meme hits on a classic case of documentation aversion in developer culture, dramatized with a Game of Thrones twist. It shows a tweet from I Am Devloper (a popular dev humor account on Twitter) asking: “What do we say to writing documentation?” and answering with the punchline: “Not today.” This is a direct reference to the famous line “What do we say to the God of Death? Not today.” from Game of Thrones. By swapping out “death” for “writing documentation,” the meme exaggerates how dreaded documentation writing is — as if it’s the ultimate enemy developers must face.

For seasoned engineers, this joke lands because it reflects an all-too-familiar reality. Writing docs is often treated like an optional boss fight you keep postponing. There’s a palpable DocumentationWoes across teams: everyone knows good docs are critical for maintainability and smooth developer experience (DX), yet when sprint planning comes, documentation tasks get pushed to “later” (which usually means never). It’s practically an unwritten rule in some codebases that the comment // TODO: add documentation later will stick around longer than some developers stay at the company. In other words, “Not today” becomes “not this week, not this month”… and before you know it, the knowledge exists only in tribal memory.

Why is this so funny (and painful) for experienced devs? Because it captures the relatableDevExperience of accruing technical debt in the form of missing docs. Here are a few senior-perspective insights wrapped in the humor:

• Knowledge Silos and Bus Factor: When documentation is always postponed, critical knowledge lives only in the heads of a few developers. If one of them goes on vacation (or gets hit by the proverbial bus), the team is in trouble. This is often called a low bus factor, and it’s a scary scenario. Yet devs continue to say “not today” to writing things down, implicitly accepting the risk.
• On-Call Nightmares: A DeveloperExperience_DX horror story: it’s 3 AM, production is on fire, and you’re frantically searching Confluence or the project wiki for troubleshooting steps… only to find an empty page or a stub that says “Documentation coming soon.” The meme’s dark humor resonates because many of us have been that developer, staring into the abyss of an undocumented system. It’s basically the Night’s Watch of tech: “I shall live and die at my post… googling code I didn’t write with no docs to guide me.”
• Agile’s Double-Edged Sword: Older devs remember the days of massive requirement docs and design spec binders (which often became obsolete fast). Modern Agile methodology said “working software over comprehensive documentation,” which was great to cut out fluff, but teams often interpret it as “no docs at all.” This tweet mocks how we swung from one extreme to the other. Now documentation has become the tech debt nobody wants to pay down. Senior engineers chuckle (or groan) because they know the DocumentationAversion that Agile procrastinationHumor has enabled: “We’ll add docs later, we’re Agile, right?” – Not today, my friend.

The Game of Thrones reference elevates the drama: writing docs is jokingly portrayed as a life-or-death confrontation. In the show, saying “Not today” to Death is heroic; in tech, saying “Not today” to documentation is almost cowardly – yet we all do it. It’s a wink to pop culture that makes the meme extra shareable as a dev_twitter_memes classic. The combination of a beloved fantasy quote and a painfully real developer habit creates a DeveloperHumor one-two punch. We laugh, but it’s the uneasy laugh of knowing we’re guilty of this. Every senior developer has that tale of a project with zero docs that came back to haunt them. The meme succinctly captures that universal experience in one snappy, nerdy quote.

In sum, this meme thrives on irony and shared understanding. It’s funny because it’s true: ask devs for documentation and you’ll hear “Not today” echo throughout the office. Knowledge sharing gets postponed indefinitely, and we joke about it to mask the guilt. Like many devTwitter memes, it unites engineers by poking fun at our own bad habits. The humor works on multiple levels — it’s a pop culture gag, a commentary on DocumentationHumor and documentation_procrastination, and a nod to the eternal struggle between getting features done and writing things down. The veteran perspective sees the deeper cautionary tale: keep saying “not today” to docs, and one day (when things go wrong) you’ll wish you hadn’t. But… as this meme implies with a smirk, we’ll worry about that later.

# Code snippet reflecting real life:
def launch_prod_fix(issue):
    apply_hotfix(issue)
    # TODO: Document this fix and its impact... eventually
    return "Fixed for now"

# The TODO above is essentially the developer saying "Documentation? Not today."