|
REST operations aren't fancy, they're just operations.
Just slap him with some YAGNI and move on.
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
That's a very bad sign indeed. You are becomming a pointy haired boss and are beginning to sound like them. Have you been bitten by one? I would sprinkle you with holy water and garlic juice, but I am allergic myself to one of them.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
It seems that most every time I have ever delivered a POC or mockup, even after explaining that 'these screens aren't wired yet', someone inevitably complains that they can't save their input. 
I agree that its overkill for a proto, but hard to argue with someone doing more than required...just at the wrong time.
"Go forth into the source" - Neal Morse
|
|
|
|
|
If it is holding up the task at hand, that is a pretty easy argument to make.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Quote: they can't save their input
I've had a design totally rejected because of this! 
They wondered why I started steaming from my ears.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
once worked for a boss who would be a perfect match to your man,
this bosses concept of a POC was something that had *full functionality* to be "demonstrated on a subset/sample of the data."
Seriously, one project was: "OK team, we got a potential 5 - 6 month project to develop a package to do account consolidation using 'fuzzy logic account matching' on 60 million records from 3 different systems, we need a POC / demo system to do ALL of those things on a 6000 record sample for a meeting with them next week. We're flying in for the demo next Friday and by the way it has to be on their hardware because they can't release any data [privacy bullshit] even for testing."
I magnanimously offered myself for the role of preparing the powerpoint slides for that meeting. 
Message Signature
(Click to edit ->)
|
|
|
|
|
Lopatir wrote: I magnanimously offered myself for the role of preparing the powerpoint slides for that meeting
 
