upvote

points

by balderdash20 hours ago |
comments
upvoteby cheney_20048 hours ago|
next
[-]
Curious, why did it take 3 months and not a few days? Honest question, just curious about what is consuming all the time in a project like this?
reply
upvoteby thejokeisonme4 hours ago|
parent|
next
[-]
Due diligence?
reply
upvoteby jurgenburgen4 hours ago|
parent|
[-]
What’s that? Is there an MCP server for it?
reply
upvoteby Traubenfuchs3 hours ago|
parent|
[-]
Just add “test everything”, “this is mission critical” and “make no mistakes” to the prompt.
reply
upvoteby Madmallard3 hours ago|
parent|
prev|
[-]
AI Booster comment spotted
reply
upvoteby slekker3 hours ago|
parent|
[-]
Need to keep the bubble alive one more day
reply
upvoteby petra19 hours ago|
prev|
next
[-]
That's really interesting.

What have been achieved using this port?

And how did you make sure the port is correct?

reply
upvoteby raizer884 hours ago|
prev|
[-]
Every time something like this has been done on my company I follow up with the question: did anyone watched the code to see if the business logic is the same between the two versions? The answer is: but but but automated testing.

Followup question: did anyone read the automated test suite?

Silence.

The software rewrite is shelved.

reply
upvoteby mattlondon43 minutes ago|
parent|
next
[-]
Why do people doing a rewrite need to have read the tests?

If you have good test coverage, and the tests are reliable, then what's the problem?

If your engineering culture is bad already and you don't have good test coverage or they're flaky or whatever then that is different. If that is the case, it is probably from smart-ass attitudes like yours asking these "clever" rhetorical questions to derail people trying to improve things that led it to be like that. Do everyone a favour and keep your mouth shut and let people fix things.

reply
upvoteby dannyw2 hours ago|
parent|
prev|
next
[-]
Honest question: does that even remotely matter, or is it an outdated prior? All software has bugs.

The goal and objective is to deliver value for your user/customers; to the speed, reliability, and assurance requirements your market segment expects.

reply
upvoteby raizer881 hours ago|
parent|
[-]
All software has bugs, but right now you have a legacy product in production that works, then you have a rewrite that nobody tested. Do you accepted the risk to yolo it?
reply
upvoteby grim_io1 hours ago|
parent|
[-]
Sometimes the risk is acceptable, sometimes it's not.
reply
upvoteby risyachka2 hours ago|
parent|
prev|
[-]
Yup. And its always garbage as result
reply
upvoteby rurban1 hours ago|
parent|
[-]
Not if you have a good harness. Docs and tests first
reply