Baustin

Thanks for the response here, Jason. So, just to confirm, you're saying it is best to delete the original xyz.wpengine.com domain and add that as a redirect under our main domain name - in my case blog.smartbear.com (you may have come across it before).

Thanks again for keeping everything in context here.

"It happened to become an addictive product. I think it has become a problem," he explained as he chain smoked cigarettes.

Yeah! See everyone, this guy got it...

Well this is embarrassing, but the irony is not lost on us: http://imgur.com/Miokv4f

Woah, looks like you're right. Didn't see it at first but it definitely doesn't seem to be loading now.

Absolutely again. In both cases, people who had read this article commented saying they were glad to see it and re-read it. This is one of two posts that I would be fine re-posting year after year.

Sorry about that. If you're looking for a laugh, I actually do have a few developer/QA comics that I published to the same blog a while ago:

http://blog.smartbear.com/cartoons/so-i-heard-you-guys-like-...

http://blog.smartbear.com/mobile/5-software-cartoons-to-get-...

I think that's the point of the article. It's how to help without being a genius.

That's true, those are all great additions. Someone actually just left a comment this morning pointing any designers to http://open-karma.com/

"It's a Unix system! I know this."

That's a good point. I really should go back and split them up at some point.

A Listly user must have added one that they thought belonged on the list. I guess this could really become the top ##, depending on how many additions are made.

Looks like a Listly user added one that they thought should be on the list.

This post seems to have gotten buried very quickly (jumped from top 50 to #172 in a matter of minutes). Anyone have a reason why?

Sorry about that - you're right, I should have gone through to the original source. Didn't realize it was already posted. Thanks for clearing up!

Although I enjoy sitting around on Sunday and getting up-to-the-second updates on all of my players, I do wish I had played fantasy football back in those days. It just feels like we're spoiled today.

This article may not be as interactive as the tour, but I do think it's still a good introduction to the language, written by a Google employee.

Ahhh damn!

I mean... you've found the Easter Egg, congratulations!

[Fixed the link]

This should be all set now. Thanks for letting me know about the issue. You've made this post more readable for millions of nostaglia-starved programmers across the globe!

Thanks for sharing this. I'm not sure why that green tab is showing up there. It really is annoying. I'll see if I can get that out of there in the next few minutes.

That's a great point. I'm not sure we'll ever know for sure, but that kind of heavy load has been known to bring down both of these sites in the past.

Good point. Maybe the title should be changed to "most frequent" stressor. Either way, I think the main point of (and research behind) the article is pretty valid. Would you agree?

Looking into this now. Sorry about that!

Yeah, it's a blog post. It's not based in science or excruciatingly fact-checked. It's just one guy's slightly cynical take on American culture.

Indeed.

Sorry, really didn't mean to duplicate. Didn't realize I had posted it before, and someone else just put it up on Reddit today so I wanted to post here too. Will delete.

I voted "I don't have one now but I may have one," but after seeing on in person for the first time a week ago I am a little more hesitant. It took 3+ hours to print a chess piece!

I definitely see the value, but it will certainly take another five years before I'd be ready to actually buy one.

Looks to be back up now. Sounds like it was a load issue. Would love to hear any information about what actually caused the problem.

Thanks for posting. If anyone truly appreciates "beauty" or quality in software, it's Ole.

If you don't mind my asking, what version of SoapUI are you using? I'm not going to say that everything was fixed and all better after SoapUI 4.5, but the team did manage to fix some of the issues that we've been having on Mac.

That said, we know that our Mac version of SoapUI is still pretty rough (we actually have a blog post from a while of back referring to SoapUI 4.5 as the "suck less on Mac version"). The reason for this is partly because Apple is doing its damndest to break Java on the Mac. But we've also needed to work on improving the Windows version, since that is what most of our users use. In all honesty, the reason we even have a Mac-version of SoapUI is because that team has a childish love for all things Mac.

We do have great hopes for the long-term: The new Product owner for SoapUI, Matti, is a Mac guy, our Technology Director, Henrik, for the SoapUI team only uses Mac, and the SoapUI Scrum Master, Ulrika, is a Mac fanatic – hopefully this all pays off.

So, please bear with us; we're working on some other projects that will delay any work on the Mac. We're re-building our entire build and release process in order to be able to release tested and validated versions of SoapUI more frequently. Boring stuff, but the advantages are huge. We’re really hoping we'll be seeing improvements for the Mac over the next year.