|
|
|
|
|
Lopatir wrote: they can't release any data [privacy bullshit] even for testing
Been there, done that so many, many times. We build commercial inkjet printing systems. I've lost track the number of times a customer has complained of a printing problem, we've asked them to send us their data, and one of two things happen. They either outright refuse, or they send us "pretend" data that was hacked together by hand. We're still supposed to fix their problem, though  .
Software Zen: delete this;
|
|
|
|
|
|
How about the other way around, when I use software (let's say - some popular IDE) that is sold in the millions, and the vendor is too cheap to invest in proper QA and automated tests?
Then, *every* *single* new minor version has some regression in it, and the vendor will not even look at a bug report that doesn't contain a whole bunch of logs and data that we cannot legally release to them.
Also, in many cases a company wants to protect their users' personal information. Legality and regulations aside, this is the ETHICAL thing to. Wouldn't *you* be happy to know that your PII is treated with respect and that access to it is shared with the minimum number of people?
Sure, it's frustrating to the vendor, and to the developers, and to me personally when I'm on the side that needs to fix bugs with limited information - but it is a fair price to pay for having an ecosystem that respects people's information and privacy.
|
|
|
|
|
obeobe wrote: an ecosystem that respects people's information and privacy
Occasionally that's the case, but most often it's far simpler. A number of our customers use our systems to print lottery tickets. Those folks almost never give us data, since they don't want us to print a winning ticket. The ones who print customized catalogs, account statements and the like won't share their data because they're worried about their competitors getting their customer list.
Software Zen: delete this;
|
|
|
|
|
I can't help but think that three years down the line you'll be thanking the invisible pink unicorn that he went to all that trouble.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Gasoline and a match.
![Beer | [beer]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/beer.gif)
|
|
|
|
|
One very useful skill to have is an understanding of what to leave out of a POC. I always try to omit at least one key thing that prohibits the POC from going immediately into production. Otherwise there is strong possibility that it might. You can easily find a whole new set of problems dropped in your lap when that happens and, of course, they have to be fixed immediately since the POC is in production.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
I have an application (classbuilder) that writes all 3 levels of the CRUD code in about 30 seconds for each table/view. Stored proc, API or WCF, client data service and controller if required and even some of the WPF views.
I used to specialise in POC and most went straight to production with only the custom processing required.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
Prototypes tend to become products.
(Vaguely related: I was at G2E last year and one of the big vendors was showing what was clearly a prototype. But, they didn't even bother adding bogus data, so the presenter actually asked us to imagine the data being there.)
|
|
|
|
|
Nand32 wrote: I just needed a Create API to populate the data. Nobody cares if the data is deletable or updateable
And if it's not readable, you don't need to test the writeable part. Sounds perfect to me, since my code is always correct the first time, so no need to test it!
CQ de W5ALT
Walt Fair, Jr., P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
Tell him it is company policy to delete all POC components after the demo.
And see if he cracks as you purge his POC components.
(Good SCM makes this kind of impossible to do though)
|
|
|
|
|
I have to agree with the developer and I don't believe this is perfectionism. I have a distinct feeling this is experience and being burned a few times. The specifications you are providing, to me, don't sound fully flushed out and it sounds like there are a whole lot of truly unreasonable expectations of both people and the final system. I am left with two conclusions, either you are building a prototype to demo to reinforce the requirements, in which case the developer SHOULD NOT BE DEVELOPING, or you don't have a full understanding of how systems and people usually function and you need to be looking hard at your expectations.
Call me a skeptic but your stated requirements break down like this, you have someone who wants to create data, never read it, will always input it correctly and always have whatever that data is follow through perfectly. That is what you are describing. From CRUD you are stating is that the data will only be created, well that means you don't need the read to verify the input was correct. You don't need the update because their data will always be input correctly the first time, and never need alteration. The data will always be followed through on (i.e. I have a store and every order ever placed will always be completed and never removed). Unfortunately, none of that sounds true. It sounds more like the specifications aren't fully flushed out and you are prototyping a product that is not whole.
I have seen this, and I may not be exaggerating here, a million times but when you start the sentence off with I have this data, it literally means, I will tell you I don't need CRUD but in reality I do, I just don't realize it yet. I will the day before we launch. In nearly 20 years, I have yet to hear of a system that never needs all of the parts of CRUD. I have bumped into systems that don't need the delete part, but even those are rare.
|
|
|
|
|
tell your boss, "Keep it simple, stupid." If he fires you, he did you a favor.
|
|
|
|
|
First of all, I'm really pissed that Microsoft has started using completely worthless digital "badges" instead of certificates when you pass their tests.
But this takes the cake, today I got a mail from Microsoft saying:
Congratulations, you have now been a member of the Microsoft Dynamics Community for 2 years. Click here to redeem your "I've been a member of the Microsoft Dynamics Community for 2 years and all I got was this lousy badge" badge!
Precisely WHY would I want that? Is that all they have to do at Microsoft? And is that really the level of seriousness you can expect from a world leading company of Microsoft's size???
Yeah, I know that the mail was autogenerated, but still, somebody has put time and effort into developing this "valuable" feature... If they hadn't used a noreply mail address, I would have told them exactly what they could do with their "badge"!
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
-
Never argue with a fool. Onlookers may not be able to tell the difference.
Mark Twain
modified 4-Jun-19 4:21am.
|
|
|
|
|
Relax have a cigar...
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
Johnny J. wrote: Click here to redeem your...
What!! No credit card required???
I'd grab it before that changes.
|
|
|
|
|
It's a sort of gamification.
Collecting badges is fun and gives a sense of accomplishment.
And while not something of real business value it does say something about your level of commitment and may even give an incentive to be more active.
If I had to hire one out of two people and one is loaded with badges that would certainly be a plus.
Kind of like CPs reputation system.
As far as I know they don't replace actual exam certificates though...
|
|
|
|
|
Sander Rossel wrote: As far as I know they don't replace actual exam certificates though...
Can't speak in general, but in some cases at least, they do. I've taken exams for which I could get a badge, but not a certificate... 
For all the exams I took in 2018, I only got a badge, no certificate:
Exam 896: Distribution and Trade in Microsoft Dynamics 365 for Finance and Operations
Exam 894: Development, Extensions and Deployment for Microsoft Dynamics 365 for Finance and Operations
Exam 535: Architecting Microsoft Azure Solutions
In 2017 I didn't do any exams, but in 2016 I did 3 - for which I got certificates for all of them...
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
-
Never argue with a fool. Onlookers may not be able to tell the difference.
Mark Twain
modified 4-Jun-19 5:29am.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
