| 1. | | Evaluating LLMs for my personal use case (darkcoding.net) |
| 120 points by goranmoomin on Aug 24, 2025 | past | 47 comments |
|
| 2. | | Overthinking Leetcode's Two Sum with SIMD (darkcoding.net) |
| 2 points by killcoder on Feb 19, 2024 | past |
|
| 3. | | A small Rust binary indeed (2022) (darkcoding.net) |
| 102 points by estebank on Feb 18, 2024 | past | 47 comments |
|
| 4. | | epoll: The API that powers the modern internet (2022) (darkcoding.net) |
| 243 points by peter_d_sherman on Jan 11, 2024 | past | 65 comments |
|
| 5. | | The memory remains: Permanent memory with systemd and a Rust allocator (darkcoding.net) |
| 132 points by petercooper on Jan 10, 2024 | past | 76 comments |
|
| 6. | | OpenTTD: Trains and signals for beginners – a tutorial (2009) (darkcoding.net) |
| 4 points by Tomte on Aug 27, 2023 | past |
|
| 7. | | Rust atomics on x86: How and why (2022) (darkcoding.net) |
| 3 points by cwaffles on Feb 27, 2023 | past |
|
| 8. | | epoll: The API that powers the modern internet (darkcoding.net) |
| 2 points by cavemancoffee on Oct 23, 2022 | past |
|
| 9. | | Linux: What Can You Epoll? (darkcoding.net) |
| 264 points by todsacerdoti on Oct 22, 2022 | past | 125 comments |
|
| 10. | | A day in the life of a professional software engineer (darkcoding.net) |
| 122 points by gregdoesit on June 19, 2021 | past | 12 comments |
|
| 11. | | Gardening as a metaphor of incrementally writing software (darkcoding.net) |
| 2 points by goranmoomin on Dec 17, 2019 | past |
|
| 12. | | The Joy of Systemd (darkcoding.net) |
| 1 point by goranmoomin on Dec 17, 2019 | past |
|
| 13. | | Facebook’s Code Quality Problem (darkcoding.net) |
| 17 points by goranmoomin on Dec 17, 2019 | past | 9 comments |
|
| 14. | | A developer goes to a DevOps conference (darkcoding.net) |
| 405 points by fanf2 on Sept 28, 2019 | past | 291 comments |
|
| 15. | | A Developer Goes to a DevOps Conference (darkcoding.net) |
| 4 points by digitallogic on Sept 13, 2019 | past | 1 comment |
|
| 16. | | Facebook’s code quality problem (2015) (darkcoding.net) |
| 502 points by setra on March 13, 2017 | past | 226 comments |
|
| 17. | | Facebook’s code quality problem (2015) (darkcoding.net) |
| 3 points by jaybosamiya on Feb 22, 2017 | past |
|
| 18. | | Facebook’s code quality problem (darkcoding.net) |
| 80 points by bochoh on Nov 2, 2015 | past | 15 comments |
|
| 19. | | Go: The price of interface{} (darkcoding.net) |
| 1 point by _ikke_ on May 27, 2015 | past |
|
| 20. | | Release It: Write software for production (darkcoding.net) |
| 1 point by percept on Feb 23, 2015 | past |
|
| 21. | | Raw sockets in Go: IP layer (darkcoding.net) |
| 1 point by watermel0n on March 25, 2014 | past |
|
| 22. | | What if everyone worked remotely? (darkcoding.net) |
| 2 points by ipmb on Sept 2, 2013 | past | 2 comments |
|
| 23. | | Online upgrades in Go (darkcoding.net) |
| 2 points by kevinburke on July 24, 2013 | past |
|
| 24. | | Rust: What I learnt so far (darkcoding.net) |
| 6 points by usea on April 29, 2013 | past |
|
| 25. | | Go after four months (darkcoding.net) |
| 5 points by andrevoget on Aug 27, 2012 | past |
|
| 26. | | In-memory key-value store in C, Go and Python (darkcoding.net) |
| 186 points by nkurz on March 21, 2012 | past | 56 comments |
|
| 27. | | Go after four months (darkcoding.net) |
| 7 points by Bockit on March 6, 2012 | past |
|
