So, I decided to treat your awful comment like you decided to treat the original article. > I have to That's not true. You don't have to reply. No one is re

So, I decided to treat your awful comment like you decided to treat the original article. > I have to That's not true. You don't have to reply. No one is requiring you do that. You've already started off by lying. This means anything else you might want to contribute is awful and worthless. > say You didn't. You typed it out. I'm pretty sure you didn't "say" anything. And now you are trying to be confusing. That's just awful. > , that headline font is awful Well, that's your opinion. Your opinion is worthless because you haven't validated your credentials. > and the link highlighting on the blog's front page is worse. So, not the page we were directed to. Did you happen to check out his Facebook page, too? Did you decide to comment on his awful dinner choice last night? > There is a bit of oddness This whole sentence is odd. In fact, that sentence is far worse than anything the OP did. You would say it's awful. In this case, you'd be right, because it's a shit sentence. > in declaring yourself a front-end person by talking about not needing to be tested as a back-end person That's not what he's doing. He's saying he's a front-end person, and was tested for back-end work. He's not saying he's a front-end person by talking about not needing to be tested as a back-end person. Those are two completely different things. If you don't immediately understand why, I apologize, but you wrote the awful and confusing sentence. > when you're applying for a front-end job yet having a blog with a such a jarring front-end. What's jarring about it? Surely you aren't speaking of the design. That would be a designer, not a front-end person. And we've established he's not apply for a designer's position. Unless you are suggesting all designers should be expert programmers? Because that's the only way what you said remotely makes any sense. Awful, just awful.