@koire @slightlyoff FWIW, I'm planning out the next release of some vendor-supplied safety analysis code. It will take substantially less than the 22 months it took to V&V and containerize the code the first time around - ideally I won't be waiting 6-8 weeks for IT to revise their procedures and get around to pushing things live this time.
Still, the process will likely take 3-4 months, mainly spent on review, evaluation, and documentarion. V&V will be more intensive in certain areas so there will likely be another big pile of questions (and possibly answers) sent back upstream. Ideally the release effort would be reduced to 4-8 weeks; any lower than that probably means the V&V process is being shortcut or the release isn't substantial enough to warrant an upgrade. We probably shouldn't be updating the production code more than once every 9-15 months unless there are critical bugs or there's a feature desperately needed by the code's users (safety analysts). Upgrading more frequently than annually is disruptive to the safety analysis process - our job is to support the engineering work being done. The software is a tool, not a product.
I do not miss web systems. At. All.
=> More informations about this toot | View the thread | More toots from arclight@oldbytes.space
=> View koire@hachyderm.io profile | View slightlyoff@toot.cafe profile
text/geminiThis content has been proxied by September (3851b).