Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
gronostaj156565dCharge for it, obviously. Are you fixing bugs for free too?
C0D44764765dWas the dev hired / contracted by the studio?
Was the database design and implementation sold to the customer, or leased in a contractual subscription model with on going support and maintenance?
Depending on your answers, you should be able to answer your own question.
It's only a bug if the original spec has not been fulfilled. If there is no original spec, then it is automatically fulfilled.
A "spec" however might also be some sort of description or use cases or anything like that which doesn't contain the length spec, but describes the usage so that a dev should have been able to conclude back then that the field length had to be a little longer.
Either way, if you aren't Oracle, then it's probably a good idea not to fuck the customers over a minor update no matter whose fault it was.
It's a change request. Of cause you charge them !
@Fast-Nop He didn’t screwed up. For 3 years softawere was conform to specification. Then they decided to change specs with more data.
It’s a change. They pay.
I used int32 as Ids in most of my projects. So when one of them (probably never) runs to max, It’s not my job to change it to int64 or guid. (I use only guid now tho)
Using these 32 bit IDs is fine as long as that is documented AND signed off by the customer, even if it's buried deep down on page 150 of the system documentation.
Because if you sell stuff that doesn't do what you claim it does, and you don't even want to put it straight afterwards, prepare to get sued. Also, 60 days is ridiculous.
You know how this looks? Trying to rip off the customer for shit you have botched up.
@Fast-Nop And that’s why I put everything in my spec docs. I find this part is even more important than code it self.
And I mean including even what datatypes will be used, protocols, platform. And specially what will not be in the final product. I will add most of things they will ask me anyway as “Additional cost”. You want sorting on your tables? Additional cost. You want grouping? Additional cost.
And all of these is based on their budget. If I feel like they have enough budget, I would quote these “additional cost” directly in the project definition.
Anything what is not explicitly stated in the docs will not be done and is a change request.
They read, sign and accept these definitions.
If they want to change anything: I’ll bill them.
@Fast-Nop And 60 days (for small/medium project. Not talking about ERP level) is more then enough. If they wait 3 months before starting tests, I’ve moved already on another project. Thier fault. So fuck them.
My product will always respect the initial definition. But if in a year you come to me and say “it doesn’t work when XXX” and XXX wasn’t part of original use cases : Bill them.
nitr0xis211. Customer wants X. 2. Developer delivers X. 3. Customer wants developer to change X to Y for free. 4. Develo...
blt9503If doctors were treated like web developers!
M-Arcus18Never let customers define the priority levels. It will end in: - Normal (never used) - High (used for small...