Currently working for the same kind of company (logistics, niche domain) with a mix of big ERPs (yes, not just one) and in-house software. If you go with in-ho

Currently working for the same kind of company (logistics, niche domain) with a mix of big ERPs (yes, not just one) and in-house software. If you go with in-house you want to make sure it does not spawn multiple pet projects per need. And you don't want your software to rot. I took my current role to be part of a modernization effort because "it's old software". Well, I did not expect this kind of outdated and things are slow to replace because everything (and many "surprise" scripts and app no one use but in fact someone does) depends on the same badly setup database. But it's a "fun" challenge. You really want easy to update / rewrite / replace software. Not just a "let's build it one time then consider it good to go for the next couple decades" politics. > Besides, can we even attract experienced developers to a non-glamorous industry like logistics? Yes, if you can present a good software project. Also pay and perks like WFH will often trump glamour, especially with experienced devs.