DEV Community: Sudo Threads

How to Explain What You Do to Non-Technical People (A Developer's Survival Guide)

Sudo Threads — Sat, 23 May 2026 08:35:04 +0000

It's Thanksgiving. You've barely gotten your coat off. And there it is — the question, delivered by a well-meaning aunt with the confidence of someone who has never heard the word "backend" in their life:

"So what do you do again? You work on computers?"

You work on computers. Sure. That's one way to put it.

If you're a software engineer, you've had this conversation approximately four hundred times. At holidays. At weddings. On first dates. On airplanes next to strangers who are about to explain to you what "the cloud" is. And every single time, you have to decide: do I explain it properly, or do I just say "yeah, basically" and change the subject?

This is a survival guide for the former.

"So what do software engineers do all day?"

Great question, hypothetical relative. Let me explain.

You write instructions for a machine that has no intuition, no common sense, and will do exactly what you tell it — including the wrong thing, at scale, in production, on a Friday afternoon. You spend a significant portion of your day reading error messages that technically describe what went wrong but offer no emotional support whatsoever. You Google things you've Googled before. You attend meetings about meetings. You occasionally ship something that works, which feels like winning an Olympic event, except nobody outside your team knows it happened.

"But like... what are you actually building?"

The website your bank uses. The app your doctor's office crashes on. The thing that recommends you movies you've already seen. The checkout flow that breaks every time someone tries to pay with a gift card. The code that runs on servers in buildings you've never been to, doing things at 3am that no human is awake to witness.

You build the invisible infrastructure of modern life, and then get asked if you can fix someone's printer.

The Analogy Game (And Why It Never Quite Works)

Developers spend years developing analogies for this conversation. Here are the ones that get tried most often, and why they all fall slightly short:

"It's like writing a recipe." Close, but recipes don't throw a cryptic error if you forget a comma. And they don't have seventeen dependencies that all need to be updated before you can make pasta.

"Think of it like building with Legos." Except the Legos are invisible, some of them are on fire, and the instructions are a Stack Overflow answer from 2014 that may or may not still apply.

"I build apps." This one works until someone asks if you could build an app for their idea about a social network for dogs. (You could. You won't.)

The truth is, software engineering is one of those jobs where the output is real and valuable and everywhere, but the work itself is essentially invisible. You're thinking for a living. You're debugging systems in your head. You're holding fifteen context windows open at once in your brain while someone asks you to "just add one quick thing."

What Do You Actually Say?

Honestly? The best move is to find the thing in your domain they already use and connect it to that.

"You know how when you click 'pay' on Amazon and it actually works? I build the systems that make that happen."

"You know how your phone knows when you've been somewhere and asks if you want to review it? I work on stuff like that — except for [company thing]."

"You know that spinning wheel that shows up when a page is loading? I try to make that not happen."

This approach works because it anchors abstract work to concrete experience. It doesn't fully explain what you do, but it gives the other person a foothold. That's all they actually need. They don't want a systems architecture lecture. They want to feel like they understand, nod, and move on to asking if you want more pie.

The Gear That Says It Without Words

Some conversations you don't want to have at all. Sometimes you want your outfit to do the talking — or at least set expectations before the conversation starts.

The Works on My Machine Tee is perfect for this. It's a reference that fellow developers will immediately recognize (and silently salute you for) while confusing everyone else just enough that they might not ask follow-up questions. That's the goal.

For the holiday gathering where you know you're about to face the full interrogation, consider showing up in the git commit -m 'fixed it' Hoodie. It says "I'm a professional, I'm warm, and I have committed code without looking at what changed." Relatable to your team. Opaque to your extended family. Perfect on both counts.

And if you want something to put on your desk while you're on the video call where someone asks why you can't just use Excel for the database, the Undefined is Not a Function Mug is a deeply specific error message that will resonate with anyone who's done JavaScript and baffle everyone who hasn't. Which is the correct distribution of reactions.

The Real Answer

Here's what you actually do: you solve problems that haven't been solved before, using tools that are constantly changing, under constraints that are often contradictory, for requirements that shift mid-sprint. You think in systems. You care about edge cases. You're comfortable with uncertainty in a way that most people aren't, because your entire job is operating in the space between "it should work" and "it does work."

That's harder to put on a Thanksgiving table than "I work on computers." But it's the truth.

And if all else fails, just say you're in IT. Nobody asks IT follow-up questions. They just want you to look at their printer.

Browse developer-humor apparel that explains the job without words at Sudo Threads.

Best Gifts for Software Engineers (That They'll Actually Use)

Sudo Threads — Sat, 23 May 2026 08:34:20 +0000

If you've ever tried to buy a gift for a software engineer, you know the drill. You Google "gifts for programmers," get a list that includes a coffee mug with binary on it, a rubber duck, and a Raspberry Pi kit they definitely won't have time to assemble. You panic-buy the mug. They smile politely. It goes in a drawer.

This list is different. These are things developers actually want — because they were picked by someone who works with developers and has seen what stays on their desk versus what gets re-gifted at the company white elephant.

Funny Programmer Shirts They'll Actually Wear

Developers are opinionated about their T-shirts. The bar isn't "has a computer on it." The bar is "do my coworkers understand why this is funny without me having to explain it." That's a surprisingly high bar.

Works on My Machine Tee — The phrase every developer has said at least once (and regretted immediately). This shirt is the universal programmer excuse, immortalized in cotton. It's the kind of thing they'll wear to stand-ups, to the office, and to every future job interview they do remotely. Grab it at Sudo Threads →

git commit -m 'fixed it' Hoodie — This one hits different for anyone who's ever pushed a vague commit message at 11pm and hoped nobody would notice. Comfortable, warm, and says everything about how software actually gets shipped. Perfect for the developer who lives in hoodies from October to April (so, all of them). Shop the hoodie →

CSS is Hard Tee — Okay, this one is for a specific type of developer: the backend engineer who refuses to touch the frontend but occasionally has to, or the frontend engineer who is tired of pretending CSS makes sense. It does not make sense. This shirt is cathartic. Get it here →

These aren't novelty items that get shoved in a box — they're the shirts developers actually reach for on casual Fridays because they fit, they're comfortable, and they land a joke without being cringe.

The Mug Situation

Yes, we're recommending a mug. But hear us out.

Undefined is Not a Function Mug — If you've spent any time with JavaScript, this error message lives rent-free in your head. It's the thing that shows up at 4pm on a Friday when you thought you were done. Having it on a mug is either deeply therapeutic or darkly funny, depending on the day.

The key thing about developer mugs: they need to survive the dishwasher, hold at least 12 oz, and be something they'll actually put on their desk rather than in the cabinet. This one checks all three. Check it out →

Gear That Actually Gets Used

Beyond apparel, here's what actually stays on a developer's desk:

A good mechanical keyboard — Not a specific model here because opinions are violent, but if you know their preference (tactile vs. linear, tenkeyless vs. full-size), a mechanical keyboard is always appreciated. Budget: $80–150 for something genuinely good.

A monitor arm — Sounds boring. Immediately beloved. Frees up desk space, reduces neck strain, and makes any setup look cleaner. The VIVO and Ergotron models are both solid. Around $30–60.

Desk cable management — The developer equivalent of a clean house. Cable clips, velcro ties, or an under-desk cable tray will make them quietly happy every day. Under $20 and totally thoughtful.

A good pair of headphones — Noise-canceling is the key feature. Sony WH-1000XM series and Bose QuietComfort are the standards for a reason. Tells the world "I am in the zone, do not interrupt me." $200–350 if you're feeling generous.

Books Worth Having

The trick with developer books is to not buy the one that was cutting-edge in 2008. Here are a few that are still genuinely worth reading:

The Pragmatic Programmer (20th Anniversary Edition) — Less about specific languages and more about how to think about software. Holds up extremely well.

A Philosophy of Software Design — Short, dense, and useful. Forces you to think about complexity in a different way. Good for developers at any level.

Designing Data-Intensive Applications — If they work with data at scale (and most backend developers eventually do), this is the one. Dense but worth it.

What to Skip

For balance: the things that look like good developer gifts but usually aren't.

Novelty USB drives shaped like things — Cute in theory, instantly lost.

Smart home gadgets they didn't ask for — Everyone has an opinion about smart home stuff. If they haven't mentioned it, don't assume.

"Learn to code" books — If they're already a software engineer, this reads as unintentionally insulting.

The RGB everything phase — Unless they're actively into battlestation aesthetics, RGB accessories can feel like buying a gift for the computer, not the person.

The Bottom Line

The best gifts for software engineers are either things that make their daily work more comfortable (keyboard, monitor arm, headphones), things that make them laugh (and fit the culture they actually live in), or things that are genuinely useful and won't sit unused for six months.

Apparel from Sudo Threads lands in that last category — the designs are written by developers, for developers, and the jokes land without explanation. That's the bar. That's the whole bar.

If you're stuck, the "Works on My Machine" tee is a safe bet for almost any developer with a sense of humor. The git commit hoodie is the move if they're a hoodie person. And the mug is for the JavaScript developer in your life who needs to see their pain acknowledged in ceramic form.

Good luck. And if all else fails, a gift card to Amazon is never wrong and you don't have to read this list at all.

Browse all developer-humor apparel at Sudo Threads — shirts and gear with jokes that actually land.

21 Actually Funny Gifts for Programmers (That Aren't a Mechanical Keyboard)

Sudo Threads — Thu, 21 May 2026 09:03:22 +0000

I have, in my possession, a rubber duck wearing a tiny graduation cap. A mug that says "I turn coffee into code" in a font that predates the iPhone. And somewhere in a junk drawer, a USB hub shaped vaguely like Tux the Linux penguin that never once worked reliably. These were all gifts. They were all given with love. They are all deeply bad.

The problem with buying gifts for programmers is that the internet has decided we want anything with a semicolon on it. We don't. We want things that are actually funny — the kind of funny that comes from recognizing something painfully true, not from someone who learned what a variable is and ran with it. There's a difference between a gift that makes a developer laugh and a gift that makes a developer politely say "oh wow, haha" and immediately put it in a bag for Goodwill.

Here's a list of things that land in the first category. No Tux USB hubs. I promise.

// 01. Works on My Machine Tee

The universal programmer excuse, now wearable. Every developer has said this with 100% confidence while pushing a bug to production — usually right before a frantic Slack message at 6pm asking why staging is on fire. The beauty of this shirt is that it doesn't just describe a behavior; it describes a worldview. A very specific kind of optimism that only developers have. Grab it at Sudo Threads.

// 02. git commit -m 'fixed it' Hoodie

The commit message every senior developer writes at 11pm on a Friday. Not "fix: resolve null pointer exception in UserService#processPayment" — just "fixed it." Done. Shipped. Going home. This hoodie is cozy, oversized, and deeply relatable to anyone who's ever shipped something they weren't quite sure about. Available at Sudo Threads.

// 03. Undefined is Not a Function Mug

A classic JavaScript error so common it's practically a greeting. Every front-end developer has stared at this message at 9am, coffee in hand, wondering why they chose this career. Put the error message on the coffee mug. Poetic. Available at Sudo Threads.

// 04. Rust or Bust Tee

For the developer who has opinions about memory safety. Strong opinions. Opinions they will share whether you asked or not. If you know a Rust evangelist, they'll wear this shirt to every meetup and feel absolutely correct about it. Also available at Sudo Threads.

// 05. CSS is Hard Tee

It is. It genuinely is. And no amount of "just use flexbox" tweets will change the fact that centering a div has ended careers. This shirt is for the developer who has lost hours to a margin that was actually a padding, and who came out the other side with a very specific kind of calm. Sudo Threads has you covered.

// 06. Senior Dev / Still Googling Everything Hat

The dirty secret of software engineering: experience doesn't mean knowing everything, it means knowing how to find it faster. Every senior dev is still googling "how to exit vim" at least once a quarter. This hat is a badge of hard-won honesty. Available at Sudo Threads.

// What Actually Makes a Good Developer Gift

The pattern you might notice: everything above works because it's true. Not "haha computers go brrr" true, but specifically, painfully, recognizably true to anyone who's spent real time writing software.

The rubber duck doesn't make a developer laugh because it's a rubber duck. It makes them laugh because they've actually talked to a rubber duck to debug something. The gift acknowledges the reality of the job — the weird rituals, the imposter syndrome, the commits that probably could've been more descriptive.

So if you're shopping for a developer: find something that shows you actually understand what they do all day. Not the Hollywood version (furious typing, green text on black screens), but the real version: the Stack Overflow tabs, the "it works, don't touch it" commits, the eternal JavaScript errors.

// The Rule of Thumb

Before buying anything for a developer, ask: would this make them laugh because it's universally "geeky," or because it's specifically true about their job? The second one is the gift worth giving. Bonus points if they can wear it to standup.

These are all real products at sudothreads.launchyard.app if you want to rep the struggle.