|
agile is where you basically do waterfall but break down the waterfall bits into bits that can ostensibly be done over 1-2 weeks. at the end you poo poo out a product with obvious flaws that could have been caught in about 3 minutes had anyone actually tried to use the thing, rather than just confirming that tests pass. this garbage is then provided to customers and will basically remain as originally written forever while engineering teams move onto the next block of sprints to produce new flawed things, most of which will only be used by the one customer who screamed real loud about really really needing something that they will likely also cease using after the one person there who wanted it leaves or moves into management eventually some of the garbage might be replaced with complete rewrites that try to improve on some of the more egregious bad design decisions while introducing a suite of new ones.
|
#
¿
Nov 22, 2019 06:54
|
|
|
|
| # ¿ May 17, 2024 00:44 |
|
|
echinopsis posted:very rarely does it take me longer than ten minutes to do a prescription and often it’s less than 5 from the time the patient hands it till when I give them the drugs. imagine if instead of prescribing based on a wealth of information in scientific literature and FDA testing that you just formulated drugs from scratch out of basic reagents with a vague idea of what the end structure should sorta look like, gave the results to patients, and improved on that by ruling out whichever syntheses resulted in deaths. now, you might say that this is a bad idea, but think of how much worse it would be if you just used one random synth only and it killed everyone!
|
|
#
¿
Nov 26, 2019 05:26
|
|