Live data from Hacker News

Programmer excuses

programmerexcuses.com

21–30 of 69 posts

Re: Programmer excuses

#22

That's an interesting webpage. it has a hidden google ads-field in an iframe. I'm not web-savy enough to fully understand how it works. The "click me as often as you can" contents for sure generate a lot of clicks. genius!

I see my GET request for show_ads.js is failing. So perhaps that nonloading javascript is suppose to make it appear but it's non working at the moment... Now, which excuses from the site would apply here?

Here's the first one that might make sense that showed up on my refresh: "It worked yesterday"

UPDATE: Must be Ad Block blocking it.

Re: Programmer excuses

#23
post #22

That's an interesting webpage. it has a hidden google ads-field in an iframe. I'm not web-savy enough to fully understand how it works. The "click me as often as you can" contents for sure generate a lot of clicks. genius!

I see my GET request for show_ads.js is failing. So perhaps that nonloading javascript is suppose to make it appear but it's non working at the moment... Now, which excuses from the site would apply here? Here's the first one that might make sense that showed up on my refresh: "It worked yesterday" UPDATE: Must be Ad Block blocking it.

Are you using Adblock or similar software?

Re: Programmer excuses

#24
post #22

Earlier quoted context omitted.

I see my GET request for show_ads.js is failing. So perhaps that nonloading javascript is suppose to make it appear but it's non working at the moment... Now, which excuses from the site would apply here? Here's the first one that might make sense that showed up on my refresh: "It worked yesterday" UPDATE: Must be Ad Block blocking it.

Are you using Adblock or similar software?

Yup, it was Ad Block.

Re: Programmer excuses

#27

On one reload I got a standard internal server error message. Next reload it was gone. If that was on purpose, it is a nice touch.

I got this twice and I went to go look at the response to see if it was actually a 200 implying that it was purposeful, but once I loaded up the dev console to see the headers I couldn't reproduce.

Try DoSing the page by holding down F5 for a second or two...

Status comes back as 500 not 200.

Post reply on HN