Skip to main content
15 events
when toggle format what by license comment
May 29, 2023 at 6:45 comment added Tristan Could u give me your lights on a similar but more detailed question about the "pyramid of tests" principle : softwareengineering.stackexchange.com/questions/445771/…
S Feb 15, 2023 at 18:31 history suggested Henke CC BY-SA 4.0
Attempt to improve grammar and language.
Feb 15, 2023 at 16:26 review Suggested edits
S Feb 15, 2023 at 18:31
Aug 18, 2021 at 12:30 vote accept Dane Bouchie
Aug 12, 2021 at 14:24 comment added Robert Harvey Great article. I especially like: "Today it would not be at all surprising to find that an engineering team has built a backend using REST even though the backend only talks to clients that the engineering team has full control over. We have all become the architect in this Monty Python sketch, who designs an apartment building in the style of a slaughterhouse because slaughterhouses are the only thing he has experience building."
Aug 12, 2021 at 14:17 comment added candied_orange @RobertHarvey if we're gonna talk about what happened to REST, can you top this? Oh and thanks for the edit.
Aug 12, 2021 at 13:46 history edited Robert Harvey CC BY-SA 4.0
deleted 1 character in body
Aug 12, 2021 at 13:44 history edited candied_orange CC BY-SA 4.0
deleted 1 character in body
Aug 12, 2021 at 13:12 comment added Robert Harvey To which Roy Fielding replies: There is no such thing as “Common REST” (nor, for that matter, the alternative declarations of “Low REST” and “High REST”). There is just REST. The problem is that various people have described “I am using HTTP” as some sort of style in itself and then used the REST moniker for branding (or excuses) even when they haven’t the slightest idea what it means. The only way to stop people from misusing the term is to make a negative example of them when they do.
Aug 12, 2021 at 13:11 comment added Robert Harvey From here: “Common REST” is all about using PUT and DELETE and organizing your data into CRUD-based interfaces. Common REST is winning mindshare over REST as you defined it. In an environment where the number of links defines authority that means Common REST IS REST.
Aug 12, 2021 at 13:03 comment added Robert Harvey It wouldn't be the first time a group of developers decided on their own to change the meaning of some word or concept. REST is the most egregious example I can think of, and there are many others. There is actually a comment on one of Roy Fielding's blog posts that claims REST no longer means what Roy says it means, because the "consensus" has evolved to mean something else. As if that somehow carries more weight than the guy who invented the term.
Aug 12, 2021 at 13:02 history edited Robert Harvey CC BY-SA 4.0
deleted 1 character in body
Aug 12, 2021 at 6:04 comment added Billal BEGUERADJ wouldn't corrupt it like they did TDD: TDD did not corrupt anything. People who misunderstand TDD corrupted the "behavioral aspect" you mentioned. Many "respected" doers published books to explain TDD "to corrupt it" because they simply did not read Kent Beck's original book.
Aug 11, 2021 at 17:49 history edited candied_orange CC BY-SA 4.0
added 7 characters in body
Aug 11, 2021 at 15:29 history answered candied_orange CC BY-SA 4.0