> According to wikipedia CVS has been around for 26 years.

Not to mention SCCS for 44 years, and RCS for 34.

You mean how they're removing encryption support from all their firmwares?

Q...A?

It sounds like you want those to be steps that come after each other, like some sort of waterfall.

If you want to get with the times, you, the developer, should write a unit test for each file you think shouldn't be deleted on running the application.

Heh Heh Heh

That's one way of looking at it. ;)

Another way of looking at it is there shouldn't be a product update/release getting pushed out to hundreds of thousands of users (a guess), without passing an extensive validation suite. Developer unit tests are for a different purpose.

Unless I missed your sarcasm? :)

> Unless I missed your sarcasm?

Ohh yes.

Nowadays I work in medical devices. It's nice because you're actually legally required to spend 5 minutes making sure your product does what you say it will before you're allowed to sell it, in contrast with what's happened to the rest of the industry.

Not in today's Agile world.

Really the problem is just there wasn't a user story saying:

  As a user having a directory .AAAAA 
  When I run an Adobe application 
  The directory should still be there

Also, the computer should not spontaneously combust. And it shouldn't try to bite my hand off. And it shouldn't morph into a soul-devouring monstrosity either. In other words, there is an infinite list of things that your/my/any program shouldn't cause. Good luck making user stories for all of them.

This so much.

If your Agile developers follow user stories to the exclusion of common sense, you should probably fire them now.

I'm fairly certain the parent post was made in jest.

Me too; hence the absurd examples :)

Sounds funny, but you are sadly correct. Some junior (or even an experienced) dev just took the shortest route to delete the file that was always listed first on their computer. `deleteFile(files[0]);`

On the other hand, the long list of terms and conditions on the Toys R Us gift card actually makes it feel more legit somehow. ("Ahh, there's the catch"?) Maybe have the front page end with that list, or the intersection of all terms, or a similar terms and conditions for muxme itself, rather than "many pages of EVEN MORE PRIZES".

You're saying the picture with the bank statement? Or are you talking about the Official Rules portion?

Yeah the giant table of "win this! win that!" seems enormously scammy. Maybe because scam ads just display something so similar. And, key thing with yours and theirs, no context and leaves me wondering "what's the catch?".

Even if you just added a short paragraph explaining the concept (since otherwise when I get to your site I look around to see what it does, and see nothing but scam ads all over = scam site; if you actually say what the site's for the prizes have context) and how it works (otherwise I'm like, "sure, effectively free cash, yeah right" = scam site), and then have the prize list, it would make a big difference in first impressions. Maybe have any list of prizes on the front page not be a countdown of upcoming prizes, but a list of selected featured prizes ("including these brands!").

> Actually, after thinking about it, I'd use a GET

Why? Using it to change state seems precisely wrong. PUT seems more appropriate.

I'll always call the ISA "amd64".

Just don't force the background to bright white please.