News for hackers. Stuff that matters.
Re:The saddest "Just Ship It" story ever (2020) by dclowd9901 on Thursday July 04, 2024 @02:50AM (#40872886)
I 100% agree with you. I’m in a situation at the moment when I’m nearly constantly having to check myself against other devs. I don’t do hacky work and nothing I do isn’t extensible or easily refactorable. But I constantly get feedback from another dev on my team wanting me to polish out a change to perfection against every feasible possibility. I try to employ YAGNI reasoning to them, but they just have a perfectionist standard.

Look: job 1 is making safe software, job 2 is making money and job 3 is perfecting the architecture.

Re:The saddest "Just Ship It" story ever (2020) by another2another on Thursday July 04, 2024 @08:46AM (#40874490)
Ask them to write the tests that will trigger the failure condition - i.e. make them prove that it's a possible thing that can easily occur.

If it is, then at least you have a simple test case to work with so they've done a chunk of the work for you. If it's not, then they'll spend ages trying to craft a test case for a scenario that's extremely unlikely.

People very often leave you alone when challenged to put in the work to prove their point.