Hacker News new | ask | show | jobs
by valicord 373 days ago
What is the point of assigning something to a new hire, if they can't do it without another person watching the whole thing over their shoulder AND they are unlikely to benefit from this knowledge in the future (since it's a legacy page that is supposed to be deleted)?
2 comments

Anytime a website is created, the information/text to used in the site is provided to the devs. You provide the same data to the QA team to ensure the Dev team did their job.

How are we seriously this obtuse? Is it deliberate?

Instead of snark please re-read the entire comment thread from the beginning and you'll realize that the scenario you're imagining is completely different from what is being discussed.
I often assign things to new hires because I expect them to approach the question without the biases of long-time team members who have learned to overlook and normalize some bullshit. Either the new person is wrong, and I explain why, and they learned something, or they're right and the existing stuff can't be defended or justified, and I learned something.