Wait until a pattern emerges, "rule of three". "But this is a rewrite of existing legacy functionally" I came to an org that is rewriting their entire .net in

Wait until a pattern emerges, "rule of three". "But this is a rewrite of existing legacy functionally" I came to an org that is rewriting their entire .net in kotlin, and trying to do it right. Then came the PMs who mentioned "this legacy functionally is getting resigned, we don't need a lot of this" but by that time, the Principal Arch had already gotten his promotion and built interfaces extending interfaces and common libraries composed of common libraries, and everything is neatly pushed into its own modules, leaving 1 file per module, max hierarchy for max portability that will never happen. The junior devs ask more questions about "where should this live" after being bitten by overarch.