Stack Overflow by Ciro Santilli 37 Updated 2025-07-16
The best place to get answers to programming questions as of 2019. Google into Stack Overflow is always the best bet.
An overview of Ciro Santilli's Stack Overflow contribution can be found at: Ciro Santilli's Stack Overflow contributions.
Figure 1.
Stack Overflow in a nutshell
. Source.
As the "WTF look at my points" guy, Ciro Santilli approves of this meme. A few more elements could be added, notably deletion of the last link-only answer, but good enough.
By the profile image, the "Grammar Nazi" editor is actually appropriately the notorious serial editor Peter Mortensen. Ciro Santilli welcomes grammar fixes, but more subjective style fixes can be a bit annoying.
Figure 2.
Catching mice by Nakanoart
. Possible non-canonical source: twitter.com/nixcraft/status/1376023938749190147
Figure 3.
How stack overflow hires meme using Welcome Aboard! meme template
. Source.
  • always upvote questions you care about, to increase the probability that they will get answered
  • never upvote other people's answers unless you might gain from it somehow, otherwise you are just giving other high reputation users more reputation relative to you
  • only mark something to close or as a duplicate if it will bring you some advantage, because closing things creates enemies, especially if the OP has a high profile
    One example advantage is if you have already answered the question (and the duplicate as well in case of duplicates), because this will prevent competitors from adding new better answers to overtake you.
  • protect questions you've answered whenever someone with less than 10 reputation answers it with a bad answer, to prevent other good contributors from coming along and beating you
  • when you find a duplicate pool answer every question with similar answers.
    Alter each answer slightly to avoid the idiotic duplicate answer detector.
    If one of the question closes, it is not too bad, as it continues netting you to upvotes, and prevents new answers from coming in.
  • follow on Twitter/RSS someone who comments on the top features of new software releases. E.g. for Git, follow GitHub on Twitter, C++ on Reddit. Then run back to any question which has a new answer.
  • always upvote the question when you answer it:
    • the more upvotes, more likely people are to click it.
    • the OP is more likely to see your answer and feel good and upvote you
  • if a niche question only has few answers and you come with a good one, upvote the existing ones by other high profile users.
    This may lead to them upvoting or liking you.
    Even if they don't, other people will still see your answer anyway, and this will lead to people to upvoting you more just to make your great answer surpass the current ones, especially if the accepted one has less upvotes than yours. Being second is often an asset.
  • always upvote comments that favor you:
    • "I like this answer!" on your answers
    • "also look at that question" when you have answered that question
  • don't invest a lot in edits. They don't give you rep, and they can get reverted and waste your time.
    Why are you trying to help other people's answers to get rep anyways? Just make a separate answer instead! :-)
  • if you answer a question by newbie without 15 reputation, find their other questions if any and upvote them, so that the OP can upvote your answer in addition to just accepting
  • If you haven't answered a question, link to related questions you've answered on question comments, so more people will come to your answers.
    If you have answered the question, only link to other questions at the bottom of your answer, so that people won't go away before they reach your answer, and so as to strengthen your answer.
  • if a question has 50 million answers and you answer it (often due to a new feature), make a comment on the question pointing to your answer
  • if you get a downvote, always leave a comment asking why. It is not because you care about their useless opinion, but because other readers might see the comment, feel sorry for you, and upvote.
  • ask any questions under a separate anonymous accounts. Because:
    • intelligent people are born knowing, and don't ever ask any questions, so that would hurt your reputation
    • downvoting questions does not take 1 reputation away from the downvoter, and so it greatly opens the door for your opponents to downvote you without any cost.
