6 ms·

For those unable to open the link due to owner site being hit by Cloudflare limit, here's a link to web archive - https://web.archive.org/web/20250409082704/htt

For those unable to open the link due to owner site being hit by Cloudflare limit, here's a link to web archive - https://web.archive.org/web/20250409082704/https://endler.dev/2025/best-programmers/ https://web.archive.org/web/20250409082704/https://endler.de...

animesh 1y ago
Off-topic: is the rate-limit because they host on a Cloudflare compute service? I ask because I would like to know if this feature would be available for just using the domain hosting.
- fideloper 1y ago
  That feature exists on cloudflare outside of using CF workers or their own compute stuff. It's part of their WAF featureset.
  - Sxubas 1y ago
    I don't think it is WAF related, it clearly says: > If you are owner of this website, prevent this from happening again by upgrading your plan on the Cloudflare Workers dashboard. Looking into it, my hypothesis is that the owners page is SSRd using cloudflare workers and they reached the daily limits.
    - ryandrake 1y ago
      Looking at the archive.org mirror, the content is 2000 words and a few images. It constantly astounds me how much "compute" people seem to need to serve 10K of text in 50K of HTML.
      - jasonjmcghee 1y ago
        If your business is selling server side compute to render front end web apps on the back end, you try to convince an entire generation that it's needed. And a few companies have been very successful in this effort.
lapcat 1y ago
There's some irony, is there not, in presuming to be able to identify "the best programmers" when you've created a programming blog that completely falls down when it gets significant web traffic?
- semiquaver 1y ago
  Presumably the author didn’t claim that they were one of them :)
- gorjusborg 1y ago
  I think it is a fairly common trait of bad programmers to design a system based on completely unrealistic operating conditions (like multiple orders of magnitude of extra traffic). Now that they've gotten the hug of death they'll probably plan for it next time.
  - grayhatter 1y ago
    How many ways are their to build a site that doesn't have these defects and risks? Good engineers build things that eliminate failure modes, rather than just plan for "reasonable traffic". Short of DDoS, a simple blog shouldn't be able to die from reaching a rate limit. But given the site is dead, I can't tell, maybe it's not just a blog.
    - gorjusborg 1y ago
      > Good engineers build things that eliminate failure modes, Yes, but not all failure modes, only the ones in scope for the goals of the system. From the outside you can't tell what the goals are. There is no such thing as eliminating all failure modes, which was exactly the point I was making in my post above. The best you can do is define your goal clearly and design a system to meet the constraints defined by that goal. If goals change, you must redesign. This is the core of engineering.
      - grayhatter 1y ago
        > Yes, but not all failure modes, only the ones in scope for the goals of the system. From the outside you can't tell what the goals are. Is basic availability not a goal of a blog? Phrased differently: given two systems, one that fails if a theoretically possible, but otherwise "unpredictable" number requests arrive. And one without that failure mode. Which is better? > From the outside you can't tell what the goals are. I either don't agree, not even a tiny bit, or I don't understand. Can you explain this differently? > This is the core of engineering. I'd say the core of engineering is making something that works. If you didn't anticipate something that most engineers would say is predictable, and that predictable thing instead of degrading service, completely takes the whole thing down, such that it doesn't work... that's a problem, no?

animesh 1y ago

Off-topic: is the rate-limit because they host on a Cloudflare compute service? I ask because I would like to know if this feature would be available for just using the domain hosting.

fideloper 1y ago
That feature exists on cloudflare outside of using CF workers or their own compute stuff. It's part of their WAF featureset.
- Sxubas 1y ago
  I don't think it is WAF related, it clearly says: > If you are owner of this website, prevent this from happening again by upgrading your plan on the Cloudflare Workers dashboard. Looking into it, my hypothesis is that the owners page is SSRd using cloudflare workers and they reached the daily limits.
  - ryandrake 1y ago
    Looking at the archive.org mirror, the content is 2000 words and a few images. It constantly astounds me how much "compute" people seem to need to serve 10K of text in 50K of HTML.
    - jasonjmcghee 1y ago
      If your business is selling server side compute to render front end web apps on the back end, you try to convince an entire generation that it's needed. And a few companies have been very successful in this effort.

lapcat 1y ago

There's some irony, is there not, in presuming to be able to identify "the best programmers" when you've created a programming blog that completely falls down when it gets significant web traffic?

semiquaver 1y ago
Presumably the author didn’t claim that they were one of them :)
gorjusborg 1y ago
I think it is a fairly common trait of bad programmers to design a system based on completely unrealistic operating conditions (like multiple orders of magnitude of extra traffic). Now that they've gotten the hug of death they'll probably plan for it next time.
- grayhatter 1y ago
  How many ways are their to build a site that doesn't have these defects and risks? Good engineers build things that eliminate failure modes, rather than just plan for "reasonable traffic". Short of DDoS, a simple blog shouldn't be able to die from reaching a rate limit. But given the site is dead, I can't tell, maybe it's not just a blog.
  - gorjusborg 1y ago
    > Good engineers build things that eliminate failure modes, Yes, but not all failure modes, only the ones in scope for the goals of the system. From the outside you can't tell what the goals are. There is no such thing as eliminating all failure modes, which was exactly the point I was making in my post above. The best you can do is define your goal clearly and design a system to meet the constraints defined by that goal. If goals change, you must redesign. This is the core of engineering.
    - grayhatter 1y ago
      > Yes, but not all failure modes, only the ones in scope for the goals of the system. From the outside you can't tell what the goals are. Is basic availability not a goal of a blog? Phrased differently: given two systems, one that fails if a theoretically possible, but otherwise "unpredictable" number requests arrive. And one without that failure mode. Which is better? > From the outside you can't tell what the goals are. I either don't agree, not even a tiny bit, or I don't understand. Can you explain this differently? > This is the core of engineering. I'd say the core of engineering is making something that works. If you didn't anticipate something that most engineers would say is predictable, and that predictable thing instead of degrading service, completely takes the whole thing down, such that it doesn't work... that's a problem, no?