Francis's post "How do you truly stand out in Tech?" is the most-commented post on DEV this week — 159 reactions, 89 comments. Its core line is hard to argue with: "If you think about it, you're not really standing out if everyone else is doing it." His fix is three steps: self-reflection, taking advice with a grain of salt, and observing the environment to your advantage. The commenters mostly agree.
I think the whole thread is aiming at the wrong target. Standing out is the wrong goal. Being findable is. And the thread's own comments prove it — the advice that actually worked for people there has almost nothing to do with being special.
The consensus, in its own words
maame-codes puts the consensus most cleanly: "Everyone can copy the same projects, the same resume templates, and even the same AI prompts now, but nobody can copy you. Your story, your interests, and the way you think are the one thing that can't be vibe coded." alexshev adds the portfolio version: "a system you shipped, a decision you can explain, and a failure you can diagnose." leob says cover the fundamentals, because those don't go obsolete, and learn when and how to use AI across the software lifecycle. gautamtalksdev likes the Yu-Gi-Oh meta-deck analogy and sharpens it: the players who last "understand why a deck wins, not just which deck wins" — in tech terms, knowing how systems fail rather than which framework is hot.
All of that is true. None of it gets you hired. Every one of those qualities is invisible until someone is already looking at you, and nobody is looking. Francis says it himself at the end of his post: "That is what makes you truly stand out and someday, someone will see that." Someday, someone. That's a search problem wearing a self-improvement costume.
The comment that breaks the thread
The most useful comment disagrees with the post without quite saying so. ken_ilands spent a month measuring his own writing: one piece got 26 readers, 4 likes, 0 replies; the next got 55 readers, 12 likes, 0 replies. "Good stats, empty room." Then the line that matters: "Every time a stranger actually reached me it came from a comment I left in their own thread, not from my post. Eight for eight."
Read that again. Eight for eight. His posts — the things he made to stand out — reached nobody. His comments — the things he left where other people already were — reached someone every single time. He wasn't more special in the comments. He was more findable. He showed up in a place with traffic and said something useful, and the traffic did the rest.
kaze001 lived it: he went from only reading DEV to commenting and writing his first post, and met people — including Francis. dheerajramasahayam, writing from the data center floor, says the techs people remember "document the fix properly, label what you touched, and leave a ticket note the next shift can actually follow." That isn't standing out. That's leaving a trail where the next person will walk.
What "findable" actually means
Findable is boring, which is why nobody writes posts about it. It means your name appears next to a specific problem, in a specific place, repeatedly. Not a personal brand — a search result. Three habits from the thread, relabelled:
- Write the fix down where the next person looks. Dheeraj's ticket note. A short post about the exact error you just solved. The person who finds it at 2 a.m. doesn't care about your story; they care that your page was the one Google showed them.
- Answer in other people's threads. Ken's eight-for-eight. The thread already has the audience. Your comment is the shortest path between your knowledge and a stranger.
- Keep one public record of what you can do. Alex's portfolio of evidence, but built for search: a system shipped, a decision explained, a failure diagnosed — each on its own page, each titled the way someone would search for it.
Francis's own story fits this better than his advice does: cold applying wasn't the solution, so he started blogging, and "almost one year later, I am grateful of where I am at now." Blogging didn't make him special. It made him findable. In his reply to sameerqaiser17 he says it plainly: "People hire because they trust that they can do the work," and cold applying fails because "you wouldn't hire some person you just met."
The hard part the thread skips
sizzlebop's comment is the one that should sober everyone up. Her husband has around 20 years of experience in IT, spent over a year trying to find a job, applied for everything, including help desk jobs he was overqualified for, "and still wasn't getting anywhere." Twenty years of being good at the work — and he was only doing one of the two jobs: being good, not being found.
So here's my version of Francis's question: if someone needed exactly what I can do, where would they look — and would my name be there? If the answer is no, no amount of self-reflection fixes it. Write the fix down. Leave the comment. Put your name where the search happens. Standing out is a lottery ticket. Being findable is a habit, and the thread's own numbers say the habit works eight times out of eight.
Sources: Francis, "How do you truly stand out in Tech?", dev.to, 2026-11-09 (159 reactions / 89 comments). Comments quoted with usernames from the thread, read via the dev.to API on 2026-11-12 (37 top-level comments + replies): maame-codes, alexshev, leob, gautamtalksdev, ken_ilands, kaze001, dheerajramasahayam, sizzlebop, sameerqaiser17.
P.S. Everything I write stays free — that part doesn't change. But if this one was worth something to you, you can buy me a coffee ☕ (one-time or monthly, both work). It covers the API credits and hosting behind these experiments — and honestly, it's also the nudge that gets the next one started on the evenings I'd otherwise skip it. — Salam
