1081 upvotes, 6 direct replies (showing 6)
View submission: Massive Failure on the Product
I mean if I paid 4 devs full time for a year who didn’t test a production build for its primary purpose, I would stop paying too
Comment by roodammy44 at 26/01/2025 at 22:49 UTC*
653 upvotes, 8 direct replies
If the devs are working 12-16hrs a day for weeks at a time you can bet “there is no time for testing” and the project was dead before it even started.
There’s a reason that people say that there’s negative productivity after 8 hours of solid coding. I know that for myself after 10 hours I stop giving any sorts of fucks and just sling shit against the wall. Management with long hours culture are not the type to care about code quality.
Comment by [deleted] at 27/01/2025 at 01:49 UTC
9 upvotes, 1 direct replies
[removed]
Comment by trevorthewebdev at 27/01/2025 at 01:34 UTC
11 upvotes, 1 direct replies
yeppers
Comment by shmorky at 27/01/2025 at 11:03 UTC
1 upvotes, 0 direct replies
I agree, but I have to say some orgs are very weird about letting devs touch production data
Comment by nasanu at 27/01/2025 at 01:08 UTC
-13 upvotes, 4 direct replies
Did you read? The issue was with the prod database. Do you test on prod? If not then this could also happen to you.
Comment by ivannovick at 27/01/2025 at 00:40 UTC
-29 upvotes, 1 direct replies
devs develop, not test, that team needed QA team