@janl @mandelhorn I spent yesterday digging through our procedure for upgrading and releasing acquired software. The whole process starts with a needs assessment - understand what we need the software to do before selecting the software to do it. Greenfield or upgrade, you have to ask what your needs are, have they expanded or changed since your last release. Needs drive software selection and requirements, requirements drive tests. This is fundamental software lifecycle management and you ignore it at your peril. It's only made worse by the expectation that code can be released as fast as it takes the unit tests to pass - it shortcuts the review and evaluation process which cannot be automated away.
Resources have a limit and a cost no matter how much those costs and limits are buried or masked by 'scalability'. Do you ever look at your code's memory or disk or CPU or network use when there's not an obvious performance issue, just to understand what your code consumes under normal operation? Thus isn't a matter of optimization, it's about getting a basic understanding of your code's resource usage.
=> More informations about this toot | View the thread | More toots from arclight@oldbytes.space
=> View janl@narrativ.es profile | View mandelhorn@mastodon.social profile
text/geminiThis content has been proxied by September (3851b).