This document is the result of a series of discussions, some online and some in person, held between Robert "Uncle Bob" Martin and John Ousterhout between September 2024 and February 2025
https://github.com/johnousterhout/aposd-vs-clean-code/blob/main/README.md
Tiger Style is a coding philosophy focused on safety, performance, and developer experience. Inspired by the practices of TigerBeetle, it focuses on building robust, efficient, and maintainable software through disciplined engineering.
edit: this seems to be a variation of the original source
advent_of_code 2025 is live! https://adventofcode.com/2025
i never managed to complete more than the first few before leisure time ran out and pre-christmas chores took over.
OOP-bashing seems fashionable nowadays. I decided to write this article after seeing two OOP-related articles on Lobsters in quick succession. I’m not interested in defending or attacking OOP, but I do want to throw in my two cents and offer a more nuanced view.
https://lesleylai.info/en/fifty_shades_of_oop/ HN
worth the read IMO
on windows i'm running a triple monitor setup - center for the IDE, left for logs, debugging and documentation and right for communication (email, chat).
sometimes, when i play games i wish to turn off the peripheral monitors for better immersion; also my graphics card is probably happy having to render a few million pixels less.
usually, i just used the physical buttons to turn the monitors off, but after a defect i've had to get a new one that places its on/off switch at the back, which i can't easily reach.
nirsoft to the rescue: enable/disable or power on/off monitors over software with MultiMonitorTool
fun article about solving fizzbuzz with cosines by susam_pal: https://susam.net/fizz-buzz-with-cosines.html
then, in the hn comments, there's even more: vidrun's fizz buzz at aphyr.
PS: also in the comments - joel grus' FizzBuzz in tensorflow: https://joelgrus.com/2016/05/23/fizz-buzz-in-tensorflow/
The phrase “favor composition over inheritance” has become one of those thought-terminating cliches in software design, and I always like to take a deeper look at those to understand where they come from and what ideas we’re missing if we just take the phrase at face value without engaging with the discussion that led to it.