[7Figures2Commas]

I empathize with you, but your experience highlights the flaws in the approach you're advocating.

I'll use myself as an example: I'm a self-taught developer who has built and managed high-profile, high-usage websites/web applications. I probably could not pass one of your algorithm-based FizzBuzz tests, but if I was hiring and you suggested that a site should scale simply because you threw it on a large AWS instance, I would not consider your candidacy further regardless of your ability to pass a FizzBuzz test.

[saching90]

I did not intend to say that the blog should work simply because we threw it on a large instance, we have been running our site on AWS and have successfully handled much larger load. We never needed to move beyond a larger server for the main site, of course with horizontal scaling. What I meant was, when you are swamped with so many things you don't want to spend too much time on things like maintaining your blog.

You want to focus on the product, fix bugs, look after feature request, produce high quality content. And then your blog crashes and things get derailed.

[7Figures2Commas]

> I did not intend to say that the blog should work simply because we threw it on a large instance...

That's precisely what you said:

"You thought a large server would be enough to handle a single wordpress blog..."

> when you are swamped with so many things you don't want to spend too much time on things like maintaining your blog.

A competent developer should be able to set up a load balanced WordPress blog (with Nginx/PHP-FPM, Varnish and a separate database server) in a day or less. There are a number of well-written tutorials on this.