[vincekerrazzi]

Potential digression here, this is why I absolutely insist on high performing software teams to have at least one junior. You need someone asking questions like this.

[r00f]

Would it work in this case? Had he asked about this in a team, he would be told about the existing approach and that'd be it. I've been on the both sides, as junior questioning common practices and as senior answering such questions - and it always resulted in transfer of common knowledge, not some breakthrough.

I totally support searching for the new truths, but we must not forget why the phrase "do not roll your own crypto" exists. It is ok, or maybe it even MUST be done by students and researchers, but I am not so sure about juniors working on production systems. Still fine if you work in R&D department

[KineticLensman]

Yes, just like evil geniuses should have their plans for world domination reviewed by a 5 year old

[jsty]

Of course not - that would be ridiculous - it's clearly a job for a Mini-Me! ;)

[socks]

unfortunately, I have a feeling that in the age of LLMs, this junior on the team will have no impetus to actually put in effort and _think_ about such a problem

[falconertc]

We survived the age of StackOverflow. I don't see why LLM's will be the death of critical thinking where all else has failed so far.

[gopher_space]

It’s nice to have someone around who doesn’t understand that I’ve given them hard work. Big, open ended tasks like “invent a photogrammetry pipeline”

[geodel]

I think a presence of even single senior can dampen the questioning part. So I prefer all junior team to make some big path breaking changes.