@delnan: Passing as POST will hide it from the average user, but that's about it. If it's sensitive, don't pass it to the client, period. :)

"so I can't exactly tell my employer that I need a couple weeks to write unit tests for all of their code". Is there a reason for that? I do that a lot, and it really pays off for everybody. I mean, if you take 3 weeks to unit test, you might just save 3 weeks of bug fixing. Usually I even find loads of eventual bugs that totally went under QA's radar. Sure, you probably don't want to do that all by yourself.

@HLGEM: Well I can say I disagree with you too. Funny that everybody compares this to my answer. Is this a contest of some sort I'm not aware of? I think it's actually a good practice to advertise something and deliver what's advertised. If I say "flying car", you expect a car that flies. If I say isTransposed, you expect something that checks if it's transposed. There's no abstraction involved. You're just making a simple problem a lot more complicated than it should be.

I'm not sure about the second part of your comment. Would you care to elaborate?

@mattnz: This just seems to me like a generic answer you could post to a lot of questions both on SO and SE, and probably be right 50% of the time, if not more. I can't say it's not true, just that I don't find it particularly useful.

@KeithThompson: I can't say I disagree with you. This question was direct and precise though, so I'm not going to second guess the OP there.

@KeithThompson: Semantically, is (as in isTransposed) defines that if you transpose the input and it gives the output (whether they're the same or not is irrelevant in semantics), then it's true.

@RossPatterson: My answer addresses the difference between is and hasBeen, which are semantically different, not different interpretations of "transposed". There was not reverse-engineering involved, it was actually quite the opposite.

@RossPatterson: So, aside from posting the actual result and the obvious "Granted the behavior can be documented but what are your thoughts on [method] returning [actual result] verse [some other result]?", what exactly is missing from that question? I understand that the expected behavior is specifically what OP is inquiring about. As far as this answer goes, it's totally missing the point IMO, although I wish I could say otherwise.

Both in your answer and the links provided, you refer to tasks and not stories. I believe the question is about stories. I mean, it makes sense and all, but doesn't really answer the question.

@blunders: Considering there's only one assertion in the whole question, I'm not sure why you ask.

Oh, and I have no idea where you take that quote from, and it's also unrelated to my first comment.

Story points are tied to a unit of time, but they're not themselves units of time like hours and days are. They're units of relative time.

Where is that suggested? AFAIK, you should size stories based on story points, not days.