36 ms·
There was just an article on here last week about how software development is a learning process and programs are just artifacts of that process. Big, old, mess
by belter5 6y ago
There was just an article on here last week about how software development is a learning process and programs are just artifacts of that process. Big, old, messy, and highly regulated domains will obviously be hard to learn.
- ethbr0 6y agoHere's an example I learned on Friday: If money is left over, apply to the next available item via (logic). Unless money is sent twice, for two separate sub-items on the same item, in which case if the first amount is insufficient to cover the entirety of the first sub-item, the excess (if any) from the second amount, after being applied to the second sub-item, must be applied to the remainder of the first sub-item. There are legal ramifications of doing the first way, without the second. And only the actual in-the-trenches people were able to tell us about the second. Using outsourced process documentation is @&$&ing useless.
- Aeolun 6y agoTo be fair, this sounds like someone having a hard time saying you should apply the money sent to the entire balance.
- ethbr0 6y agoNope. That's pretty much what the specs (written by outsourced consultants) said. In reality, there's one edge case where things needs to be applied in a different, distinct, and very specific order, otherwise (legal consequences).
- Aeolun 6y agoYeah, this is probably just my lack of context around the subject. That said, if I get requirements like that I always have a strong feeling the case can be generalized. Laws generally aren’t as specific as that.
- ethbr0 6y agoThis is around refund payments and interest, in healthcare. So probably an outlier. ;)
- bdavis__ 6y agonot to mention the fact that by definition the software developers know very little about the domain (given that 1/2 of them have less than 5 years of experience)