Pop Quiz Hot Shot
-
Pretend you offer a REST API and a potential customer asked you to change one of the GET methods to allow POST as well. Let's also pretend that in all modern languages this is a 15 second change + deploy, 20 second if you have automated testing, 30 minutes if you write a unit test, I suppose. What do you do? A) Do it B) Refuse to do it C) Write a condescending refusal?
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost "All users always want Excel" --Ennis Lynch
-
Pretend you offer a REST API and a potential customer asked you to change one of the GET methods to allow POST as well. Let's also pretend that in all modern languages this is a 15 second change + deploy, 20 second if you have automated testing, 30 minutes if you write a unit test, I suppose. What do you do? A) Do it B) Refuse to do it C) Write a condescending refusal?
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost "All users always want Excel" --Ennis Lynch
I would do it, but I would tell him that it takes 40 hours and charge him a weeks work, and then I'd take the missus (or the mistress - depending on the mood) on a long weekend to Paris. :cool: What? Morals? Such a foul word! :rolleyes: Speaking of foul words, you started it: Unit test! X|
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
I'd just like a chance to prove that money can't make me happy.
Me, all the time -
Pretend you offer a REST API and a potential customer asked you to change one of the GET methods to allow POST as well. Let's also pretend that in all modern languages this is a 15 second change + deploy, 20 second if you have automated testing, 30 minutes if you write a unit test, I suppose. What do you do? A) Do it B) Refuse to do it C) Write a condescending refusal?
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost "All users always want Excel" --Ennis Lynch
D) Tell them it breaks your authentication model and so it is a huge security problem and will compromise their used of the system. Instead you will have to write a similar, yet different POST method requiring the necessary parts for authentication and it will take MANY days and cost MUCH money. After returning from a leisurely vacation and collecting some cash from the client, make the GET allow POST.
-
Pretend you offer a REST API and a potential customer asked you to change one of the GET methods to allow POST as well. Let's also pretend that in all modern languages this is a 15 second change + deploy, 20 second if you have automated testing, 30 minutes if you write a unit test, I suppose. What do you do? A) Do it B) Refuse to do it C) Write a condescending refusal?
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost "All users always want Excel" --Ennis Lynch
D) Do an impact analysis of what else will be affected by this change. Better to properly evaluate and schedule in an update than to perform a knee jerk change which shouldn't affect anything else but which probably is going to come home and bite you on the keester when it breaks something else for your biggest client.
-
Pretend you offer a REST API and a potential customer asked you to change one of the GET methods to allow POST as well. Let's also pretend that in all modern languages this is a 15 second change + deploy, 20 second if you have automated testing, 30 minutes if you write a unit test, I suppose. What do you do? A) Do it B) Refuse to do it C) Write a condescending refusal?
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost "All users always want Excel" --Ennis Lynch
Ennis Ray Lynch, Jr. wrote:
Pretend you offer a REST API and a potential customer asked you to change one of the GET methods to allow POST as well.
Don't touch working code unless you are absolutely sure it will not impact anything that is using it.* Instead offer a new POST method specifically for this client, and charge accordingly. Win, win. :-D * - If you do be sure you do full regression testing to insure it doesn't adversely impact existing code.
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am. JimmyRopes -
Pretend you offer a REST API and a potential customer asked you to change one of the GET methods to allow POST as well. Let's also pretend that in all modern languages this is a 15 second change + deploy, 20 second if you have automated testing, 30 minutes if you write a unit test, I suppose. What do you do? A) Do it B) Refuse to do it C) Write a condescending refusal?
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost "All users always want Excel" --Ennis Lynch
D) Mock the customer elsewhere on the intarwebz while being foolish enough to use your real name. :doh:
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
D) Mock the customer elsewhere on the intarwebz while being foolish enough to use your real name. :doh:
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
I could care less. I am acting on behalf of the customer in this case and mocking the vendor. Three separate individuals here spent quite a while trying to POST to this API only to finally discover it is GET only. What is the tenet of services, be liberal in what you accept and restrictive in what you provide or such? Saying a vendor of an API should accept a GET and a POST verb for the same method call is not a "game changer" by any means. And calling the vendor out without publicly identifying them is not really that big of a deal. Though, I am still holding out that they will change their mind.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost "All users always want Excel" --Ennis Lynch
-
Pretend you offer a REST API and a potential customer asked you to change one of the GET methods to allow POST as well. Let's also pretend that in all modern languages this is a 15 second change + deploy, 20 second if you have automated testing, 30 minutes if you write a unit test, I suppose. What do you do? A) Do it B) Refuse to do it C) Write a condescending refusal?
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost "All users always want Excel" --Ennis Lynch
Ennis Ray Lynch, Jr. wrote:
What do you do?
Send an invoice, based on the hourly rate, for all 35 seconds and the time you wasted emailing, phoning and posting here. Did the customer request a unit-test? Let me rephrase that, would it be billable?
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
-
Pretend you offer a REST API and a potential customer asked you to change one of the GET methods to allow POST as well. Let's also pretend that in all modern languages this is a 15 second change + deploy, 20 second if you have automated testing, 30 minutes if you write a unit test, I suppose. What do you do? A) Do it B) Refuse to do it C) Write a condescending refusal?
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost "All users always want Excel" --Ennis Lynch
B) Refuse to do it. I'll tell them, its not logical and why its not logical And will ask them why they need it and suggest alternative solution if possible.
-
I would do it, but I would tell him that it takes 40 hours and charge him a weeks work, and then I'd take the missus (or the mistress - depending on the mood) on a long weekend to Paris. :cool: What? Morals? Such a foul word! :rolleyes: Speaking of foul words, you started it: Unit test! X|
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
I'd just like a chance to prove that money can't make me happy.
Me, all the timeNice one :thumbsup:, but billing of 40 hours will not be sufficient if it break any existing (working) things :)