After Ciro Santilli got a lot of attention on Hacker News news.ycombinator.com/item?id=19428700 his Stack Overflow account was suspended for 3 days web.archive.org/web/20190320163458/https://stackoverflow.com/users/895245/ciro-santilli-新疆改造中心-六四事件-法轮功 and he received a magic notification that led to a private message:
Hello,
I'm writing in reference to your Stack Overflow account:
I don't understand why you are actively promoting and assisting people to commit fraud on the site.
I've removed this from your profile github.com/cirosantilli/stack-overflow-vote-fraud-script and do not expect you to post it around the site.
I'm suspending you to gain your attention on this matter.
We have temporarily suspended your account; you may return after 3 days.
Regards,
To: Aaron Hall ♦;Andy ♦;Baum mit Augen ♦;Bhargav Rao ♦;Bohemian ♦;BoltClock ♦;Brad Larson ♦;ChrisF ♦;Cody Gray ♦;deceze ♦;Ed Cottrell ♦;Flexo ♦;George Stocker ♦;Jean-François Fabre ♦;Jon Clements ♦;josliber ♦;Madara Uchiha ♦;Martijn Pieters ♦;meagar ♦;Michael Myers ♦;Rob ♦;Robert Harvey ♦;Ry- ♦;Samuel Liew ♦;Undo ♦;Yvette Colomb ♦
Ciro's reply was:
Hi mods,
Reply and unsuspend quickly followed, with link still removed:
I suspended you to get your attention. Your attitude about going to Twitter about it does not bode well with me.
Feel free to have whatever you want in your GitHub repo. Just don't advertise tools to make it easier for people to circumvent the rules. As easy or as hard as it may be to circumvent them, you're handing it to people who may not be capable of doing so. It doesn't help.
Don't make threats to upload on an anonymous account. Accounts created to circumvent previous warnings are not welcomed on the site.
We don't need a meta thread to discuss whether it's ok to post voting fraud links in your profile and we definitely don't need to give it anymore publicity.
I'll unsuspend you, now we've had this discussion.
Regards,
A meta thread was later created by Yvette, kudos, to which Ciro answered with the correct unpopular answer that will be downvoted to oblivion: meta.stackoverflow.com/questions/381577/is-it-ok-to-have-links-on-how-to-create-sock-puppets-and-gain-rep-fraudulently-i/381635#381635
Yvette had also previously deleted one or two of Ciro's answers for being duplicates, which is a policy Ciro is against: if the questions are not dupes, a single answer might still directly reply to both of them.
Yvette later announced that she was leaving the website: meta.stackoverflow.com/questions/399495/leaving-the-site-and-the-network-mid-election-is-not-the-best-but-theres-no. This is evil, but Ciro was happy. He does not mean harm to Yvette, but in their limited interaction, Ciro disagreed with her choices.
Video 1.
The Great Places Erased by Suburbia by Not Just Bikes (2022)
Source. Stack Overflow, and other online forums, can serve as a sort of a third place for its more active users.
One may dream.
If they belive that their reputation is a representative meaningful metric, then it should be fine!
And if not, then they should fix it.
Notably, more people would try to "game" the system by quickly answering lots of small impact answers which could tilt things off a bit. Not to mention straight out fraud.
So basically less money into developers doing useless new features for the website, and more money back into meaningful contributors.
How about 2k USD / month for the number one contributor of the year, going linearly down to 0 for the 200th? This would be 100k USD / month, so about 12 developers.
There's no point.
The question remains there, but people lose the ability to help the asker.
Reputation is meaningless regardless, since JavaScript gurus will always have 1000x more readers than low level junkies.
The deeper problem: the existence of multiple separate websites instead of just using the tags on a single website.
It's great right? You can't link to your other answer alone: Stack Overflow link-only answer policy, but you can't copy the other answer either.
And because not all duplicate close votes succeed, see e.g. stackoverflow.com/questions/59649238/how-to-use-the-m5ops-in-gem5-such-m5-exit-and-m5-dump-stats-in-se-mode/63955139#63955139 the result is that someone else will come and answer the same thing in a different wording.
And some answers answer two questions that are not duplicates, e.g. superset/subset questions.
So just do a slight variation wording yourself and get all the reputation.
Why. Why. Why is there no limit to how much I can help, but there is a limit to how many thanks I can get?
At most, limit it to a single answer to avoid highly publicized events, e.g. an answer being shared on Reddit. But across answers? It makes no sense.
The two ways main ways to overcome this limit are the 15 point answer accept reputation and bounties.
200 reputation per day works out 73k a year BTW.
Ciro also really likes the following users, a bit less like Gods, and bit more like friends:
Nothing personal, just Ciro Santilli strongly disagrees with the moderation philosophies of these users.
One particular type of user Ciro particularly dislikes are those who do more moderation than content. Ciro finds it very hard to understand why some people spend so much time moderating. Maybe that's how politicians exist, some people just like that kind of activity.
The moderators tend to have lower intermediate rep. They spend too much time moderating and too little time coding.
Stack Exchange by Ciro Santilli 37 Updated 2025-07-16
Waste of time sub-sites that should instead be merged into Stack Overflow as different tags.
Nowhere is this waste more visible than at: cs50.stackexchange.com/. A website just for some specific course that is completely covered by other sites of the network? What a humongous waste!!!

Pinned article: Introduction to the OurBigBook Project

Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
We have two killer features:
  1. topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculus
    Articles of different users are sorted by upvote within each article page. This feature is a bit like:
    • a Wikipedia where each user can have their own version of each article
    • a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
    This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
    Figure 1.
    Screenshot of the "Derivative" topic page
    . View it live at: ourbigbook.com/go/topic/derivative
  2. local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:
    This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
    Figure 2.
    You can publish local OurBigBook lightweight markup files to either https://OurBigBook.com or as a static website
    .
    Figure 3.
    Visual Studio Code extension installation
    .
    Figure 4.
    Visual Studio Code extension tree navigation
    .
    Figure 5.
    Web editor
    . You can also edit articles on the Web editor without installing anything locally.
    Video 3.
    Edit locally and publish demo
    . Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.
    Video 4.
    OurBigBook Visual Studio Code extension editing and navigation demo
    . Source.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact