Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #3034

T

The Coding Nest

Personal blog · codingnest.comprogramming

The Coding Nest is a personal blog at codingnest.com about programming. Since 2018, 25 different Hacker News readers have linked it 32 times, most often “Modern SAT solvers: fast, neat and underused”. The last post was in 2024, but the archive is still widely read.

Visit the blog
32mentions?
25HN people?
2018–2026first – last linked?
Links on Hacker News per year · peak 7 in 2018

Too few sampled comments (7) to say how often HN recommends it.?

Why HN links it

HN readers link this blog for its series on modern SAT solvers, which argues that generic solvers can get most of the way to a solution with little effort. It is also cited for a CMake tutorial.

Summarised by Claude from a sample of 7 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

The stash of knowledge magpies.

Most-linked posts?

  1. Modern SAT solvers: fast, neat and underused
    8 people · 8 mentions · first linked 2018-08-03
  2. Generating random numbers using C++ standard library: the problems
    4 people · 4 mentions · first linked 2020-05-18
  3. Where did <random> go wrong? [pdf]
    3 people · 3 mentions · first linked 2025-06-03
  4. The Missing Performance in std:vector
    2 people · 2 mentions · first linked 2023-08-27
  5. Modern SAT solvers: fast, neat and underused
    2 people · 2 mentions · first linked 2019-04-17
  6. The Little Things: My?radical? opinions about unit tests
    2 people · 2 mentions · first linked 2022-09-11

What Hacker News says?

  1. hmm I wonder if the article about SAT solvers defines them? https://codingnest.com/modern-sat-solvers-fast-neat-underuse...

    Comment linking /modern-sat-solvers-fast-neat-underused-part-1-of-n/

    on “Modern SAT solvers: fast, neat and underused”
  2. Submitted Modern SAT solvers: fast, neat and underused as a story · 465 points

    HN discussion
  3. The article series Modern SAT Solvers: Fast, Neat, and Underused [1] argues that we don't use generic problem solvers enough in our daily engineering work. A generic solution won't beat a hand-optimised specific solution, but if you're good at phrasing your problem in the right way, you can get 80 % of the way there with 20 % of the effort by using a generic solver. Z3, being an even more generic SMT solver rather t…

    Comment linking /modern-sat-solvers-fast-neat-underused-part-1-of-n/

    on “Z3 Tutorial”
  4. Submitted Modern SAT solvers: fast, neat and underused as a story · 368 points

    HN discussion
  5. The author does discuss this in a footnote: https://codingnest.com/basic-cmake/#fn4 In this case, I think I agree. Otherwise ya, try to avoid set. Except for CACHE variables, I think.

    Comment linking /basic-cmake/

    on “Modern CMake short tutorial and best practice”
  6. Submitted Modern SAT solvers: fast, neat and underused as a story · 237 points

    HN discussion
  7. A closely related technique to SAT solvers is the "Constraint Satisfaction Problem" which I've been looking into recently. Constraint Programming and SAT are BOTH NP-complete problems, and as such, they are mathematically equivalent. However, its sometimes more "obvious" to write problems in one form vs the other. For example, Sudoku is simply written 27 constraints: * All Different (X11, X12, X13, X14, X15, X16, X1…

    Comment linking /modern-sat-solvers-fast-neat-underused-part-1-of-n/

    on “Modern SAT solvers: fast, neat and underused – part 2”
  8. Submitted Modern CMake short tutorial and best practice as a story · 170 points

    HN discussion
  9. That's not really an option for me when I debug C++ that is run on a Linux or Android TV. It also wouldn't be an option when I used to work with C++ that was used on Linux servers. That's a big chunk of C++ use. While I have your attention, I see your comments here in C++ threads quite often. You seem to like the language and at the same time you have some experience with simpler languages like Oberon. My experience…

    Comment linking /generating-random-numbers-using-c-standard-library-the-problems/

    on “Goals and Priorities for C++”
  10. Submitted Modern SAT solvers: fast, neat and underused – part 2 as a story · 154 points

    HN discussion
  11. Penyngton · 2022-10-07Recommends
    I'm surprised not to see any mention of satisfiability here. There are a few papers I've seen about it, but this blog post seems to give a reasonable overview: https://codingnest.com/modern-sat-solvers-fast-neat-underuse... Then you just need to start counting models, which is the #SAT (sharp SAT) problem: https://en.wikipedia.org/wiki/Sharp-SAT Using software such as: https://github.com/marcthurley/sharpSAT

    Comment linking /modern-sat-solvers-fast-neat-underused-part-1-of-n/

    on “Will We Ever Run Out of Sudoku Puzzles?”
  12. Submitted The Little Things: Speeding up C++ compilation as a story · 133 points

    HN discussion
  13. I'm not familiar with that game, but depending on what the goal is, I think you have three options: - if you want to check that a complex system of rules has a solution, then you can translate that into a SAT problem and run a SAT solver ( https://codingnest.com/modern-sat-solvers-fast-neat-underuse... ) - if the problem is small enough, you could run an exhaustive search of options - in that case it really doesn't…

    Comment linking /modern-sat-solvers-fast-neat-underused-part-1-of-n/

    on “Solving a simple puzzle using SymPy”
  14. Submitted Generating random numbers using C++ standard library: the problems as a story · 96 points

    HN discussion
  15. Submitted Modern SAT solvers: fast, neat and underused (2018) as a story · 12 points

    HN discussion
  16. Submitted The Little Things: Comparing Floating Point Numbers as a story · 10 points

    HN discussion
  17. Submitted Where did <random> go wrong? [pdf] as a story · 6 points

    HN discussion
  18. Submitted What went wrong with <random>? [pdf] as a story · 3 points

    HN discussion
  19. Submitted Generating random numbers using C++ standard library: the solutions as a story · 3 points

    HN discussion
  20. Submitted Where did C++ <random> go wrong? [pdf] as a story · 2 points

    HN discussion
  21. Submitted The Missing Performance in std:vector as a story · 2 points

    HN discussion
  22. Submitted The Little Things: My?radical? opinions about unit tests as a story · 2 points

    HN discussion
  23. Submitted Generating random numbers using C++ standard library: the problems as a story · 1 points

    HN discussion
  24. Submitted The Little Things: The Missing Performance in Std:Vector as a story · 1 points

    HN discussion
  25. Submitted The Little Things: Why you should always have benchmarks ready as a story · 1 points

    HN discussion
  26. Submitted The Little Things: My?radical? opinions about unit tests as a story · 1 points

    HN discussion
  27. Submitted Generating Random Numbers Using The C++ Standard Library: The Problems (2020) as a story · 1 points

    HN discussion
  28. Submitted The Little Things: Everyday Efficiencies in C++ as a story · 1 points

    HN discussion
  29. Submitted Modern SAT solvers: fast, neat and underused (part 1 of N) as a story · 1 points

    HN discussion
  30. Submitted Modern SAT solvers: fast, neat and underused – part 3: CDCL as a story · 1 points

    HN discussion

Search all of HN for codingnest.com

Linked by the same people?