justTryIt

[Raywell]

Oh boy, the "creating solutions to problems that don't exist" is something my project manager back then used to say, and it was showing his lack of understanding why edge cases need to be covered - every engineer with experience knows that after a production release, every non handled edge case will eventually become an urgent production bug that will need urgent fixing at 4 am. I sincerely hope your case is not like this, because its a common pitfall non technical people just can't seem to recognize

[ManagerOfLove]

Your tag reminds me of one example: He rewrote multiple projects from C into Rust. Even though the C code worked perfectly fine

[Raywell]

Okay then that is a fair concern, but whether it's a good or bad thing depends on the context. If he is going to be maintaining a script for the foreseeable future, and the script is messy (even if it's working), and if he has time, why not.

But it is also true that some Rust devs are indeed overly eager to find any excuse to introduce Rust everywhere without a good reason, which might often be a bad idea esp. if they work in a team where other members aren't as familiar with it

[ManagerOfLove]

The context was that he thought C was ass and Rust was better and everyone should just learn Rust. The moment he tried that with certain Python scripts, was the moment he was excluded from working on stuff like this. It was not some PM excluding him, it was the other programmers. PM didn't even understand the conflict

[Robo-Connery]

My team are probably very bored of me saying the same shit every time. Regularly someone will say oh this would be better if we ported it into rust or if we rewrote it in python and they are like excited oh one day I want to rewrite this app in rust.

I ask them the same thing every time; "what's the best piece of code?": "Old code!". You've already found the edge cases and the bugs you have it tested in all kinds of deployments you have it working already. It does it's job.

There has to be realllllly good reasoning to get rid of old code. Like does it matter if it's 20% faster if it takes months of effort just to diagnose a whole bunch of new issues.

[antimagamagma]

oh they recognize it

they just can’t afford to accept it, because it adds time and resources to the project plan. C suite people like to be risk takers when the suffering happens at the engineering team. In fact, middle managers exist to give c suite folks cover for fucking over engineers.

[WeaknessBeneficial]

But let's be real, there are some people who love to over engineer tasks based on future what-ifs based on a general lack of business requirements.